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

# Set Up Stripe Payments for Salesforce

## Overview

Limio for Salesforce supports Stripe as a payment method. Stripe payments are configured entirely within Limio — no separate payment gateway metadata setup is required in Salesforce.

When a Salesforce Flow collects a payment via Stripe, Limio renders the Stripe Payment Element iFrame directly within the Flow screen. The payment is processed through the [Stripe Connect](/integrations/stripe-billing-integration/getting-started/stripe-connect-integration.md) integration.

## Prerequisites

Before using Stripe payments in Limio for Salesforce:

1. **Stripe Connect** must be configured in Limio — see [Stripe Connect Integration](/integrations/stripe-billing-integration/getting-started/stripe-connect-integration.md)
2. **Stripe Payment Settings** must be configured — see [Configure Stripe Payment Settings](/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings.md)
3. **Named Credentials** must be set up in Salesforce — see [Set Up Limio for Salesforce](/integrations/setting-up-limio-for-salesforce/install-and-setup.md)

## How It Works

1. The Salesforce Flow displays the payment selection screen
2. The agent selects Stripe as the payment method
3. Limio calls the Stripe Payment Intent API to create a PaymentIntent and return the client secret
4. The Stripe Payment Element iFrame renders in the Flow screen, allowing the customer's card details to be securely captured
5. The payment token is passed back to the Flow and included in the order payload

## Configuration in Salesforce

### Adding Stripe to the Payment Picklist

In your Limio for Salesforce Flow:

1. Open the **Payment Selection** screen step
2. Add a new picklist choice for **Stripe** (e.g., "Credit Card (Stripe)")
3. Configure the subsequent screen to load the Stripe Payment Element

No additional Custom Metadata Types configuration is required for Stripe payments.

### 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).

### 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": {
    "paymentIntentId": "pi_xxxxxxxxxxxxx",
    "paymentMethodId": "pm_xxxxxxxxxxxxx"
  }
}
```

## Related Resources

* [Stripe Connect Integration](/integrations/stripe-billing-integration/getting-started/stripe-connect-integration.md)
* [Configure Stripe Payment Settings](/integrations/stripe-billing-integration/getting-started/configure-stripe-payment-settings.md)
* [Capture an Additional Payment](/integrations/using-limio-for-salesforce/payment-method-options/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 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/setting-up-limio-for-salesforce/detailed-salesforce-setup/stripe-payments-for-salesforce.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.