> 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/capture-additional-payment.md).
# Additional Payment
The Limio for Salesforce flows supports the following payment methods out-of-the-box:
* Credit card via embedded Zuora iframe
* Direct debit via embedded Zuora iframe
* Stripe Payment Element. See [Set Up Stripe Payments for Salesforce](/salesforce/setting-up/detailed-salesforce-setup/stripe-payments-for-salesforce.md) and [Payment Providers](/salesforce/setting-up/detailed-salesforce-setup/payment-providers.md)
* Existing payment method i.e. customer wallet
In some cases, there may be a need to setup an additional payment method. It may be specific to the Salesforce org and already implemented as part of the org. For example, you may have implemented a payment gateway that ask the customer to input their payment information using their phone’s keyboard (DTMF or IVR), without the agent ever seeing or handling the full credit card details.
Additional payments can be collected outside the Limio for Salesforce Flow and passed to Limio for Salesforce. In order to do so, a specific payment body needs to be passed to the Flow in the variable "payment". To see the variable, go to any Limio for Salesforce Flow, click on Toolbox > Manager and click payment under Variables.
The variable will be a string that represent a JSON body for the payment being collected. For example, a Zuora payment would have a variable that looks like the following JSON:
`{"type":"zuora","zuora":{"refId":"8ad08871813e5776018143730f096940","paymentGateway":"Test Gateway"}}`
For a Stripe payment, the variable would look like:
`{"type":"stripe","stripe":{"intentType":"setup_intent","intentId":"seti_xxxxxxxxxxxxx","paymentMethodId":"pm_xxxxxxxxxxxxx","customerId":"cus_xxxxxxxxxxxxx"}}`
That's it on the Limio side! Now, you can create a Subflow to invoke the additional payment method, for example a DTMF/IVR solution. Assign the output of the flow to the payment variable as below.
---
# 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/capture-additional-payment.md?ask=&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.
.png?alt=media)
.png?alt=media)
.png?alt=media)