KYC Webhook
Introduction
When the user’s KYC result is received from the card issuer, it will be sent to the callbackUrl provided during the KYC Registration request. The merchant can use this callback to confirm the user’s KYC status.
After merchant received webhook, response HTTP code 200 for success or ACH will retry.
Merchant can also call Query KYC status api for confirming.
API Description
Request Method: POST
Request Path: /**/callback
Response Parameters
Model Entity Description
| Parameter | Type | Description |
|---|---|---|
| userNo | string | User number |
| string | User email | |
| kycStatus | string | kyc status |
| kycStartTime | string | kyc start time |
| callbackUrl | string | kyc success webhook url |
| redirectUrl | string | kyc success redirect url |
KYC Webhook Description
Parameter | Description |
|---|---|
COMPLETED | KYC COMPLETED |
REJECTED | KYC was submitted but rejected by the compliance department. |
Response Parameter Example:
{
"userNo": "500417494499129131050",
"email": "[email protected]",
"kycStatus": "COMPLETED",
"kycStartTime": "2025-06-09 17:41:53",
"redirectUrl": "https://card.alchemypay.org/web3auth",
"callbackUrl": "https://card-api.alchemypay.org/kyc/callback"
}Updated 25 days ago