Skip to main content
The platform sends a POST request to the configured merchant callback URL when a consumption transaction is created, its status changes, or when fees and merchant information are supplemented.

Trigger Scenarios

  • Consumption transaction created, transaction status changed (success / failure / reversal / refund).
  • After fee breakdown and merchant information are supplemented, proactively push to the merchant callback address.

Push Parameters

string
required
Push ID.
string
required
Push action, see [Appendix - Constants] Push Actions.
object
required
Push data.

data

string
Consumption order number
string
Consumption related order number
string
Card order number
string
Cardholder order number
string
Consumption type, see [Appendix - Constants] Consumption Type
number
Consumption amount (BigDecimal)
number
Original amount
string
Original currency
number
Total fee (sum of all amount values in fee_detail)
string
Remarks (from consumption extension info)
string
Description (from consumption extension info)
array
Fee detail list (field name is fee_detail, not fee_list)
object
Merchant information
string
Status, see [Appendix - Constants] Common Status
number
Consumption update time (Unix milliseconds, uses record mtime)

fee_detail Fields

string
Fee type, see [Appendix - Constants] Fee Types
number
Fee amount
Fee details differ by integration mode:
  • Credit extension mode: Consume_fee, Exchange_fee, Atm_fee / Apple_auth_fee, Small_fee, Decline_fee (only pushed when amount > 0).
  • Authorization mode: Reserve fund side fees, including Consume_fee, Exchange_fee, Apple_auth_fee, Atm_fee, Small_fee, Refund_fee, Cancel_fee.

merchant_info

string
Merchant name
string
Merchant MCC
string
Merchant city
string
Merchant country

Merchant Response

number
required
Response code. 0 indicates success.
string
Failure reason, required when failing.