Home
chevron_right
API Keys
chevron_right
KYC Integration
Base URL
https://api-dev-services.alfredpay.app/api/v1/third-party-service
API Key
alfredpay.4dqd$jKwSpjnPT!J3U!QsL&7TfAQKPJa
This is only for example purposes, you will be assigned an unique API KEY
API Secret
M992ASr4KnQkvI2)LN3qExWnzNuE2F3*
This is only for example purposes, you will be assigned an unique API SECRET

KYC Full - Share document of the user

We obtain the company registration data and the webview for execute, the balance and user are necessary  for other process

HTTP Request
PUT
https://api-dev-services.alfredpay.app/api/v1/third-party-service/kyc/upload-document
1. --request PUT
2. --url https://api-dev-services.alfredpay.app/api/v1/third-party-service/kyc/upload-document
Input Header
{
"API-key": "YOUR_API_KEY",
"API-secret": "YOUR_API_SECRET",
"Authorization": "YOUR_AUTH-TOKEN",
}
Response
{
"statusCode": 202,
"message": "upload KYC full successful"
}
Form
value docType can be idCardFront, idCardBack, selfie.

Errors

alfred uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed given the information provided (e.g., a required parameter was omitted, a charge failed, etc.).

Some 4xx errors that could be handled programmatically (e.g., a card is declined) include an error code that briefly explains the error reported.

HTTPS STATUS CODE SUMMARY
202 - ACCEPTED
Everything worked as expected.
404 - NOT FOUND
The requested resource doesn't exist.

Considerations

The end point must execute three once per type of document after you can open the widget (url + uid session), the authorization is getting from kyc lite /login-sof-kyc