Skip to main content
Not sure which flow applies to your account? Start with Overview & which flow applies.

​
How it works

This is the flow for partners that are regulated entities: companies obligated to verify their customers’ identity under anti-money laundering (AML) regulations. You have already verified your users with your own process, so there is no extra step for them. You submit their data, Ripio stores it, and the KYC is approved in the same request. You remain responsible for the verification you performed. Make sure the data you submit is the data you verified.

​
The flow

1

Get the KYC requirements

Call KYC Requirements to get the fields required for your account’s country. You only need to do this once, while integrating.
2

Create the KYC Submission

Call Create KYC Submission with the user’s email and the kyc_submission data. The response already comes back approved:
Response
provider_url is null: the user doesn’t have to do anything else.
3

Let the user operate

With the KYC approved, the user can trade, withdraw and use Banking as a Service.
The result is in the response itself, so don’t wait for a webhook to continue: depending on your account’s configuration, a KYC.COMPLETED notification may not be sent in this flow. You can always check a submission with Retrieve KYC Submission.
A user can have only one approved KYC. Submitting a new one for a user that is already approved answers 400 with code 20031.