You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/kyc-sharing.md
+20-2Lines changed: 20 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,28 +8,46 @@ To improve the onboarding experience, we provide multiple ways to empower our bu
8
8
9
9
By receiving KYC details, Topper can reduce the amount of information requested from users, resulting in a faster and smoother KYC process.
10
10
11
+
Of the two approaches below, **KYC shareable tokens** is the recommended path. The **KYC sharing API** is an alternative for partners who do not use Sumsub or prefer a manual REST integration.
12
+
11
13
## KYC shareable tokens
12
14
15
+
:::tip
16
+
**Recommended approach** — use this whenever your KYC provider is Sumsub.
17
+
:::
18
+
13
19
When starting a Topper session, partners can provide a KYC shareable token, which will be used to ingest all available information for the required scopes.
14
20
15
21
Currently, we only support tokens from **Sumsub** provider.
16
22
17
23
:::note
18
-
Only applicants with a valid identity will be able to be ingested through the shareable token.
24
+
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.
19
25
:::
20
26
21
27
:::info
22
28
To use KYC shareable tokens please see [crypto on-ramp](./flows/crypto-onramp.mdx) or [crypto off-ramp](./flows/crypto-offramp.mdx) flows documentation.
23
29
:::
24
30
31
+
### User experience
32
+
33
+
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.
**Alternative approach** — use this only if you cannot integrate via Sumsub or prefer a manual REST integration.
43
+
:::
44
+
27
45
There is a REST API where partners can check user KYC details and share information regarding current missing or expired/outdated scopes.
28
46
29
47
Currently, we support the following scopes: **email**, **profile**, **address**, **phone**, and **identity**.
30
48
31
49
For more details, see the [KYC sharing documentation](https://developer.uphold.com/rest-apis/core-api/kyc/introduction).
32
50
33
51
:::info
34
-
To use the KYC sharing API, business customers need to complete a compliance check and be approved before gaining access.
52
+
To use the KYC sharing API, business customers must be reviewed and approved by Compliance to be authoritative for the shared scopes before gaining access.
0 commit comments