Reading List
Payment Routing Reading List
Routing decisions — which acquirer, which rail, which token type, in what order — sit directly in the authorisation path and determine a measurable share of net revenue. This reading list builds the operator picture in sequence: a KPI scorecard that defines what good routing performance looks like, the economics of a single auth rate point, the optimisation levers available across your stack, multi-acquirer and least-cost routing architecture, network token coverage and its auth rate uplift, AI and ML-based orchestration, and a tooling evaluation for operators deciding whether to buy a dedicated orchestration layer.
Who this is for
Payments engineers designing or rebuilding routing logic, PSP product teams evaluating orchestration tooling, and merchant payments leaders managing auth rate, cost, and failover across multiple acquiring relationships.
Reading order
The full reading list
-
Payment Routing KPIs: Auth Rate, Failover, Cost, and Recovery
The operator scorecard: 15 KPIs across approval performance, routing reliability, cost efficiency, latency, and recovery. Start here to understand what you are measuring before reading the architecture and tooling chapters — every downstream piece is a control on one or more of these metrics.
15 min read
-
What an Auth Rate Point Is Worth: Authorisation Optimisation Economics
What a one-basis-point improvement in auth rate is worth — at different GMV levels and margin profiles. The economic model that makes routing investment decisions quantifiable and buildable, not just intuitive.
10 min read
-
Authorization Optimization: The Hidden Margin in Card Acceptance
The full set of optimisation levers: retry logic, soft decline handling, 3DS exemption selection, BIN-level routing rules, and acquirer-level performance monitoring. The practical playbook for operators who want to move the auth rate number without a second acquirer.
7 min read
-
Multi-Acquirer Routing: When and How to Add a Second PSP
When a second acquirer creates value — and when it creates operational complexity without measurable benefit. Selection criteria, BIN routing logic, failover architecture, and the overhead most operators underestimate before adding a second acquiring relationship.
11 min read
-
Least-Cost Routing: Sending Payments to the Cheapest Eligible Rail
How to identify and route to the lowest-cost eligible rail without sacrificing auth rate or settlement certainty. MDR stack analysis, rail eligibility logic, and the cost-quality trade-off matrix operators use to set routing priority.
11 min read
-
Network Tokens vs PSP Tokens: When Each Wins
Network tokens improve auth rates and reduce chargeback exposure by keeping card credentials current across lifecycle events. This article maps when network tokens win over PSP vault tokens — and the acquiring integration work required to capture the uplift.
10 min read
-
AI-Powered Payment Routing: How ML Replaced the Static Routing Table
How ML replaced static routing tables for operators at scale — feature engineering on transaction signals, model architectures that run inline in the authorisation path, and the latency and accuracy trade-offs that determine whether ML belongs in your routing layer.
11 min read
-
Spreedly vs Primer vs Gr4vy: Payment Orchestration Layer Compared
When a dedicated orchestration layer makes sense versus building routing logic in-house. Spreedly, Primer, and Gr4vy compared on architecture, connection breadth, routing logic flexibility, and total cost — with a framework for deciding what to build versus buy.
10 min read