Skip to main content
WEBHOOK

Overview

This page documents webhook unresolvedPayWebhook. 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.

Message Structure

data Field Reference

Callback Example

Body

application/json

Unresolved payment webhook payload

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.