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

Webhook Notification Tutorial

PreviousWebhook NotificationNextAPI Deposit Webhook Notification

Last updated 1 year ago

CCPayment will notify your webhook URL of the transaction details of in real-time.

  1. Notification trigger: The CCPayment will notify the transaction's final status to the merchant by default. if you want to be notified when the transaction was detected or was sent to the blockchain, you can adjust the notification setting on the below page to suit your needs.

  1. You can set the configure Webhook URL on the Developer setting page to receive the notification. And part of the interface supports separate configuration via incoming parameters: Notification URL

  1. Once the merchant has processed the order, please return {http code: 200} and include a “success” string in the HTTP response body.

Example

$this->response->setString("success")
this.response.setString("success");
this.response.SetString("success")
self.response.set_string("success")
this.response.setString("success");
  1. If CCPayment does not receive “success” as a response from the merchant, CCPayment will keep pushing the notification up to 7 times. Any response other than “success” will be regarded as a failure, and CCPayment will keep sending the notification.

  2. Notification log: you can view the sent notifications on the webhook log page. You can click "Resend" or "Batch Resend" to push the notification again also.

Note: Different types of transactions have different notification content, and you can distinguish the transaction types according to the type of webhook notification order. (Please check )

the webhook notification of all types of transactions
configured token you set on the merchant settings