> 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/payment-providers.md).

# Payment Providers

The payment provider collects the card details in its own secure form. Limio stores the token that the provider returns.

Limio for Salesforce supports two payment providers: Zuora and Stripe. You set one provider for your org. Every flow that takes or changes a payment follows it: the acquisition journey, Change Payment, and the actions that agents see on a subscription.

## What the setting controls

| Journey                 | With `zuora`              | With `stripe`                                               |
| ----------------------- | ------------------------- | ----------------------------------------------------------- |
| Acquisition             | Zuora hosted payment page | Stripe Payment Element                                      |
| Change Payment          | Payment Selection screen  | Stripe payment screens, for a new or a saved payment method |
| Cancel                  | Cancel flow               | Cancel V2 flow                                              |
| Change the subscription | Manage Add-Ons            | Update Subscription                                         |

### Actions available to agents

When no [Subscription Actions](/salesforce/setting-up/additional-config/subscription-actions-rules.md) matches a subscription, the package shows these actions by default:

| Action                                                 | With `zuora`          | With `stripe` |
| ------------------------------------------------------ | --------------------- | ------------- |
| Cancel                                                 | Yes                   | Yes           |
| Change Payment                                         | Yes                   | Yes           |
| Change Address                                         | Yes                   | Yes           |
| Manage Add-Ons (Zuora) or Update Subscription (Stripe) | Yes, when switched on | Yes           |
| Switch                                                 | Yes                   | No            |
| Renew                                                  | Yes                   | No            |
| Refund                                                 | Yes                   | No            |
| Redeem Gift                                            | Yes, when switched on | No            |
| Pause Print                                            | Yes, when set up      | No            |
| Credit Memo                                            | Yes, when switched on | No            |
| Revert Cancel                                          | Yes                   | No            |

Each action also depends on the subscription, for example on its status. Manage Add-Ons, Update Subscription, Credit Memo and Revert Cancel show in the Manage Subscriptions flow only.

To switch on Manage Add-Ons, Redeem Gift or Credit Memo, see [Custom Metadata Types](/salesforce/setting-up/detailed-salesforce-setup/custom-metadata-types.md). Pause Print needs a `pause_print` custom order type in Limio.

{% hint style="warning" %}
If you move an org from Zuora to Stripe, check that the Stripe actions cover your agents' journeys before you change the setting on production. Talk to your Limio contact to plan the move.
{% endhint %}

## Availability

| Release | Stripe support       |
| ------- | -------------------- |
| 13.91   | Acquisition journey  |
| 13.96   | Cancel V2            |
| 13.97   | Subscription actions |
| 14.00   | Change Payment       |
| 14.02   | Update Subscription  |

Earlier releases support Zuora only.

{% hint style="info" %}
After you upgrade, set the **Payment Provider** value before agents use the org. The field is empty after the upgrade, also on orgs that use Zuora. Existing Zuora customers enter `zuora`, and nothing else changes for them.

While the field is empty, agents see the error "Payment provider is not configured or not supported" when they open a subscription or start a sale.
{% endhint %}

## Set up the Payment Provider setting

1. Click the gear icon → **Setup**.
2. In the **Quick Find** box, type `Custom Settings` → click it.
3. Find **icConfig** in the list → click **Manage** (left of the name).
4. Click **New** if nothing exists yet, or **Edit** on the **Default Organization Level Value**.
5. In the field labelled **Payment Provider**, enter `stripe` or `zuora` in lower case.
6. Click **Save**.

{% hint style="warning" %}
Set the value at the organisation level only. A profile-level or user-level record overrides the organisation value for those users. If one agent sees different screens from the rest, look for a record at those levels.
{% endhint %}

<figure><img src="https://284256719-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUgE12kxtw8dDbuEZGzbI%2Fuploads%2Fgit-blob-8ca1177fd39ffbd2d055008379baa82605f352c3%2Fimage%20(404).png?alt=media" alt=""><figcaption></figcaption></figure>

## Related Resources

* [Stripe Payments](/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.md)
* [Zuora Hosted Payment Method](/salesforce/setting-up/detailed-salesforce-setup/zuora-hosted-payment-method.md)
* [Subflow: Update Subscription](/salesforce/servicing-subscriptions/manage-subscriptions-flow/subflow-update-subscription.md)
* [Subflow: Change Payment](/salesforce/servicing-subscriptions/manage-subscriptions-flow/subflow-change-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/payment-providers.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.
