> For the complete documentation index, see [llms.txt](https://docs.ccpayment.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ccpayment.com/faq/webhook-notification/how-to-receive-the-transaction-notification.md).

# How to receive the transaction notification

As usual, CCPayment will post transaction notification to the ***merchant webhook URL*** when the received payment success. \
But also, you can adjust the webhook notification posting occasion on the merchant setting if you want to receive the notification when the transaction is made.

<figure><img src="/files/zQFiliV3dlKkbn3uigEg" alt=""><figcaption></figcaption></figure>

* **Transaction started:** The system will send a webhook notification instantly when the transaction starts, and upon it detects new transaction and will notify again when the transaction was sent/confirmed on the blockchain.
* **Transaction processing:** The system will send a webhook notification instantly upon the transaction was processing and will notify again when it is confirmed on the blockchain.
* **Transaction confirmed:** The notification is only posted when the transaction has been confirmed.

<figure><img src="/files/CWo3GsYprWGK9pqXjzZ4" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
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.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.ccpayment.com/faq/webhook-notification/how-to-receive-the-transaction-notification.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
