Routing Matrix

Routing Matrix allows you to build and manage rules for how transactions are processed across different payment providers, payment methods, geographies and other dependencies. By defining routing logic, you gain full control over how payments are directed, blocked, or prioritized — ensuring optimal performance, compliance, and cost-efficiency.

With the Routing Matrix, you can:

• Create routing rules – define when transactions should be sent to a specific PSP.
• Block transactions – prevent payments based on defined criteria such as country, BIN, or amount thresholds.
• Optimize performance – route payments based on success rates, authorization speed, or other KPIs.
• Support compliance requirements – enforce country-specific rules or block restricted payment types.

Key Features

• Rule-based configuration – build conditions using parameters such as country, card brand, transaction amount, currency, or customer details.
• PSP traffic – distribute traffic dynamically across multiple PSPs.
• Flexible control – apply the same rules globally or per merchant account.
• Real-time updates – rules take effect immediately, ensuring your routing strategy adapts as needed.
• Monitoring & reporting – track the impact of routing changes on performance, costs, and approval rates.

ℹ️

Please note that Routing Rules refer to the initial transaction only. If the fallback applies, the Routing Rules are not taken into account in the fallback cycle.

Getting Started

1. Access the Routing Matrix Tool

• Log in to your merchant account.
• Navigate to Integration → Payment Network → Routing Matrix If you have more than one Merchant Account, you need to select it in the Payment Network first.

2. Create a Rule

   • Click Add a new rule and define conditions such as:

     • Amount
     • Authorization currency
     • Country (IP)
     • Issuer country
     • Issuer
     • Merchant store ID
     • Merchant data
     • List
     • Payment channel Payment method
     • Payment method type
     • A/B testing_

   • Assign the desired action: Route to a desired PSP or Block. If your defined condition is A/B testing, specify the division (%) across the PSPs you want.

3. Order & Prioritize Rules
   • Rules are executed in sequence.
   • Use drag-and-drop to define evaluation order.
4. Test
   • Use test transactions or Rule Testing Engine to verify expected behavior.
   • Make adjustments in the rules or their order if needed
     

Routing rule examples

1. Spread traffic across selected PSPs for a specific payment method.

flowchart LR 
A[Payment method: Visa] --> B[70%] 
A --> C[30%] 
B --> D[PSP A]
C --> E[PSP B]

2. Route certain types of payment methods (card, e-wallet, etc.) to different PSPs.

flowchart LR 
A[Payment method type] --> B[Card] 
A --> C[E-wallet] 
B --> D[PSP A]
C --> E[PSP B]

3. Block transaction for a specific country IPs.

flowchart LR 
A[Country IP] --> B[United States, Cuba] 
A --> C[Other]
B --> D[Block transaction] 
C --> E[Allow transaction] 

Test your routing rules

Once you have created the routing rule(s), you can make a simulation from the UI, using our Rule Testing Engine to see whether the specific transaction falls correctly under the rule you have created.

In the engine, you can fill in some basic payment details and add more filters for additional ones. Once you click on submit, you will see the Merchant Contract (PSP) that the transaction was routed to and the rule it fell under. If it did not fall under any rule, you will still see the Merchant Contract and the Smart Routing being applied.

Best Practices

• Start simple – begin with high-level routing rules (e.g., by region or card brand) before adding granular conditions unless it is not possible in you use case.
• Monitor performance – regularly check dashboards and reports to refine your routing strategy.

The Routing Matrix gives you the flexibility to adapt your payment flow in real time, balancing performance, reliability, and compliance while keeping full control of transaction routing.