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?
| Ripio-hosted (redirect) | Partner-submitted (API) | |
|---|---|---|
| Who collects the data | Ripio | You (the partner) |
| User experience | User leaves your UI to Ripio’s KYC page | Fully native in your UI |
| Integration effort | Lower | Higher |
| Best for | Getting live quickly | Custom, embedded onboarding |
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).Where KYC fits in the flow
KYC happens after creating the customer and accepting the Terms & Conditions, and before creating any order:KYC statuses
| Status | Meaning |
|---|---|
INCOMPLETE_USER_DATA | Required information is still missing (or a pending step, such as OTP validation, hasn’t been completed). Provide the missing data to continue. |
IN_REVIEW | Submitted and under review. |
UPDATE_REQUIRED | Some information must be corrected or updated before the KYC can be approved. |
COMPLETED | Approved — the customer can operate. |
FAILED | Rejected. |