> For the complete documentation index, see [llms.txt](https://docs.finpay.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.finpay.id/finpay-pg/after-payment/notification-handle.md).

# Notification Handle

Best Practice to Handle Notification :

1. Use an HTTPS endpoint at all times. Since we verify the certificates match the hosts, it is safe and cannot be the target of Man-in-the-Middle (MITM) attacks. Self-signed certificates should not be used.
2. Notification should always be implemented idempotently. We might occasionally send out two or more notifications for the same transaction occurrence. Using Order ID as the key to track the entries is a straightforward method of ensuring that there are no duplicate entries on the merchant end.
3. Although we work hard to deliver notifications as soon as a transaction is completed, in the very unusual event that you experience delays, please utilize the Check Status API to find out the transaction's current status. To view the most recent transaction status, you may also utilize the Check Status API for any usecase.
4. We have 30 seconds set as the HTTP timeout. It is generally advised to keep the response time of your HTTP notifications to less than 5 seconds.
5. The body of the notice is sent as JSON; use a JSON parser to interpret the JSON. It is advisable to parse the notification body in a non-strict format, as new fields are likely to be added. This will ensure that the parser does not throw an exception when it encounters new fields. It ought should politely overlook the newly added fields. This keeps our older clients intact while expanding our notification system for more recent use cases.
6. Whenever possible, reply to notifications with the appropriate HTTP Status code. Retries for error scenarios are handled differently depending on the status code:
   * for 2xx: No need for tries, it's deemed successful
   * for 5xx : We will retry 5 times with interval 1 minute, 5 minutes, 15 minutes, 30 minutes, and 1 hour


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.finpay.id/finpay-pg/after-payment/notification-handle.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.