Refund Webhook Notification
CCpayment will post the webhook notification when the merchant refund order on the dashboard.
Last updated
CCpayment will post the webhook notification when the merchant refund order on the dashboard.
Last updated
Name | Value | Required | Type | Description |
---|---|---|---|---|
Once the merchant has processed the order, please return {http code: 200} and include a “success” string in the HTTP response body.
If CCPayment does not receive “success” as a response from the merchant, CCPayment will keep pushing the notification up to 6 times. Any response other than “success” will be regarded as a failure, and CCPayment will keep sending the notification.
Example
Due to scarce objective reasons, merchants may occasionally fail to receive webhook notifications. But such cases are extremely rare. If it involves a refund order, it is recommended that merchants confirm the actual notification delivery status first through the Order Information Interface API or the Webhook Notification Log to avoid misjudgment caused by missing notifications.
Name | Type | Description |
---|---|---|
pay_status
string
Payment status: success, failed
order_type
string
Refund
record_id
string
Trading record: one transaction generates one unique record_id
amount
string
Withdrawal amount, the amount will be deducted from the merchant account.
network_fee
string
Network fee
network_crypto
string
Token name of network fee.
network_coin_id
string
Coin ID for network fee crypto.
net_receivable
string
Net receivable= withdrawal amount- network fee
chain
string
Chain for this transaction
contract
string
Contract
crypto
string
Crypto symbol
to_address
string
Destination address of withdrawal
memo
string
Memo/tag; unique identification for address
txid
string
Txid
merchant_order_id
string
Order ID in Merchant's system. A unique ID for every order
Content-Type
Y
string
application/json; charset=utf-8
Appid
202302010636261620672405236006912
Y
string
Merchant's unique credential. Find it on the Developer page.
Timestamp
1677152490
Y
string
Timestamp in seconds (10-digit). The request is valid for two minutes.
Sign
871f0223c66ea72435208d03603a0cb00b90f6ac4a4ba725d00164d967e291f6
Y
string
SHA-256 (appId + appSecret + timestamp+body (json string))