> 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/automations-builder/how-to-take-payment-via-stripe-in-automation-flow.md).

# How to take payment via Stripe in Automation flow ?

To integrate Stripe payment in WhatsApp automations, start by creating a flow with a trigger for when a new order is received, and the user selects online payment.

The first step is to add a new block to multiply the total amount by 100, as payment apps automatically take the lowest unit of money.

To do this, add a new automation app, search for "calculator", and select the "multiply" block, then enter the values manually and save the result.

Map the order total to the first number and 100 to the second number, and then click on save.

Next, add a new automation app, search for "Stripe", and select "create checkout".

Create a new authentication by clicking on "create new authentication" and entering a label, then in stripe click on "developers" and "API keys" to create a restricted key.

Select "building your own integration" and continue, then enter a name and select the permissions you want to give, including read permissions for charges, write permission for payment links, payment intents, and checkout sessions.

Create the key and enter the OTP for verification, then copy the API key and paste it into the authentication.

After selecting authentication, add a product name and map the charge amount to the result from the multiplication, then map the currency and quantity.

Add a success URL and cancel URL, which will redirect the user when the payment is successful or cancelled.

Add data manually to "run and save" and  then map properly and save.

In the next block, select the "question block" and add a CTA URL button message, then map the URL and click on save.

This will allow you to share the checkout URL with your users.

{% embed url="<https://youtu.be/8cXwdU9Abnc?si=zgVgWb8IOI_sktgZ>" %}


---

# 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/automations-builder/how-to-take-payment-via-stripe-in-automation-flow.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.
