Add KYC shareable tokens documentation

Author: zangetsouu

docs/flows/crypto-offramp.mdx

@@ -29,6 +29,9 @@ The crypto off-ramp flow allows a user to sell cryptocurrency and convert it int
     - `type`: Tag type (e.g.: `memo` or `destination-tag`).
     - `value`: Tag value.
   - `priority` (_optional_): Priority of the crypto transaction (e.g.: `fast` will enable instant send for `Dash` transactions). Defaults to `normal`.
+- `reusableKYC` (_optional_): An object to provide a KYC shareable token.
+  - `provider` (_required_): Provider that issued the shareable token.
+  - `token` (_required_): Token issued that can be used to fetch user information.
 - `simulation` (_optional_): Simulation object.
   - `country` (_optional_): Country to use during simulations, in alpha-2 code format; It will be ignored after the user is authenticated and the user's country will be used.
 - `source` (_optional_): An object configuring the asset and amount to be sold.

docs/flows/crypto-onramp.mdx

@@ -24,6 +24,9 @@ The crypto on-ramp flow allows a user to add funds from a credit or debit card t
     - `same-tab`: Open in the same tab or iframe (default).
     - `parent-tab`: Useful only in an iframe: open in the tab that contains the iframe.
 - `partnerFee` (_deprecated_): Use `partner.fee` instead.
+- `reusableKYC` (_optional_): An object to provide a KYC shareable token.
+  - `provider` (_required_): Provider that issued the shareable token.
+  - `token` (_required_): Token issued that can be used to fetch user information.
 - `simulation` (_optional_): Simulation object.
   - `country` (_optional_): Country to use during simulations, in alpha-2 code format; It will be ignored after the user is authenticated and the user's country will be used.
 - `source` (_optional_): An object configuring the asset and amount to be paid.

docs/kyc-sharing.md

@@ -4,14 +4,32 @@ sidebar_position: 15
 
 # KYC sharing
 
-To improve the onboarding experience, we provide a REST API that allows our business customers to share user KYC information directly with Topper.
+To improve the onboarding experience, we provide multiple ways to empower our business customers to share user KYC information directly with Topper.
 
 By receiving KYC details, Topper can reduce the amount of information requested from users, resulting in a faster and smoother KYC process.
 
+## KYC shareable tokens
+
+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.
+
+Currently, we only support tokens from **Sumsub** provider.
+
+:::note
+Only applicants with a valid identity will be able to be ingested through the shareable token.
+:::
+
+:::info
+To use KYC shareable tokens please see [crypto on-ramp](./flows/crypto-onramp.mdx) or [crypto off-ramp](./flows/crypto-offramp.mdx) flows documentation.
+:::
+
+## KYC sharing API
+
+There is a REST API where partners can check user KYC details and share information regarding current missing or expired/outdated scopes.
+
 Currently, we support the following scopes: **email**, **profile**, **address**, **phone**, and **identity**.
 
 For more details, see the [KYC sharing documentation](https://developer.uphold.com/rest-apis/core-api/kyc/introduction).
 
 :::info
-To use the KYC sharing feature, business customers need to complete a compliance check and be approved before gaining access.
+To use the KYC sharing API, business customers need to complete a compliance check and be approved before gaining access.
 :::