> 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/servicing-subscriptions/manage-subscriptions-flow/subflow-change-payment.md).

# Subflow: Change Payment

#### **LFS version:** Stripe support requires Limio for Salesforce v14.00 or later. Saved Stripe payment methods require v14.20 or later.

Change Payment updates the payment method on an existing subscription. The screens that the agent sees depend on the **Payment Provider** setting. See [Payment Providers](/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md).

## Which screens the agent sees

| Payment Provider | Screens                                                                         |
| ---------------- | ------------------------------------------------------------------------------- |
| `zuora`          | Payment Selection Screen, then direct debit, credit card or the customer wallet |
| `stripe`         | Stripe Payment Selection Screen, then a new payment method or an existing one   |

## The Stripe path

On the Stripe Payment Selection Screen the agent chooses one of two options.

* **Add new payment method** — Stripe collects the new payment details.
* **Use existing payment method** — the agent picks a saved payment method for the subscription.

For the Stripe setup itself, see [Stripe Payments](/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.md).

## The Zuora path

The Payment Selection Screen offers direct debit, credit card and the customer wallet. A credit card or direct debit payment uses the Zuora hosted payment page. See [Zuora HPM](/salesforce/setting-up/detailed-salesforce-setup/zuora-hosted-payment-method.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/servicing-subscriptions/manage-subscriptions-flow/subflow-change-payment.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.