> For the complete documentation index, see [llms.txt](https://docs.360dialog.com/partner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.360dialog.com/partner/messaging/commerce-and-payments.md).

# Commerce & Payments

The WhatsApp Payments API enables businesses in India and Brazil to collect payments seamlessly directly within the WhatsApp chat thread. By integrating local payment ecosystem features such as UPI in India and Pix or Boleto processing in Brazil, businesses can deliver an end-to-end conversational checkout experience. This reduces drop-off rates, simplifies transaction flows, and keeps the customer purchasing journey within a single messaging interface.

{% content-ref url="/pages/96cE1LLbs04Sj4AWPyaz" %}
[Payments API Brazil](/partner/messaging/commerce-and-payments/payments-api-brazil.md)
{% endcontent-ref %}

{% content-ref url="/pages/DaWFICuRrnBbFyZzC0Ha" %}
[Payments (India Only)](/partner/messaging/commerce-and-payments/payments-india-only.md)
{% endcontent-ref %}

{% content-ref url="/pages/FPU8NKp0nmT5Zm3NJobR" %}
[Payments (Singapore Only)](/partner/messaging/commerce-and-payments/payments-singapore-only.md)
{% endcontent-ref %}

{% content-ref url="/pages/UUCEXFsixDqx0GRzJrhy" %}
[Products and Catalogs](/partner/messaging/commerce-and-payments/products-and-catalogs.md)
{% endcontent-ref %}


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.360dialog.com/partner/messaging/commerce-and-payments.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 `build a script that syncs our docs to a CMS` 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.