Skip to main content
WEBHOOK
callbackNotification
{
  "main_order": {
    "batch_id": "831618381568",
    "merchant_id": 17329983,
    "status": "SUCCESS",
    "client_id": "igasgasdbub",
    "pay_back_status": "NO",
    "channel_id": ""
  },
  "suborders": [
    {
      "merchant_id": 130559,
      "channel_id": "",
      "suborder_id": "30969031299072",
      "chain": "TRX",
      "address": "QBTW9qTMQBTW9qnoeMMmUxaAWEqVDDUgUw",
      "currency": "USDT",
      "amount": 2362.1,
      "fee": 1,
      "tx_id": "aaa33e642d6fb6e3272ae3c21c60f1248d1cd7ccdc000458308d690699",
      "memo": "",
      "status": "DONE",
      "merchant_withdraw_id": "1839295815",
      "fee_type": 1,
      "batch_withdraw_id": "",
      "desc": "",
      "reconciliation_status": 0,
      "is_placed": 1,
      "finish_time": 1748581414000,
      "sub_amount": 2363.1,
      "done_amount": 2362.1
    }
  ]
}

Documentation Index

Fetch the complete documentation index at: https://docs.gate.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This page documents webhook callbackNotification. The full schema, parameters, and examples are rendered from the linked OpenAPI or webhook definition above.

​
Notes

  • This page describes a callback payload sent by GatePay, not a merchant-initiated request.
  • Verify the signature first, then apply idempotent processing before updating business state.
  • For callback guidance organized by business flow, read this page together with the Notification guide.
  • For shared signing rules, see /api-reference/version/100/en/common/securityAndSignature.

Response

200 - application/json

Returns HTTP 200 to indicate the callback notification has been received.

Data structure for GatePay callback to merchant when withdrawal order status changes, including main order object and suborder array.

​
main_order
object
required

Main withdrawal order information in callback notification.

​
suborders
object[]
required

Suborder callback details array.