Acquiring · QRoute

Every charge takes
the smartest path.

Specificity-scored routing rules steer every charge to the best gateway by country, currency, method and amount — with automatic failover when a rail degrades. Declare your routing intent once — QRoute evaluates it on every transaction, in real time, with a full audit trail of why each decision was made.

Live routing decision

Rules that explain themselves.

Stop hard-coding gateway choices into application logic. Every routed charge records which rule won, its specificity score, and which gateways were considered — so operations and finance can always answer "why did this go there?"

  • Deterministic selectionThe narrowest matching rule always wins — no ordering tricks, no black box.
  • One clean outcomeFailover retries cascade underneath; the payer sees a single result.
  • Everything journaledCandidate rules, scores and gateway attempts, ready to export.
ChargeNGN 250,000 · card
Winning ruleNG + card + >₦100k (score 7)
Primary gatewayQPay
Failover chainPaystack → Sandbox
HealthAll probes passing
Capabilities

Orchestration built for uptime and approval rates.

Declarative routing, automatic failover and health-aware steering — everything you need to squeeze more approvals out of the processors you already have.

Specificity-scored rules

Write rules over country, currency, method and amount band. QRoute scores each match by how specific it is, so the narrowest applicable rule always wins — deterministically, with no ordering tricks.

Automatic failover

Each rule carries an ordered gateway chain. If the primary declines for a technical reason or times out, QRoute retries the next processor in milliseconds — the payer never sees the stumble.

Gateway health probes

Continuous synthetic probes and rolling error-rate windows detect a degrading rail before your customers do, automatically demoting it from routing until it recovers.

Multi-gateway portfolio

Connect any mix of processors — global acquirers, local champions, your own claimed gateways — and rebalance volume between them without a code deploy.

Cost-aware steering

Weight decisions by processing cost as well as approval likelihood. Send high-margin traffic to premium rails and commodity traffic to the cheapest healthy one.

Decision audit log

Every evaluation is journaled: candidate rules, scores, gateway attempts and outcomes. Export it for reconciliation, disputes or regulator questions.

Declarative by API

Routing intent as data, not code.

Define conditions and an ordered gateway chain once — in the dashboard or over the API. QRoute versions every rule and evaluates them the same way on every charge, so a routing change never means a redeploy.

CountryCurrency MethodAmount band Ordered chain
POST /api/v1/qroute/rules { "match": { "country": "NG", "currency": "NGN", "method": "card", "amount_min": 10000000 }, "gateways": ["qpay", "paystack", "sandbox"], "weight_by": ["approval_rate", "cost"] } → 201 rule #7 · specificity score 7 primary: qpay · failover: paystack → sandbox
How it works

Three steps from policy to routed payment.

Declare your rules

In the dashboard or via API, define conditions and an ordered gateway chain for each. Start broad, then add narrower rules as volume grows.

QRoute scores & selects

On each charge, every matching rule is scored for specificity; the winner's healthiest gateway takes the transaction.

Failover if needed

Technical declines cascade down the chain automatically. You see one clean outcome; the retries live in the audit log.

Under the hood

Deterministic by design, transparent by default.

No black-box scoring, no hidden ordering. Every routing primitive is inspectable and reversible.

Condition matchingCountry, currency, payment method and amount band, combined with AND semantics per rule.
Specificity scoringThe narrowest matching rule wins deterministically — no manual priority list to maintain.
Ordered gateway chainsPrimary plus ranked failover targets, retried on technical decline within the same request.
Rolling health windowsSynthetic probes and live error rates demote and restore rails automatically.
Cost weightingBlend processing cost with approval likelihood to steer margin-sensitive traffic.
Exportable audit trailFull decision journal for reconciliation, disputes and regulator queries.
2–5%
Declined volume recovered
<50ms
Routing decision time
99.99%
Orchestration uptime
100%
Decisions audited
Lift approvals

Turn routing into a competitive advantage.

Merchants moving to intelligent orchestration typically recover 2–5% of declined volume. Let us show you the math on yours.