{
  "business": 0,
  "requestUUID": "f56d2814-7a8f-4dcf-9008-990c1be6e13e",
  "tenantUserId": "bbxuzbc",
  "callBackId": "D611657466",
  "type": 2,
  "trackingId": "102004"
}

{
  "apiKey": "88c47568-8d24-4983-9b4c-y1ec8b939e9b",
  "data": "{\"tenantUserId\":\"ryan_test_2\",\"callBackId\":\"D682988196\",\"address\":\"TGDHyoMpgDQj4DmoZdwJP2FSkSG4DEchnK\",\"chainName\":\"TRON\",\"symbol\":\"USDT\",\"amount\":\"3.3\",\"type\":2}"
  "errCode": 0,
  "message": ""
}

NOTIFY_REQUEST_WITHDRAW (type=2)

When a user initiates a withdrawal request (requiring secondary confirmation), WaaS will request the merchant to perform secondary confirmation through this interface. The merchant needs to return specific withdrawal information in the response, which will determine whether WaaS executes the withdrawal operation.

​
⚠️ Special Requirements

  1. Independent URL: Requires separate configuration for this type of callback URL

​
Request Parameters

The request sent by WaaS is an RSA-encrypted Base64 string. Merchants need to decrypt it using their public key:

​
Withdrawal Secondary Confirmation Request Parameters
object

​
Response Parameters

After processing the callback, merchants need to return a JSON-formatted response body. The data field must return an RSA-encrypted Base64 string (encrypted using the public key provided by WaaS), while other fields are in plain text:

​
Withdrawal Callback Response Parameters
object
{
  "business": 0,
  "requestUUID": "f56d2814-7a8f-4dcf-9008-990c1be6e13e",
  "tenantUserId": "bbxuzbc",
  "callBackId": "D611657466",
  "type": 2,
  "trackingId": "102004"
}

{
  "apiKey": "88c47568-8d24-4983-9b4c-y1ec8b939e9b",
  "data": "{\"tenantUserId\":\"ryan_test_2\",\"callBackId\":\"D682988196\",\"address\":\"TGDHyoMpgDQj4DmoZdwJP2FSkSG4DEchnK\",\"chainName\":\"TRON\",\"symbol\":\"USDT\",\"amount\":\"3.3\",\"type\":2}"
  "errCode": 0,
  "message": ""
}