Skip to main content

Overview of Payment Gateway Routing

Zuora

Overview of Payment Gateway Routing

  1. Last updated
  2. Save as PDF

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. 

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. 

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

  • Payment Run
  • Zuora UI
  • Payments API
  • Subscriptions API 
  • Hosted Form
  • Payment Method API
  • Update Payment Method API
  • Authorization API
  • Verify Payment Method API

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

GR_1.jpeg

 


Important 

  • To ensure gateway failovers work accurately, all configured gateways must support the same payment methods.
  • When you create a rule from the Authorization API, ensure that all gateways included support Delayed Capture.

Use cases of how merchants utilize Gateway Routing

  • Use rules to route based on the Payment Method type and avoid complex workflows or manual account updates. For example, automatically route PayPal Wallets to the PayPal gateway, regardless of the configuration on the customer account.
  • Introduce a new provider gradually by using the split traffic rules. For example, send 10% of traffic to a new gateway, while 90% remains on the existing provider.
  • Use split traffic to compare authorization rates, latency, or performance between providers. For example, route 50% of the USA traffic to Gateway A and 50% to Gateway B.
  • Protect revenue by automatically rerouting failed transactions to a backup provider by navigating to Assign Gateway > Response Condition > Assign Gateway. For example, during a network timeout or soft decline, retry with a second gateway. 
  • Prioritize your new gateway but route to a trusted fallback if needed. 
  • Use Gateway Routing to shift volume temporarily, without any code changes. For example, route 20% of volume to an alternative provider during contract negotiations.

Limitations

  • If a rule execution assigns a gateway that does not support an operation, the system will not generate a payment transaction log row or a payment method transaction log row for the applicable execution, depending on the situation.
  • Gateway failovers in 3DS2 applicable scenarios are not supported.
  • Hosted Payment Methods 2.0, DirectPOST, POST_Account, POST_PaymentMethodsDecryption, and POST_Order are not supported.
  • Zuora does not support Gateway Routing for the Apple Pay payment method in the Payment Form.

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.