> 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/additional-config/payment-methods.md).

# Payment Methods

In both acquisition and management flows, is it possible to customise the payment methods, passing other values to the picklist.

Because the payment selector uses the ootb picklist component, choices can be specified directly within the component itself, to accommodate it to payment methods that are the most relevant.

{% hint style="info" %}
From v14.41, the packaged Acquisition Journey takes the payment in the **Limio Order Payment Subflow**. This subflow is part of the managed package, so you cannot change its choices in Flow Builder. It shows the payment methods that your [payment provider](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md) supports. A copy of the Acquisition Journey that you made before v14.41 keeps its own payment screens, and the text above applies to that copy.
{% endhint %}

Limio for Salesforce supports both Zuora HPM and Stripe Payment Element for secure payment capture. For Zuora setup, see [How to create a new Zuora Hosted Payment Method](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/zuora-hosted-payment-method.md). For Stripe setup, see [Set Up Stripe Payments for Salesforce](https://docs.limio.com/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.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/additional-config/payment-methods.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.
