5.3.1 Reverse signature verification for withdrawals

#Brief description: When a user initiates a withdrawal request, the merchant platform will generate a signature data (such as a transaction order) and send it to the background for processing. In order to ensure that the data has not been tampered with and that the source of the request is legitimate and trustworthy, the backend needs to perform a "reverse signature verification" operation on the request content.

Reverse signature verification settings: Merchants need to log in to the merchant backend to set up by themselves (please obtain login information from the operation staff) as shown below:


Step instructions

1. Merchant logs into the merchant backend
2. Click Merchant Management in the navigation bar
3. Click Merchant Settings
4. Click to turn on the API switch, enter the custom request URL and key, and save it.

Request Description

• Request method: POST
• Request interface: provided by the merchant
• Request media type (JSON data format)Content-Type: application/json

Note: If the merchant has not turned on API security, there is no need to process this business. (Must See)

Request parameters

Parameter name	Type	Required	Parameter meaning	Parameter description
key	string	Yes	Merchant key	apiKey
localOrderId	string	Yes	Merchant platform local order number	Merchant platform generates unique order number locally
localUserId	string	No	Merchant platform local user ID	Merchant platform local user ID
amount	number	Yes	Order Amount	Withdrawal Amount
network	string	Yes	Mainnet	Mainnet (currently only supports TRON, BSC, POLYGON, ETHEREUM)
address	string	Yes	Withdrawal Address	Withdrawal Address
notifyUrl	string	No	Callback address	After the order is successfully placed, the merchant's address will be notified by API callback | (For callback details, please refer to Document 3)
nonce	string	Yes	Random string	Random string
currency	string	Yes	Currency	Currency (wallet supports digital currencies)
successRedirectUrl	string	No	Address	Automatically jump to the address after success
isBlockchain	boolean	No	Whether to return blockchain information (default false)	When true, the callback request will carry the transaction information on the order chain

Request json sample

{
  "amount": 30,
  "isBlockchain": true,
  "address": "TPutFhYUQnrRxHSmKVwjp55vgk9QY6r5nS",
  "merchantId": 303675535978,
  "notifyUrl": "http://conan.test/notify",
  "currency": "USDT",
  "localOrderId": "CONAN-9999",
  "merchantCurrency": "USDT",
  "nonce": "MapDwK",
  "key": "dNNTJZpgFVWlYrVv",
  "network": "TRON"
}

Note: The system request (merchant reverse signature verification path) parameters are consistent with the merchant withdrawal request parameters. (Must See)

Response Example

 "2b703624f24962f5a12d5d1f7569447a"

Response result description: The response is an encrypted string, which is an encrypted string generated by encrypting the request parameters and the merchant's customized reverse signature verification key (for the encryption algorithm, please refer to Document 2 How to Sign). (Must See)