> 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/manage-payments/configure-payment-methods.md).

# Configure Payment Methods

Payment methods for Stripe Billing are configured per Offer. Each Offer defines which Stripe payment methods are available at checkout, allowing you to tailor the payment experience to the product.

## Supported Payment Methods

| Payment Method               | Type                                       | Availability |
| ---------------------------- | ------------------------------------------ | ------------ |
| **Stripe Card**              | Credit / debit card, Apple Pay, Google Pay | All regions  |
| **Stripe BACS Direct Debit** | UK bank debit                              | UK only      |

Apple Pay and Google Pay are automatically available when **Stripe Card** is selected, provided they are enabled in your Stripe account and the customer's device supports them. They do not need to be configured separately.

{% hint style="info" %}
Additional payment method support (SEPA Direct Debit, ACH, PayPal) is planned. Contact <support@limio.com> for the latest availability.
{% endhint %}

## Enabling Payment Methods on an Offer

On the Limio Offer, use the **Payment Types** dropdown to select the Stripe payment methods you want to allow. You can select one or multiple:

* **Stripe Card** — displays Card, Apple Pay, and Google Pay options in the Payment Element
* **Stripe BACS Direct Debit** — displays only BACS Direct Debit

The Stripe Payment Element at checkout will render only the options configured on the Offer.

### When both are configured

If an Offer has both **Stripe Card** and **Stripe BACS Direct Debit** selected, the customer uses the Payment Method Selector subcomponent to choose between Card or Direct Debit before the Stripe Payment Element loads.

### Example: different prices per payment method

A common use case is offering a discount for Direct Debit to encourage customers to pay by DD (which typically has higher retention than card).

**Setup:** one Stripe Product, two Limio Offers:

| Offer                           | Price      | Payment Type             |
| ------------------------------- | ---------- | ------------------------ |
| Adult Membership — Card         | £60 / year | Stripe Card              |
| Adult Membership — Direct Debit | £55 / year | Stripe BACS Direct Debit |

Each Offer is displayed separately on the pricing page. The customer chooses the Offer that matches their preferred payment method, and the checkout only shows the matching Payment Element.

## How Payment Methods Work

### Card, Apple Pay, Google Pay

These all run through Stripe's card rails. Payment is collected immediately via a PaymentIntent, and the payment method is saved to the Stripe Customer for future recurring charges.

Apple Pay and Google Pay only appear in the Payment Element if:

* They are enabled in your Stripe account
* The customer's device and browser support them
* The site is served over HTTPS

### BACS Direct Debit

BACS Direct Debit uses a mandate-based flow:

1. The customer enters their bank account details in the Stripe Payment Element
2. A BACS mandate is created
3. The first payment is collected — settlement is typically 3-5 business days
4. Future recurring charges are collected automatically against the mandate

{% hint style="warning" %}
BACS settlement is not instant. Depending on your business requirements, you may activate the subscription immediately on mandate creation or wait for payment confirmation.
{% endhint %}

### What customers see in self-service

From Release 116, all of these payment methods display correctly in the saved payment methods component and on the order complete page:

* **Cards** show the brand, last 4 digits and expiry date
* **Apple Pay and Google Pay** payments are identified distinctly, with the wallet icon alongside the underlying card's brand, last 4 digits and expiry date
* **BACS Direct Debit** shows the last 4 digits of the account with a bank icon

Any of these payment methods can be set as the default, and the default stays consistent between Limio and Stripe.

## Customising the Payment Element Appearance

For Payment Element appearance, layout, and theme options, see [Configure Stripe Payment Settings](/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings.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 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/manage-payments/configure-payment-methods.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.