Welcome to Zuora Product Documentation

Explore our rich library of product information

Use multiple payment gateways

You can configure multiple payment gateways in Zuora so that different groups of customers use different gateways based on your business needs.

You can set up multiple payment gateways by using the same gateway type or different gateway types. This approach is useful when you want to route transactions for different customer segments through different gateways.

Common reasons to use multiple payment gateways include the following:

  • By country: You might use different gateways for customers in different regions. For example, you can process US transactions through one gateway, UK transactions through another gateway, and Canadian transactions through a third gateway.
  • By payment method: You might use one gateway for ACH payments and another gateway for card payments.
  • By fraud risk: You might send transactions for higher-risk customers through a gateway or service that provides stronger fraud detection, while sending lower-risk transactions through a lower-cost gateway.
  • By currency: Some gateways require or recommend different merchant IDs for different settlement currencies, such as one merchant ID for USD and another for EUR.

After you configure multiple gateways, you can assign a specific gateway to each customer account. The default payment gateway is used when you create a customer account, but you can change the gateway later in the customer account settings under Billing and Payment Term.

To add more payment gateways, repeat the gateway configuration process for each additional gateway instance.

Important:

If you use Payment Pages 2.0 to host payment method pages and you switch a payment method to another payment gateway after the stored credential profile has already been created, the customer must re-authenticate that payment method on the hosted payment page. Payment Pages 2.0 is Zuora's hosted payment method solution and supports secure, PCI-compliant payment method collection through embedded pages or related integration options.

For more information about Payment Pages 2.0 implementation and client parameters, see the following articles: