KYC Callback

Tip

• This callback uses POST and the data format is application/json.
• After processing the KYC result, the merchant must respond with plain text OK.

Brief Description

• This document describes the asynchronous callback used to notify merchants of the KYC result.

• If the merchant server has IP restrictions, please inform us in advance.

Request Method

• Method: POST
• Content-Type: application/json

Request Parameters

Parameter	Required	Type	Description
userId	Yes	String	Merchant-side user ID.
authenticationStatus	Yes	String	Authentication status. 0: Pending authentication, 1: Under review, 2: Approved, 3: Rejected. If the status is 3, the merchant needs to submit a new KYC application.
failReason	No	String	Failure reason. This field is returned when authentication fails.
timestamp	Yes	String	Callback timestamp.
sign	Yes	String	Callback signature. Sort all non-empty callback parameters except sign by parameter name in ascending alphabetical order, concatenate them as key1=value1key2=value2, append the app secret, and generate a lowercase MD5 hash.

Request Example

{
  "userId": "79x7p10nh4xd121m",
  "authenticationStatus": "3",
  "failReason": "The file and type do not match",
  "timestamp": 1728609277476,
  "sign": "d41d8cd98f00b204e9800998ecf8427e"
}

Response Parameters

OK