Comment on page
Static wallet
The deposit report is implemented by means of webhooks.
Set the Webhook URL in the menu Merchant\Classic processing\WebhookURL to receive a callback about payment status. Required https (TLS/SSL)
Webhook password - password required to verify the payment signature
Webhook URL - the address in the system from which the payment is made, this address will be used to send updates on the status of payments:
Request method: POST
Response Type: JSON
Parameters:
Name | Description | Type |
|---|---|---|
PaymentId | Transaction ID in the 0Xprocessing system | Integer |
MerchantId | Merchant ID in 0Xprocessing system | String |
ShopId | Merchant ID in 0Xprocessing system | String |
Amount | Payment amount in cryptocurrency | Double |
AmountUSD | Payment amount in USD equivalent | Double |
TotalAmount | Full amount received in the cryptocurrency without fee | Double |
TotalAmountUSD | Full amount received in USD equivalent without fee | Double |
Currency | Payment currency | String |
Email | Not used for this method | String |
Status | Payment status Possible values are: Success - payment has been executed successfully | String |
BillingID | Not used for this method | String |
Signature | Checksum to verify the authenticity of the request (to ensure that the request came from 0Xprocessing) | String |
Insufficient | Not used for this method | Boolean |
ClientId | Unique client ID in your system | String |
TxHashes | Successful transaction hash | String |
Signature check:
1. A string of the following form must be generated: "PaymentId":"MerchantID":"Email":"Currency":"Password" (WebhookURL link password)
Without quotation marks through a colon.
Example: 12345:Qtfxhgy43:[email protected]:USDT (ERC20):qwerty
2. Encrypt the resulting string using MD5 algorithm
3. Compare the resulting string with the one that came through Webhook
"Signature":"a5510c8c3e657ffd8229813749cd20ec"
4. If the strings are the same, return HTTP Status 200 (Required)
If the callback is not delivered successfully, the system repeats at 31 times with an interval of 15 seconds. If the webhook still fails to be delivered, the system sends a notification to the merchant's account email indicating a problem with the WebhookURL.
Example Webhook JSON:
1
{
2
"PaymentId":10453,
3
"MerchantId":"Asv0232SSd",
4
"Amount":0.00264765,
5
"TotalAmount":0.00264765,
6
"Currency":"BTC",
7
"Email":"null",
8
"Status":"Success",
9
"Signature":"a5510c8c3e657ffd8229813749cd20ec",
10
"BillingID":"null",
11
"AmountUSD":115.0,
12
"TotalAmountUSD":115.0,
13
"Insufficient":false,
14
"Test":false,
15
"ClientId": "1000",
16
"TxHashes":["0e61e33a0c02204c41ac210c2fcffda4bea4399792acc49479aa8374465ef63a"]
17
}
When processing callbacks, you MUST use the PaymentId parameter from the callback 0xProcessing as an additional validation factor.
Last modified 3d ago