> For the complete documentation index, see [llms.txt](https://pivot-payment.gitbook.io/pivot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pivot-payment.gitbook.io/pivot-docs/payments/after-the-payment/payment-notify.md).
# Payment Notify
## Create a Callback endpoint
Before handling payment events, you must register the endpoint in the Dashboard so that we can notify you.
Follow these steps:
1. Log in to your Dashboard
2. Navigate to Settings > Choose Developer Setting
3. Go to Callbacks, then register your Payment Callback URLs
4. Return only HTTP Response 200 for registering the Callback URLs
## Create a payment event handler
You need to create a handler in your server to receive and process incoming payment event notifications. There are four key event types you need to handle:
| Event Name | Description | Action |
| ------------------ | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| PAYMENT.PROCESSING | The Payment has been initiated and is currently in progress | Update the transaction status in your system to "Processing" or "Pending Payment." |
| PAYMENT.PAID | The payment was successfully completed | Fulfill the order, update the transaction status to "Paid", and notify the customer if needed |
| PAYMENT.CANCELLED | The payment has been cancelled, either by the Customer, system timeout, or manual intervention | Update the transaction status to "Cancelled" or "Failed" and inform the customer if needed |
| CHARGE.SUCCESS | Charge was successfully completed in Multiple Payment Type | Fulfill the order, update the transaction status to "Paid", and notify the customer if needed |
---
# 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://pivot-payment.gitbook.io/pivot-docs/payments/after-the-payment/payment-notify.md?ask=&goal=
```
`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.