> 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/zuora-integration/configuring-payment-gateways.md).

# Manage Payments

Learn how to configure payment gateways in Zuora for use with Limio Commerce.

## Overview

Payment gateways process credit card and other payment transactions. Zuora supports multiple payment gateway providers that can be configured for use with Limio Commerce.

This section covers how to set up and configure payment gateways to work seamlessly between Limio and Zuora.

## Related Topics

For specific payment types configuration, see:

* [Configuring Payment Types](https://docs.limio.com/integrations/zuora-integration/configuring-payment-gateways/configuring-payment-type.md) - Apple Pay, Google Pay, PayPal setup
* [Payment Gateway & Method Flexibility](https://docs.limio.com/product/checkout/overview-how-to-customise-the-limio-modular-checkout#payment-gateway-and-payment-method-flexibility) - Overview of how Limio integrates with billing-native and third-party payment providers


---

# 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/integrations/zuora-integration/configuring-payment-gateways.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.
