At present, all client applications have a fixed count of 2 complimentary KYC checks programmed into them. This setup has led to users receiving unclear rejections for SORA Cards, resulting in the rapid consumption of their 2 available KYC attempts. To demonstrate our appreciation for early adopters, we aim to raise the number of complimentary KYC applications to 4, until the integration with the acquirer is completed. However, modifying this count necessitates updating all associated applications.
Solution
Rather than relying on hard-coded values, it would make sense to enable to fetch the allowed count from the middleware. By implementing this approach, any future changes to the count will only require updates on the middleware level, avoiding the need to modify individual applications.
The application should make a call to /kyc-attempt-count, requiring a JWT access token, and retrieve a JSON response containing the KYC attempt counters. This number should then be cross-referenced with the count of previous KYC checks, just as it is currently done.
Problem Statement
At present, all client applications have a fixed count of 2 complimentary KYC checks programmed into them. This setup has led to users receiving unclear rejections for SORA Cards, resulting in the rapid consumption of their 2 available KYC attempts. To demonstrate our appreciation for early adopters, we aim to raise the number of complimentary KYC applications to 4, until the integration with the acquirer is completed. However, modifying this count necessitates updating all associated applications.
Solution
Rather than relying on hard-coded values, it would make sense to enable to fetch the allowed count from the middleware. By implementing this approach, any future changes to the count will only require updates on the middleware level, avoiding the need to modify individual applications.
Requirements
Backend
Client Applications
The application should make a call to
/kyc-attempt-count, requiring a JWT access token, and retrieve a JSON response containing the KYC attempt counters. This number should then be cross-referenced with the count of previous KYC checks, just as it is currently done.[x] https://github.com/sora-xor/sora-card-android/issues/103
[x] https://github.com/sora-xor/sora-card-ios/issues/73
[x] https://github.com/sora-xor/sora-card-web/issues/27