Callback Message Transfer
The payment gateway can generate multiple transactions for a single order.\ This may happen due to user input errors or issuer restrictions. For example: * A user may attempt payment several times. * Once restrictions are cleared (e.g., via contacting their bank), the transaction can be retried on the payment gateway page — without being redirected to the merchant. As a result, a single order may be linked to multiple transactions (some failed, one eventually successful).
| Name | Type | Required | Description |
|---|
URL_PARTNER_SYSTEM | string | ✅ | Notification handler endpoint on the partner's side |
| Name | Type | Default | Required | Description |
|---|
id | string | — | ✅ | Transaction ID in the external system |
dt | date | 2000-01-01 00:00:00 | ✖️ | Date/time of the payout operation |
amount | string | 00.00 | ✖️ | Payout amount to be credited |
result | int32 | 0 | ✖️ | Operation status: 0 = fail, 1 = success |
error | string | — | ✖️ | Error message (only if result != 1) |
destination | string | — | ✖️ | Payout destination identifier (see destination list) |
hash | string | — | ✅ | Control signature: md5(id + dt + amount + result + destination + secretKey) |
| Header | Type | Required | Description |
|---|
Content-Type | string | ✅ | Must be application/x-www-form-urlencoded |
