> For the complete documentation index, see [llms.txt](https://docs.super-forms.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.super-forms.com/features/integrations/stripe-beta.md).

# Stripe (BETA)

{% hint style="danger" %}
This feature is work in progress and not yet available to the public. The documentation will be available upon release. If you have any questions regarding the Stripe integration, please [submit a ticket](/support.md).
{% endhint %}

### Quick start

Navigate to Super Forms > Settings > Stripe checkout. Configure all the Stripe API settings for both **Live** and **Sandbox** mode.

On your form you can navigate to the **\[Stripe]** TAB. Here you can configure all the required settings such as the Stripe product ID or subscription ID in order for Stripe to understand what it needs to add to the cart on the checkout page. You may also configure products on the fly


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.super-forms.com/features/integrations/stripe-beta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.