Submits KYC data for a specific customer. The response will include a URL to a third-party KYC provider’s widget for document uploads and liveness checks. Webhook events will notify about the validation process.
Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>.
Unique identifier for the customer.
KYC data for the customer. Structure should align with fields from /kycRequirements/.
Request body for KYC submission. Use kycSubmission + redirectUrl for the standard API flow, or only redirectUrl for the Ripio KYC delegated flow.
Customer KYC data. Fields vary by country — use /kycRequirements/ to get the required fields for the customer's country. Not required when using the Ripio KYC delegated flow.
URL to redirect the user after completing the KYC flow. Required for the Ripio KYC delegated flow; optional for the API flow.
"https://www.example.com/"
KYC submission received successfully. Includes providerUrl for document upload and liveness check.
Unique identifier for the submitted KYC data.
Date and time the KYC submission was created (UTC format).
Points to a third-party KYC provider's widget to handle file uploads and liveness checks. Only available in production.