COMPLETED before you can create On-Ramp or Off-Ramp orders.
There are two ways to run KYC. This page helps you pick the right one; each model has its own step-by-step page.
The two models
Ripio-hosted KYC (redirect)
You send the user to Ripio’s KYC platform via a redirect. Ripio collects the data and documents. Simplest to integrate.
Partner-submitted KYC (API)
You collect the KYC fields in your own UI and submit them through the API. Maximum control over the experience.
Which model should you use?
In both models the user is redirected to a third-party provider for document upload and liveness checks. The difference is who collects the personal data beforehand.
Shortcut: reuse an existing Ripio KYC
If the customer already has an approved KYC with Ripio, you don’t need to collect anything — you can verify them with a one-time password (OTP) sent to their email. Always check for this first; it’s the fastest path. This shortcut is documented inside Partner-submitted KYC (API).Shortcut: reuse a KYC from your own Sumsub account
If your customers are already verified in your own Sumsub account, you can share that verification with Ripio instead of running a new one: you send a Sumsub share token when creating the KYC and, when both verifications are compatible, the customer skips the document upload and liveness check. It works on top of either model, and it needs setup on your Sumsub account plus an opt-in from the Ripio team before the first call. See Reusable KYC (Sumsub share token).Where KYC fits in the flow
KYC happens after creating the customer and accepting the Terms & Conditions, and before creating any order:KYC statuses
Instead of polling, you can subscribe to KYC Events to be notified when a customer’s status changes.