> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/payments-ecosystem/how-to-send-message-or-run-bot-flow-once-a-payment-is-successful.md).

# How to Send Message Or Run Bot Flow Once A Payment is Successful ?

To send a success message when a payment is received in the payments system, create a bot flow:

1. Select the trigger as **WhatsApp chatbot** and the **payment received** option.
2. Choose your channel and go to the option of **send message**.
3. Select the option of **order status message** and enter the content `"Payment is successful"`.
4. Add other details like **payment amount**, **payment currency**, and **payment reference ID**.
5. In the next step, select the option of **add automation app** and choose the option of **payments**.
6. Select the option of **fetch payment order** and in the **reference ID** field, select the option of **payment reference ID**.
7. Click on **Save** and add a **router** to create routers and send separate messages or questions to the user based on the inclusions of the payment order message.

{% embed url="<https://youtu.be/hXnBR6JXB7E>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/payments-ecosystem/how-to-send-message-or-run-bot-flow-once-a-payment-is-successful.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.