When a merchant uses the Request Withdrawal Order (Secondary Confirmation Required) API, the platform will call this callback interface to ask the merchant to confirm the details of the withdrawal order.

This interface is only applicable for callback type 2（NOTIFY_REQUEST_WITHDRAW）。Merchants need to confirm the details of the withdrawal order based on the callback content. Although it shares the same request and response parameter templates as the general Webhook callback interface, the URL for this interface is independent.

​
API Example

  • API Endpoint：https://xxxx/api/v1/uu/withdraw/info

​
Request Method

POST

​
Request Headers

NameTypeRequiredExample ValueDescription
Content-TypestringYesapplication/x-www-form-urlencodedRequest Format: Form-Encoded Format
X-API-KEYstringYesyour-api-keyAuthorization key for authentication.

​
Request Body Parameters

Below is the request body parameter template:

Attribute NameTypeRequiredExample ValueDescription
tenantUserIdStringYestenant123Merchant user identifier.
requestUUIDStringYes2137890Unique identifier for the request.
trackingIdStringYestrack-4567Order tracking ID.
typeIntegerYes2Callback type
businessIntegerYes0Tenant type (no actual control effect currently).
callBackIdStringNo12345Callback ID.
toAddressStringNoTUekuiBgdk...Target address.
chainNameStringNoTRONBlockchain name.
txIdStringNo22e1c72076...Transaction ID.
symbolStringNoUSDTSymbol
amountStringNo0.5Amount
txIndexIntegerNo20Transaction index.
tagStringNoWITHDRAW_SUCCESSSTag
fromAddressStringNoTUekuiBgdk...Source address.
newAddressStringNoTUekuiBgdk...New address (only used when type is 4).
riskLevelFromIntegerNo15Risk score of the source address (exists when type is 1).
riskLevelToIntegerNo15Risk score of the target address (exists when type is 1).

​
Request Example

{
  "tenantUserId": "tenant123",
  "requestUUID": "2137890",
  "trackingId": "track-4567",
  "type": 2,
  "business": 0,
  "callBackId": "12345",
  "toAddress": "TUekuiBgdk...",
  "chainName": "TRON",
  "txId": "22e1c72076...",
  "symbol": "USDT",
  "amount": 0.5,
  "txIndex": 20,
  "tag": "WITHDRAW_SUCCESSS",
  "fromAddress": "TUekuiBgdk...",
  "newAddress": "TUekuiBgdk...",
  "riskLevelFrom": 15,
  "riskLevelTo": 15
}

​
Response Parameters

Attribute NameTypeRequiredExample ValueDescription
requestUUIDStringYes2137890Unique identifier for the request.
userIdStringYes1308764Tenant ID.
createByStringYes“Information about the creator (no actual control effect).
messageStringYes“Description message (no actual control effect).
apiKeyStringYes“apiKey
errCodeintYes“Error code: 0 indicates success; other values indicate failure.
dataStringYes“Encrypted data using an RSA public key.

Below are the descriptions for the data parameter:

Attribute NameTypeExample ValueDescription
requestUUIDString2137890Unique identifier for the request, used to uniquely identify it.
userIdInteger1User ID, identifies the specific user who triggered the event.
trackingIdString track-4567Order tracking ID.
addressStringtoAddress123Target address, indicates the operation’s target address.
tenantUserIdStringtenant123Merchant user identifier, used to differentiate merchant users.
chainNameStringTRONBlockchain name, identifies the blockchain where the transaction occurred.
symbolStringUSDTCurrency symbol, identifies the token or currency involved in the transaction.
callBackIdString12345Callback ID, identifies the current callback event.
amountString0.5Amount, indicates the specific transaction or operation amount.
typeInteger2Callback type, detailed explanation can be found in the callback type

​
Response Example

{
  "requestUUID": "2137890" ,
  "userId": 1,
  "createBy":"xxxx",
  "message": "成功处理请求",
  "apiKey": "your_api_key",
  "errCode": 0,
  "data": {
    "userId": 1,
    "trackingId": "track-4567",
    "address": "toAddress123",
    "tenantUserId": "tenant123",
    "chainName": "TRON",
    "symbol":"USDT",
    "callBackId":"12345",
    "requestUUID": "2137890",
    "amount": 0.5,
    "type": 2,
  }
}

​
Response Parameter — Callback Type Description

  • type:
    • Always 2, indicating the callback type is NOTIFY_REQUEST_WITHDRAW.
    • This callback type is used for merchants to confirm the details of a withdrawal order.
    • Merchants should confirm the withdrawal order details based on the callback content before proceeding with further processing.

​
Notes

  1. Merchants must ensure that the callback interface URL can be accessed normally and returns the correct response; otherwise, the callback may fail.
  2. The platform will retry multiple times in case of callback failure. Merchants need to handle idempotency properly to ensure that the same callback request is not processed multiple times.
  3. The security of the callback interface should be verified using the X-API-KEY. Please keep your key secure to prevent unauthorized access to the interface.