CCPayment
Have Questions?TwitterMediumBlog
  • CCPayment - For Merchant
    • What is CCPayment
    • CCPayment API Introduction
    • Fees
    • Invoice
    • Contact Us
  • CCPayment v1.0 API
    • SDK Libraries
    • To Get Started
      • Signature
      • API Specification Common Rules
    • Payment API - CCPayment
      • Hosted Checkout Page Integration
      • Native Checkout Integration
      • API Deposit Order Information Interface
    • Wallet API - CCPayment
      • Get permanent deposit address for users
    • Withdrawal API Integration
      • Create a withdrawal order
      • Withdrawal Order Information Interface
    • Resources Document
      • Token ID Interface
      • Current Token Rate Interface
      • Asset Balance Interface
      • Network Fee Interface
      • Block Height Information Retrieval API
      • Check the Validity of Cwallet ID
      • List of Supported Coins
      • List of Denominated Currency for API Payment
      • Error Code
    • Webhook Notification
      • Webhook Notification Tutorial
      • API Deposit Webhook Notification
      • Direct Deposit to Permanent Address Webhook Notification
      • Invocie Webhook Notification
      • Withdraw Webhook Notification
      • Refund Webhook Notification
      • Resend Webhook Notification
  • Changes
    • Change Record
    • Upcoming Changes
  • FAQ
    • FAQ
    • Webhook Notification
      • How to receive the transaction notification
      • Why do some deposit transactions not include the “from address” in the webhook notification?
    • Payment
      • Why hasn't my transactions been confirmed?
      • Why hasn't my withdrawal arrived
      • Minimum amount of withdrawal and deposit
      • How to find out withdrawal fees for each cryptocurrency?
      • How does CCPayment charge the service fee
      • After payment has been paid, why does the order status not appear successful
      • What types of tokens do we accept for payment
      • How long does it take for a withdrawal to be processed
      • When a payment is not sufficiently made, can the user make it again and have it credited correctly
      • Is it possible to pay by credit card
      • What is token aggregation fee?
    • Security & Privacy
      • How to Secure My CCPayment Account
      • What information do you collect about my customers
      • Is my website required to be reviewed when using CCPayment API
      • Why can’t I get the email verification code?
      • Verify your site ownership
        • Verify your site ownership with HTML file
        • Verify your site ownership with HTML tag
    • Refund
      • How to cancel a pending refund request
      • How does the merchant issue a refund to the customer
      • What should you do if you entered a wrong memo/tag?
      • What should you do if you credited to CCPayment's unsupported tokens?
    • Others & Academy
      • How to manage multiple merchant account
      • How does the lock exchange rate of an order work and what happens when it is locked
      • What is the transaction under the category Other in the transaction records
      • Are there any regional restrictions on API use
      • What is a referral program?
      • CCPayment ETH Testnet Tutorial
      • What is auto-swap for deposit?
  • CCPAYMENT POLICY
    • CCPayment Privacy Policy
    • Disclaimer for Purchasers
    • Terms of Use
    • AML/CTF Policy
Powered by GitBook
On this page
  1. CCPayment v1.0 API
  2. Webhook Notification

Refund Webhook Notification

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

PreviousWithdraw Webhook NotificationNextResend Webhook Notification

Last updated 1 year ago

Webhook notification

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))

```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"
}
```
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

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

$this->response->setString("success")
this.response.setString("success");
this.response.SetString("success")
self.response.set_string("success")
this.response.setString("success");
Response 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 API or the to avoid misjudgment caused by missing notifications.

Order Information Interface
Webhook Notification Log