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
  • Webhook notification resend API
  • Resend webhook notifications for a specified time period
  1. CCPayment v1.0 API
  2. Webhook Notification

Resend Webhook Notification

Resend confirmed transaction webhook notifications for a specified time period.

PreviousRefund Webhook NotificationNextChange Record

Last updated 1 year ago

The webhook notification resend API is intended for specific and necessary use cases, such as retrieving missed notifications or ensuring data integrity. Misusing this API by excessively requesting resends may result in disruptions to your merchant account and impact our services.

If you need to resend a webhook notification for development and debugging purposes, it is recommended to use the webhook resend functionality on .

Webhook notification resend API

The maximum request frequency for this API is set at once per minute, with a daily limit of 25 calls.

Resend webhook notifications for a specified time period

POST https://admin.ccpayment.com/ccpayment/v1/webhook/resend

Headers

Name
Type
Description

Sign*

String

Timestamp*

String

Timestamp in seconds (10-digit). The request is valid for two minutes.

Appid*

String

Content-Type*

String

application/json; charset=utf-8

Request Body

Name
Type
Description

start_timestamp*

Int

Specifies the start time for webhook notification sending. Timestamp in seconds (10-digit)

end_timestamp

Int

Specifies the end time for webhook notification sending. Timestamp in seconds (10-digit) If "endTimestamp" is empty CCPayment will resend webhook notifications within a one-hour window based on the start time. The duration between the end timestamp and the start timestamp must not exceed one hour.

webhook_result

String

Pass “Failed”. (default if not provided) If you want to resend all the failed webhook notification of transactions in a specific time frame Pass “All Result”. If you want to resend webhook notification of all transactions in a specific time frame

transaction_type

String

Specifies the type of transactions for which webhook notifications should be sent. - All Type (default if not provided) - Direct Deposit - API Deposit - Invoice - API Withdrawal - Refund

Response (Success 200)

Header

Name
Value
Required
Type
Description

Appid

202302010636261620672405236006912

Y

String

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

{
	"code": 10000,
	"msg": "success",
	"data": {
		"resend_count": "12345",
	}
}

Parameters

Name
Value
Required
Type
Description

code

10000

Integer

msg

success

String

data

Object

data.resend_count

0

Int

Quantity of webhook notifications that were resent during the requested timeframe.

Response (Fail 200)

{
	"code": 224066,
	"msg": "Service error, pleaser try again",
	"data": null
}
Name
Value
Required
Type
Description

code

224066

Number

msg

Service error, please try again

String

data

Object

As a security measure, we will sign the returned data (and according to this only { code: 10000 } should be signed, but it's signing all the returned body.). Additionally, it will 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.

Please note that CCPayment closely monitors the usage of the webhook notification resend API.

If your system requires a significant number of webhook notification resends, we kindly request you to inform the CCPayment team in order to avoid any mistaken categorization of your merchant account as an abuser.

SHA-256 (APPID + APP Secret +timestamp+body (json string)). .

Merchant's unique credential. Find it on the

Merchant's unique credential. Find it on the

webhook page
Signature guide
Developer page
Developer page