> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings.md).

# Configure Stripe Payment Settings

Limio allows you to customise the appearance and behaviour of the Stripe Payment Element that is rendered in your checkout and self-service forms.

## Accessing Stripe Settings

1. Go to `https://<tenant>.limio.com/developer/settings`
2. In the left-hand sidebar under **General Settings**, click **Stripe**

## Configuration Options

### Stripe Payment Element Configuration

| Setting                      | Description                                                              | Options                                       |
| ---------------------------- | ------------------------------------------------------------------------ | --------------------------------------------- |
| **Accepted Payment Methods** | The payment methods available to customers in the Stripe Payment Element | Card, ACH, and other Stripe-supported methods |
| **Layout Style**             | How the payment methods are displayed in the form                        | `Accordion` (default), `Tabs`                 |
| **Theme**                    | The visual theme of the Stripe Payment Element                           | `Stripe` (default), `Night`, `Flat`           |
| **Primary Color**            | The accent colour used in the Payment Element                            | Any hex colour value                          |

### Zuora Billing Configuration

If you are using the [Limio Stripe Payments Integration](/integrations/zuora-integration/configuring-payment-gateways/limio-stripe-payments-integration.md) with Zuora (Stripe tokenization with Zuora billing), you can also configure:

* **Stripe Payment Page Configuration** — Set up a Publishable Key and Zuora Payment Gateway ID for Stripe-to-Zuora token passing

{% hint style="warning" %}
The Zuora Configuration section is only relevant if you are using Stripe with Zuora. If you are using Stripe Billing (Stripe Connect), you do not need to configure anything in this section.
{% endhint %}

## Saving Changes

After making your changes, click **Save** at the top of the page. Changes to your Stripe Payment Element configuration take effect immediately on your shop and self-service pages.

## Next Steps

* [Stripe Connect Integration](https://github.com/innovate42/innovate42-service-template/blob/docs/docs/_external/spaces/integrations/stripe-billing/getting-started/stripe-connect-integration.md) — Link your Stripe account
* [How Checkout Works with Stripe](https://github.com/innovate42/innovate42-service-template/blob/docs/docs/_external/spaces/integrations/stripe-billing/manage-payments/how-checkout-works-with-stripe.md) — Understand the payment flow


---

# 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.limio.com/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings.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.