Enhance KYC sharing documentation#123
Conversation
|
🚀 Preview has been deployed.
|
|
|
||
| :::note | ||
| Only applicants with a valid identity will be able to be ingested through the shareable token. | ||
| The Sumsub shareable token flow is only initiated when the user has a valid Sumsub identity **and** Topper requires identity (or related personal-data scopes) for the current session. If identity is not needed, the token is ignored. |
There was a problem hiding this comment.
The Sumsub shareable token flow is only initiated when the applicant has a valid Sumsub identity and Topper requires identity for the current session. If identity is not needed, the token is ignored.
|
|
||
| ### User experience | ||
|
|
||
| When the share token is accepted, the user sees their partner-provided identity document already marked as accepted in Topper and only needs to complete a fresh liveness check rendered by the Sumsub SDK. |
There was a problem hiding this comment.
The user will be presented with a KYC onboarding screen, where they will be required to capture a selfie as part of a liveness check to securely share their personal data. The Sumsub SDK will be initiated, allowing the user to clearly see the information they are about to share while guiding them through the liveness verification process. Once the selfie is successfully submitted, the user will either proceed to transact or, if necessary based on their country, be prompted to provide additional KYC details.
There was a problem hiding this comment.
And update images with the KYC onboarding screen, the initial screen after the SDK has been initiated, the steps screen, and the pre-initiate liveness check step.
2 participants
Description
Reframes the KYC sharing documentation to clearly position shareable tokens as the recommended approach and KYC sharing API as the alternative for partners that don't use Sumsub.
Changes in
docs/kyc-sharing.md::::tip"Recommended approach" admonition on that section.### User experiencesubsection with two screenshots showing what the end user sees: the partner-provided identity already accepted, and the Sumsub liveness check rendered inside Topper.:::info"Alternative approach" admonition on the API section and strengthened the compliance note — partners using the API must be approved by Compliance to be authoritative for the shared scopes.Related issues