Create KYC Submission
This endpoint allows you to submit user’s kyc information.
This endpoint behaves asynchronously, don’t expect the KYC Submission to be approved after the request execution. To check for its completion, use the Retrieve KYC Submission endpoint. When the verification submission is completed, a webhook will be sent. See BaaS Webhooks in the documentation.
Authorizations
B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
- clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.
Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.
Every request must be accompianed by an Authorization
header with a value that follows the following schema: Bearer ACCESS_TOKEN
Path Parameters
Body
End User's unique email.
Json formatted data with the information detailed on KYC Requirements
Response
KYC Submission unique identifier
KYC Submission status.
COMPLETED
, IN_REVIEW
, FAILED
, UPDATE_REQUIRED
URL to redirect users in order for them upload or fulfill extra information. E.g: ID photo, proof of life, etc. May be null if no further information is required.
ISO format creation datetime
Was this page helpful?