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

Direct Deposit to Permanent Address Webhook Notification

CCPayment will post the Webhook notification when the permanent address has received the payment.

PreviousAPI Deposit Webhook NotificationNextInvocie Webhook Notification

Last updated 1 year ago

Webhook notification

There are three transaction statuses in the webhook notification under the field name “pay_status”. CCPayment will credit assets if the pay_status is “success”, which is the one and only status you should consider as the confirmation of the transaction. The other two pay_status, “pending” and “processing”, can not be regarded as the confirmation of the transaction.

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": "Direct Deposit",
	"record_id": "202307191012191681607895159656448",
	"paid_amount": "666",
	"credit_amount": "665.8002",
	"chain": "BSC",
	"from_address": "0x3E89fcC505xxxxxx6AA4b78fecB3b2d2D8",
	"to_address": "0x3E89fcC5050bCEc6xxxxxx096F386AA4b78f",
	"contract": "0x55d398326f99059ff775485246999027b3197955",
	"crypto": "USDT",
	"txid": "internal transfer",
	"service_fee": "0.1998",
	"memo": "",
	"user_id": "10192128173"
}
```
Name
Type
Description

pay_status

string

Payment status: pending, processing, success, failed pending: The transaction started, it is waiting to be sent out to the blockchain. processing: It’s being processed on the blockchain.

order_type

string

Direct Deposit

record_id

string

Trading record: one transaction generates one unique record_id

paid_amount

string

Received amount

service_fee

string

Service fee charged by CCPayment

credit_amount

string

Amount credited to merchant's account credit_amount=paid_amount-service_fee

chain

string

Chain for this transaction

contract

string

Contract

crypto

string

Crypto symbol

from_address

string

Sending address of the payment

to_address

string

Permanent deposit address for users

memo

string

Memo/tag; unique identification for address

txid

string

Txid

user_id

string

The unique user id of this address

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.

The direct deposit webhook notification was only posted the token configured by the merchant was deposited.

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