1. Create order request
Business Description: The interface needs to take the initiative to configure the callback url to provide the callback order number, the callback url, and the jump url, we actively initiates an order request, then make a callback notification. If the corresponding callback function is not configured , corresponding orders will be generated according to our rules.
Actively request data：
| field | type | nickname | description |
|---|---|---|---|
| amount | Integer | deposit amount | Amount deposit by the user |
| userWalletAddress | String | Wallet Address | User's wallet address |
| remarks | String | Remarks | |
| merchUserId | String | The merchant’s user ID | can be passed by your company when recharging |
| merchName | String | Merchant name | |
| sign | String | sign | sign |
Return data results：
| field | type | nickname | description | |
|---|---|---|---|---|
| code | Integer | status code | 0 means the request is normal | |
| message | String | message | ||
| data | Return data | table below | table below |
data：
| field | type | nickname | description |
|---|---|---|---|
| merchOrderId | String | Merchant’s order number | |
| callBackUrl | String | Merchant Customized Callback Interface | For details, please see the user’s order result notification. |
| merchUserId | String | Merchant's User ID | Merchant's User ID（unique value） |
Verify sign rules：
1.Simplify the information in the form except sign into map key-value pairs
2.Sort the key-value pairs in positive order by the name of the key
`Sorting Alphabetically would be example: `Before sorting: merchUserId => “user0000005”
address => “address00000005"
After sorting: address => “address00000005"
merchUserId => “user0000005”
3.Encode into get request format in the sorted order
example:address=address00000005&merchUserId=user0000005
`4.Splice the md5key string from the merchant information directly after the get request string to get the signature source. `For example, the md5key value is merchmd5Key
example:address=address00000005&merchUserId=user0000005merchmd5Key
5.The result of step 4 is md5 encrypted to get the final signature value ownSign
6.Verify whether the received sign is the same as the self-calculated signature value ownSign. If they are the same, it is a trusted notification request.