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
Push ID.
Push action, see [Appendix - Constants] Push Actions.
Push data.
data
Consumption order number
Consumption related order number
Card order number
Cardholder order number
Consumption type, see [Appendix - Constants] Consumption Type
Consumption amount (BigDecimal)
Original amount
Original currency
Total fee (sum of all
amount values in fee_detail)Remarks (from consumption extension info)
Description (from consumption extension info)
Fee detail list (field name is
fee_detail, not fee_list)Merchant information
Status, see [Appendix - Constants] Common Status
Consumption update time (Unix milliseconds, uses record
mtime)fee_detail Fields
Fee type, see [Appendix - Constants] Fee Types
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
Merchant name
Merchant MCC
Merchant city
Merchant country
Merchant Response
Response code.
0 indicates success.Failure reason, required when failing.
