Authorizations
Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>
.
Path Parameters
Unique identifier for the customer.
Response
KYC approved in Ripio and OTP sent.
"kyc approved. Otp sent"
Checks the customer’s KYC status with Ripio to determine if they can be fast-tracked through onboarding.
If the customer has a previously approved KYC with Ripio, this endpoint sends a One-Time Password (OTP) to their email. You can then use the POST /customers/{customerId}/otp/
endpoint to validate the OTP and instantly approve the customer’s KYC with your service, skipping the full data submission process.
If the customer’s KYC is not approved with Ripio (indicated by a KycNotApprovedException
), you must guide them through the standard KYC process. This involves retrieving the required fields via GET /kycRequirements/
and submitting their data using POST /customers/{customerId}/kyc/
.
If the customer’s KYC has already been approved with your service, a KycAlreadyApprovedException
will be returned.
Access token obtained via /oauth2/token/. Use as Authorization: Bearer <access_token>
.
Unique identifier for the customer.
KYC approved in Ripio and OTP sent.
"kyc approved. Otp sent"