Skip to main content
WEBHOOK
unresolvedPayNotify
{
  "bizType": "PAY_UNRESOLVED",
  "bizId": "123",
  "bizStatus": "UNRESOLVED_PENDING",
  "data": {
    "exceptionId": "123",
    "orderType": "acquiring_type",
    "errorType": "address_risk_address",
    "originalOrderId": "355450733498011648",
    "expectedAmount": "10.0",
    "expectedChainCurrency": [
      {
        "chain": "TRX",
        "currencies": [
          "USDT"
        ]
      }
    ],
    "actualAmount": "1.0",
    "actualCurrency": "USDT",
    "actualChain": "TRX",
    "customerName": "",
    "toAddress": "TExampleAddressxxxxxxxxxxxxxxxxxx",
    "fromAddress": "TFromAddressxxxxxxxxxxxxxxxxxxxx",
    "hash": "0xabc",
    "updateTime": 1740000000000
  }
}
{
  "returnCode": "SUCCESS",
  "returnMessage": ""
}

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 unresolvedPayNotify. 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.

Body

application/json

Unresolved payment webhook payload (POST)

​
bizType
enum<string>

Business type; always PAY_UNRESOLVED.

Available options:
PAY_UNRESOLVED
​
bizId
string

Business ID (e.g. identifier linked to the exception; actual payload may vary).

​
bizStatus
enum<string>

Business status, e.g. UNRESOLVED_PENDING (pending; actual payload may vary).

Available options:
UNRESOLVED_PENDING
​
data
object

Unresolved payment details. Some fields may be empty depending on acquiring vs payee QR scenarios; see each field description.

Response

200 - application/json

HTTP 200 indicates the merchant successfully received the notification.

Response body returned by the merchant after receiving the notification.

​
returnCode
string
required

Result code; SUCCESS means success.

​
returnMessage
string | null

Message; may be empty on success.