Refund Webhook Notification

CCpayment will post the webhook notification when the merchant refund order on the dashboard.

Webhook notification

Header

Name	Value	Required	Type	Description
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))

Body

```json
{
  "pay_status": "success",
  "order_type": "Refund",
  "record_id": "202307310544361685889174073212928",
  "amount": "1",
  "net_receivable": "1",
  "network_fee": "0",
  "network_crypto": "USDT",
  "network_coin_id": "8e5741cf-6e51-4892-9d04-3d40e1dd0128",
  "chain": "ETH",
  "contract": "0xdAC17F958D2ee523a2206206994597C13D831ec7",
  "crypto": "USDT",
  "to_address": "0xA9F422BFBeB46f1FbcBBaf947E15b84D8Fbba80C",
  "memo": "",
  "txid": "internal transfer",
  "merchant_order_id": "test_xxxx1688370383377840"
}
```

Parameters

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

Remarks

Return Appid, Sign, Timestamp in the header of the response. The signature method SHA-256 (appid+appSecret+Timestamp+body).

Please use the data with caution if the signature verification fails. It indicates that the data has been tampered with.

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

PHP

$this->response->setString("success")

Java

this.response.setString("success");

Golong

this.response.SetString("success")

Python

self.response.set_string("success")

Node.js

this.response.setString("success");

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.