Closed Tieumsan closed 1 year ago
@bgodlin please complete the requirements @spitsynval please add link to the design
please complete the requirements
done
Endpoints \kyc-status
, \last-kyc-status
.
Example KYC result with rejection_reasons
:
{
"kyc_id":"936da01f-9abd-4d9d-80c7-02af85c82222",
"person_id":"00000000-0000-0000-0000-000000000000",
"user_reference_number":"1234567890",
"reference_id":null,
"kyc_status":"Completed",
"verification_status":"None",
"iban_status":"None",
"card_status":"None",
"additional_description":"Video verification was rejected",
"rejection_reasons":[
{"Description":"The user uploaded screenshots"},
{"Description":"Your KYC application was rejected"}
],
"update_time":1696494249
}
@bgodlin we need clarity on what to show to users. Current imp shows hardcoded text: Your application has been rejected.
So, do we need to use additional_description
instead of hardcoded text
and rejection_reasons
, use all of them, or just ignore additional_description
?
@bgodlin we need clarity on what to show to users. Current imp shows hardcoded text:
Your application has been rejected.
So, do we need to useadditional_description
instead ofhardcoded text
andrejection_reasons
, use all of them, or just ignoreadditional_description
?
@2bogd As it is currently stated in the designs (see https://github.com/sora-xor/sora-card/issues/108#issuecomment-1748746029), you should display both.
Problem Statement
Currently users are not provided with enough information to determine the reason their KYC application has been rejected.
Solution
We can receive details from the partner's API. The description received can be shown on the relevant screen.
Platforms
Backend
Client applications
The application should present all potential rejection reasons found within the
rejection_reasons
object, when handling the status according to the newly presented schema in https://github.com/sora-xor/sora-card/issues/94. This object is an array, with each of its child objects containing aDescription
field. It's important to list all of these reasons, so implementing scrolling may be necessary.Web
Mobile