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.
B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
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
Created
The response is of type object
.
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.
B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:
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
Created
The response is of type object
.