Reading List
Payment Architecture Reference Reading List
Payment architecture decisions are unusually unforgiving: they are made early, they are expensive to reverse, and the cost of getting them wrong shows up years later as a migration nobody budgeted. This list is the structural layer — who the parties are and what each one owns, whether to build or buy orchestration, how entities and MIDs should map to legal and commercial reality, where credentials live and who can reach them, how card-present fits alongside online, and what happens when a provider goes down. Read it before designing, not while debugging.
Who this is for
Payments engineers and architects designing or re-platforming a payment stack, and technical leads evaluating orchestration, vaulting and multi-acquirer strategies.
Reading order
The full reading list
-
Issuer, Acquirer, Gateway, PSP: The Payment Stack Operators Actually Contract With
The foundation everything else assumes. Who the issuer, acquirer, gateway and PSP actually are, what each one owns, and where the boundaries sit — including the cases where one company occupies several roles at once and the boundary stops being visible.
11 min read
-
Payment Orchestration Architecture: Build vs Buy vs PSP-Native
The first structural fork. What an orchestration layer genuinely provides, what it costs in control and lock-in, and the conditions under which building it yourself is the cheaper mistake.
22 min read
-
Multi-Entity, Multi-MID Payment Architecture: Designing Merchant ID Structure
How legal entities, MIDs and descriptors should map to each other — and the failure mode where a structure designed for one market quietly breaks settlement, reporting or scheme compliance in the next one.
16 min read
-
Payment Credential Vault Architecture: Topology, Control, and Migration
Where card credentials live, who can reach them, and how vault topology determines both PCI scope and how hard your next provider migration will be. The single decision most likely to trap you with a provider.
17 min read
-
Card Credential Lifecycle: What Actually Keeps a Stored Card Working
Stored credentials decay. Account updater services, network-token lifecycle, and the operational work that keeps a card-on-file portfolio chargeable rather than slowly rotting into involuntary churn.
13 min read
-
Card-Present Payment Architecture: The Omnichannel Reconciliation Problem
The physical side, and how it joins the online one. Terminal topology, semi-integrated versus fully integrated designs, and what genuine omnichannel requires beyond sharing a customer record.
14 min read
-
PSP and Acquirer Outage Failover Runbook: Detecting Degradation, Failing Over Cleanly, and Recovering Without Double Charges
What the architecture is for. Detecting a provider outage, deciding whether to fail over, and the pre-work — routing, credentials, reconciliation — that has to already exist for failover to be a decision rather than a project.
10 min read