> For the complete documentation index, see [llms.txt](https://help.pickyassist.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.pickyassist.com/whatsapp-commerce/getting-started/connecting-payment-gateway.md).

# Connecting Payment Gateway

{% hint style="warning" %}
**Note: WhatsApp in App support only in India**
{% endhint %}

WhatsApp supports **in-app payments** in India with deep integration into the WhatsApp app. This allows your users to make payments quickly within WhatsApp itself, without being redirected to a browser link. As a result, the payment success rate is higher compared to redirection.

{% embed url="<https://www.youtube.com/watch?v=fGhXy2sE1z4>" %}

In India, WhatsApp in-app payments are supported only with the following payment gateways:

* Razorpay (Recommended)
* PayU
* BillDesk
* ZaakPay

To start collecting payments seamlessly within WhatsApp, your business must have an active payment gateway account with full KYC completed from any of the providers listed above.

## Mandatory Business Verification

To collect payments within WhatsApp, your business must be verified. Ensure that you proceed with the steps below **only after your business has been verified by Meta**.

You can refer to the guide on how to verify your business with Meta.

{% hint style="warning" %}

#### Important Note : Neither Picky Assist nor WhatsApp settles or holds your payments. All payments collected are settled **directly into your bank account** by the respective payment gateway.

{% endhint %}


---

# 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://help.pickyassist.com/whatsapp-commerce/getting-started/connecting-payment-gateway.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.