Skip to main content

Overview of Payment Gateway Routing

Zuora

Overview of Payment Gateway Routing

Payment Gateway Routing is a feature powered by Zuora, which allows you to route transactions to preferred payment gateways and to handle fallback scenarios in case those transactions fail. It is helpful to lower costs and increase the success rate of transactions. 

This feature is in the Early Adopter phase. We are actively soliciting feedback from a small set of early adopters.

You are able to define your own custom rules for processing payments through the specified payment gateway. The rules determine when a gateway should be changed from the default, how to categorize transactions and route to specified gateways, and whether to immediately retry those transactions on subsequent failover gateways. You can specify conditions based on attributes of payments, payment methods, and gateway response.

When the Payment Gateway Routing feature is enabled, the payment transaction will follow the routing rule to determine the payment gateway to use. However, if a gateway is specified in your payment API request, the routing rule will not be triggered, and the specified gateway will be used. 

If the execution of the routing rule is not successful because no routing rule matches or the Payment Gateway Routing service is unavailable, the default gateway will be used. The default gateway of the customer account takes precedence over the default gateway of the tenant. 

For now, the trigger of the routing rule execution can be payment processing from the following sources:

  • API operations 
  • Payment runs
  • Manual operations through the UI

The following diagram illustrates the logic of using which payment gateway in payment processing.

gateway-routing-flow.png

To use Payment Gateway Routing, complete the following tasks. Click each task for details.

  1. Ensure that you have been granted the Edit Payment Gateway Routing permission. For more information, see Payments roles.
  2. Enable the Payment Gateway Routing feature.
  3. Create and manage rules.
  4. Review the rules used for payment processing.