Use case for Payment Gateway Routing
Learn how merchants use Gateway Routing rules to control payment provider selection, compare gateway performance, and protect revenue by dynamically routing transactions.
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 . 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.