Subscription
Payment Deduction Notification
Callback when a subscription deduction attempt completes (payment / deduction notification).
WEBHOOK
Overview
This page documentswebhook subscriptionOrderPaymentWebhook. The full schema, parameters, and examples are rendered from the linked OpenAPI or webhook definition above.
After a subscription billing cycle completes, GatePay sends an asynchronous notification to the merchant-configured callback URL. Depending on the payment channel, bizType may be SUBSCRIPTION_PAYMENT (Web3 on-chain deduction) or ACCOUNT_AUTH_DEDUCTION (Gate account authorized deduction).
Notes
- Use
bizId,paymentOrderNo, ordeductOrderNofor idempotency after parsingdata. - Signature verification, retries, parsing
data, and the success response are covered in Notifications Overview; see Security and Signature for signing rules.
When notifications are sent
- GatePay sends a notification after each subscription billing cycle completes (success or failure)
- If delivery fails, GatePay retries according to Notifications overview
- Use Deduction order detail as a query fallback when needed
Message structure
bizStatus values
data fields (bizType=SUBSCRIPTION_PAYMENT)
data fields (bizType=ACCOUNT_AUTH_DEDUCTION)
Callback examples
Web3 deduction success (bizType=SUBSCRIPTION_PAYMENT)
Authorized payment deduction success (bizType=ACCOUNT_AUTH_DEDUCTION)
Authorized payment deduction failed (bizType=ACCOUNT_AUTH_DEDUCTION)
Body
application/json
Subscription order deduction notification parameters POST method
Business type: SUBSCRIPTION_PAYMENT — subscription payment deduction notification; ACCOUNT_AUTH_DEDUCTION — authorized payment deduction notification.
Business status: SUCCESS for successful SUBSCRIPTION_PAYMENT; DEDUCT_SUCCESS / DEDUCT_FAILED for ACCOUNT_AUTH_DEDUCTION.
Deduction details as a JSON string; fields vary by bizType.
Deduction order ID (for SUBSCRIPTION_PAYMENT, usually paymentOrderNo).

