> 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/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.md).

# Stripe Payments

## Overview

Limio for Salesforce supports Stripe as a payment method. You configure Stripe in Limio. In Salesforce, you only set the **Payment Provider** value.

When a Salesforce Flow collects a payment via Stripe, the Stripe Payment Element shows on the Flow screen, and Stripe collects the card details. The payment goes through the [Stripe Connect](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/stripe-connect-integration) integration.

## Prerequisites

Before using Stripe payments in Limio for Salesforce:

1. Configure **Stripe Connect** in Limio. See [Stripe Connect Integration](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/stripe-connect-integration).
2. Configure **Stripe Payment Settings** in Limio. See [Configure Stripe Payment Settings](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings).
3. Set up **Named Credentials** in Salesforce. See [Set Up Limio for Salesforce](https://docs.limio.com/salesforce/setting-up/install-and-setup.md).
4. Set **Payment Provider** to `stripe` on the icConfig custom setting. See [Payment Providers](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md).

{% hint style="warning" %}
Do step 4 last. The value changes the set of actions that agents see as soon as you save it. See [Payment Providers](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md) for the actions that Stripe supports.
{% endhint %}

## How It Works

1. The Salesforce Flow displays the payment selection screen
2. The agent selects Stripe as the payment method
3. Limio prepares the payment with Stripe
4. The Stripe Payment Element shows on the Flow screen, and Stripe collects the card details
5. The payment token is passed back to the Flow and included in the order payload

## Configuration in Salesforce

### Choosing Stripe

The **Payment Provider** setting chooses the provider, not the agent. With `stripe`, the packaged flows open the Stripe payment screens.

Do not add a Stripe choice to the Payment Selection screen. That screen is for Zuora only.

Stripe payments need no Custom Metadata Types configuration.

### Supported Payment Methods

The Stripe Payment Element in LFS supports:

* **Credit / Debit Card** — Immediate payment collection via PaymentIntent
* **BACS Direct Debit** — UK bank debit via mandate creation

The available methods depend on your Stripe account's enabled payment methods. Configure these in the [Stripe Dashboard](https://dashboard.stripe.com/settings/payment_methods).

{% hint style="info" %}
From v14.14, the Payment Element does not show Apple Pay or Google Pay. Agents take payment details over the phone, so device wallets do not apply.
{% endhint %}

### Saved Payment Methods

From v14.21, the Change Payment flow lists the Stripe payment methods that Limio holds for the subscription. An agent can use one of them again, and does not have to collect new details. See [Subflow: Change Payment](https://docs.limio.com/salesforce/servicing-subscriptions/manage-subscriptions-flow/subflow-change-payment.md).

### Existing Customer Matching

When processing an order, Limio checks for an existing Stripe Customer by email. If a match is found, the existing customer record is reused rather than creating a duplicate. This preserves subscription history and payment methods.

### Payment Body Format

When Stripe is used, the payment variable contains a JSON body in the following format:

```json
{
  "type": "stripe",
  "stripe": {
    "intentType": "setup_intent",
    "intentId": "seti_xxxxxxxxxxxxx",
    "paymentMethodId": "pm_xxxxxxxxxxxxx",
    "customerId": "cus_xxxxxxxxxxxxx",
    "connectedAccountId": "acct_xxxxxxxxxxxxx"
  }
}
```

`connectedAccountId` is present only when the payment uses a Stripe connected account.

## Related Resources

* [Stripe Connect Integration](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/stripe-connect-integration)
* [Configure Stripe Payment Settings](https://docs.limio.com/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings)
* [Capture an Additional Payment](https://docs.limio.com/salesforce/setting-up/additional-config/payment-methods/capture-additional-payment.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.limio.com/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.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.
