Unblock offers its Merchants two levels of KYC and KYB process abstractions. The more abstraction you build, the better the UX for the Individual and Corporate going through the process.

📘

Individuals require KYC before any bank account creation

An individual can use their Unblock bank account to do a fiatToCrypto or cryptoToFiat transaction after user creation and after providing KYC information.

☝️Level 1: SDK and full delegation to Unblock

At this level, you can leverage the partnership between Unblock and Sumsub to gather identity and verification (IDV) documents from individuals extremely quickly, with very little development time.

The process is as follows:

1. Create a user

2. Create a KYC applicant using this endpoint
3. Retrieve Sumsub SDK token using our endpoint
4. Initiate the Sumsub SDK using the token
5. This will initiate the SDK UI

5. Once the Individual is done with the IDV collection, the Merchant will get a series of webhooks confirming the state of the KYC process and when the user is approved

✌️☝️Level 2: Full delegation to the Merchant

At this level, Unblock will fully rely on the KYC process and assessment of the Merchant. We will only do a random periodical audit of the Merchant processes to confirm that they still fit with the standard agreed in our commercial agreement.

This level does not require technical integration, as all the data and process stays on the Merchant side.

For Unblock to go through this assessment and discuss specifics, please get in touch with the onboarding team

KYC statuses

Users progress through various KYC states while applying. Every state has a distinct status. Merchants will be notified about any changes in a user's state and related data via our webhooks standards. Below are the definitions for each status.

KYC_NEEDED

This is when a user has gone over his no KYC limit and will go through the KYC process to be able to do more transactions.

PENDING_KYC_DATA

This is when a user has started the KYC Process, but we are still waiting on a few KYC documents to complete the verification.

KYC_PENDING

This is when a user has provided all the documents needed so far, and we are performing our KYC checks; this state can last between 10s and 5 minutes with an average of 1 minute.

SOFT_KYC_FAILED

This state is when a user has not passed our KYC checks but has a chance to correct the data or upload supporting documents for another try. There can be lots of different reasons that a user enters this state; these reasons will be sent as part of thedata key.

HARD_KYC_FAILED

This state is reached when a user has not passed our KYC checks, and we have decided we cannot serve this user. This could be for several reasons, but unfortunately, this decision is final. Reaching out to your Unblock support will not change this decision.

FULL_USER

Once all KYC checks have been submitted and passed, the user status changes to FULL_USER allowing them to transact without restriction.