Why Static Processor Setups Fail
Merchants operating multiple acquirers often run into structural inefficiencies:
- Approval rates fluctuate across BINs and regions
- Single-processor setups increase operational risk
- Processor performance varies by country and card scheme
- Fixed cascading order ignores real approval probability
- Brand-level routing (e.g. "all Visa to processor X") becomes too coarse
Modern payment performance requires granular control — not simple failover.
Rule-Based Routing with Full Control
UpGate routing is priority-driven and fully configurable. Rules can factor in card data, customer location, payment attributes, and purchase history — so traffic is distributed intentionally, not randomly.
- Segment CIT/MIT and first-time payments
- Filter by BIN, country, scheme, and card type
- Route high-ticket transactions to dedicated MIDs
- Define custom parameters and merchant logic
Rules are evaluated in strict priority order, ensuring predictable execution.
Traffic Distribution Across Multiple Processors
Within each routing rule, traffic can be distributed across multiple processors using percentage allocation.
- Define precise traffic splits (e.g. 70% / 30%)
- Gradually scale traffic to new processors
- Balance load across acquirers
- Run controlled A/B performance testing
Total allocation is always governed and transparent — routing stays flexible and operationally controlled.
Decline-Aware Cascading
Routing determines the first attempt. Cascading determines what happens if that attempt fails — avoiding unnecessary retries while maximising recovery. All cross-acquirer fallback attempts happen seamlessly in the background, requiring no further user interaction.
- 1
First processor in the sequence
- 2
Second processor in the sequence
- 3
Additional processors, as configured
Retries only trigger for recoverable declines — soft decline codes, authentication failures (CVV/3DS), or custom codes you define — and stop once the transaction is approved or the maximum configured attempts is reached.
Built for Multi-Acquirer Environments
UpGate routing and cascading are designed for merchants who:
End-to-End Merchant Benefits
Higher Approval Rates
Granular routing combined with intelligent cascading increases successful authorisations.
Improved Infrastructure Stability
Automatic fallback protects against processor downtime and instability.
Controlled Cost Optimisation
Direct traffic toward lower-cost acquirers without sacrificing performance.
Reduced Dependency Risk
Multi-processor orchestration reduces reliance on any single provider.
Transparent Governance
Priority-based rules and percentage allocation keep behaviour predictable.
Latency & Fallback Speed
Routing decisions execute in real time within the orchestration layer, minimising latency.
UpGate vs. Basic Failover Setups
| Capability | UpGate | Basic Processor Setup |
|---|---|---|
| Deterministic rule priority | Yes | Limited |
| Granular condition engine | Yes | Typically country-based only |
| Percentage traffic split | Yes | Rare |
| Decline-code-level cascading | Yes | Limited |
| Multi-flow segmentation (CIT / MIT / Recurring) | Yes | Often restricted |
How to Enable Routing & Cascading
Merchants configure routing rules and cascading logic directly within UpGate.
- 1
Define routing conditions
- 2
Assign processor allocation
- 3
Configure cascading order and decline triggers
- 4
Set rule priority
Mass Routing Configuration
UpGate supports bulk routing management through Mass Upload Routing Rules in Advanced Settings — upload configurations in JSON to manage rules at scale.
Tell us about your company
Get a custom setup designed for your business model and scale.