> For the complete documentation index, see [llms.txt](https://docs.faspay.co.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.faspay.co.id/merchant-page-reference/transactions/notification.md).
# Notification
## Ge**tting Started**
You can access notification history of your transactions by following these steps:
1. On transaction page, click **Notification**.
2. As default, it will show notification history of your transactions in the last 30 days.
## Renotif Transaction Status
You can resend notification status of your transactions, as follows:
1. Checklist the transactions.
2. Click **Renotif.**
3. Click **Yes**, to confirm.
## Adjust Transactions Status
You can adjust the status of your transactions that have not been processed yet to either Success or Cancel.
1. Click **Adjust Status.**
2. Click on one of the Transaction ID.
3. Input Payment Total, Payment Date and Payment Status, then **Submit.**
## Searching Notification History
You can search notification history in 5 ways, including:
* by Transaction ID
* by Merchant ID
* by Billing No
* by Billing Date
* by Status
To search the Notification History it can be done by:
* **Input the keyword** based on the data that you want to show**,** then click **Enter.**
* **Click** the **dropdown button, choose one from the options**.
---
# 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.faspay.co.id/merchant-page-reference/transactions/notification.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.