> For the complete documentation index, see [llms.txt](https://docs.feathery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.feathery.io/guides/payment-flow.md).

# Build a Payment Flow

Stripe is a leading payments provider. Use Feathery’s Stripe integration for any or all of the following:

* Collect payment methods from users (e.g. a credit card)
* Allow users to choose products to purchase
* Accept online payments for selected products

### What you need

* An active [Feathery](https://feathery.io/) account and form
* An active [Stripe](https://stripe.com/) account

### Implementing Payments

Determine how you plan to integrate Stripe with Feathery. You can choose to only collect payment info (credit cards) for future charges or you can collect an actual payment as well.

Your implementation will have up to 4 steps:

1. [Turn on your Stripe integration](/guides/payment-flow/connect-to-stripe.md)
2. [Add your payment collection method](/guides/payment-flow/collect-payment-method.md)
3. [Build your product selector and selections confirmation or cart (optional](/guides/payment-flow/select-products-or-plans.md))
4. [Charge the user's payment method (optional)](/guides/payment-flow/purchase-products.md)


---

# 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://docs.feathery.io/guides/payment-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.