> 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/using-limio-for-salesforce/payment-method-options.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.

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](/integrations/setting-up-limio-for-salesforce/detailed-salesforce-setup/zuora-hosted-payment-method.md). For Stripe setup, see [Set Up Stripe Payments for Salesforce](/integrations/setting-up-limio-for-salesforce/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 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/using-limio-for-salesforce/payment-method-options.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.