Skip to main content
Before your users can operate, Ripio needs their identity data. In the API integration you always collect that data in your own UI and submit it with Create KYC Submission. What Ripio does with it depends on your company:
  • If you are a regulated entity — a company obligated to verify its customers’ identity under anti-money laundering (AML) regulations — you have already verified your users. Ripio stores the data you submit and the KYC is approved right away.
  • If you are not a regulated entity, Ripio processes the data and asks the user to complete an ID document upload and a liveness check with the identity provider.
Ripio sets the flow up when it configures your account, based on your company. You don’t choose it per request.
This page covers the API integration. In the Crypto Widget, you send the user’s data when opening the widget — see User verification (KYC).

​
The two flows

KYC for regulated entities

You submit the data of users you already verified. The KYC is approved in the same request.

KYC with liveness check

You submit the data, and the user completes a document upload and liveness check on Ripio’s KYC platform.

​
How they compare

You can always tell which flow ran from the response: a provider_url means the user still has to verify their identity.

​
Where KYC fits in the flow

  1. Create the end user.
  2. Get the fields required for your account’s country with KYC Requirements.
  3. Submit the KYC with Create KYC Submission.
  4. Once the KYC is approved, the user can trade, withdraw and use Banking as a Service. An operation for a user whose KYC is not approved answers 20030.
A user can have only one approved KYC. Submitting a new one for a user that is already approved answers 400 with code 20031.