Reading Lists
Curated reading trails
Operator-focused reading lists that turn PaymentBrief's article library into guided journeys — each one sequenced from foundational concepts through practical decision-making.
Chargeback Operator Reading List
Chargebacks are the P&L leak most operators manage by instinct rather than system. This reading list covers the scheme rules you're being held to, the unit economics most teams underestimate, the dominant fraud pattern driving the majority of dispute volume, and the representment process that recovers revenue most merchants walk away from.
Risk and operations teams managing dispute volume, payments engineers configuring dispute rules or 3DS, and any operator who has received a chargeback threshold warning from Visa or Mastercard.
Cross-Border Payments Reading List
Cross-border B2B payments are structurally expensive and operationally fragile — SWIFT correspondent chains, FX markups, and regulatory fragmentation add cost at every stage. This reading list traces the problems from first principles, maps the incumbent rail against emerging alternatives, and follows the real cost in stablecoin corridors that promise to replace it.
CFOs and treasury teams moving money across borders, payment operators expanding internationally, and fintech product teams building or evaluating cross-border payment infrastructure.
Fraud Operator Reading List
Fraud operations have shifted faster than most teams' tooling — foundation models score in milliseconds, attack patterns drift in weeks, and the cost of false positives now rivals fraud losses in many CNP channels. This reading list builds the operator picture in order: a KPI scorecard that defines what you are measuring, the detection architecture that delivers those metrics, the attack categories that drive most volume, the model and rule governance that keeps controls calibrated, and finally the platform selection decision — guarantee/liability-shift, managed decisioning, or risk scoring — that operationalises those controls.
Fraud teams, payments engineers building fraud decisioning into the authorisation path, risk leaders setting tooling and team strategy, and any operator who needs to distinguish scheme-enforced compliance thresholds from internal operating targets.
Payment Operations Decision Guides
Payment operations decisions don't arrive in isolation. They follow a sequence: before you can choose a rail or a reconciliation approach, you need to know who holds your merchant account and what liability that creates. This guide is organized as a six-stage operator decision path. Stage 1 — operating model — answers who holds the account: direct PSP, PayFac, MoR, or marketplace structure. Stage 2 — rail and lifecycle — covers which rails, which auth flow, and which capture-settlement mechanics apply to your model. Stage 3 — reconciliation and failure — addresses three-way match, break taxonomy, and recovery runbooks for when settlement doesn't close. Stage 4 — refund, chargeback, and fraud controls — is the post-payment exception stack: the refund-vs-void decision, representment controls, and the operator evidence layer for disputes. Stage 5 — marketplace and payout — covers platform-specific split-payment mechanics, seller KYB gating, payout holds, and negative-balance recovery. Stage 6 — incident and governance — is the final layer: what to do when prevention fails, including fraud incident command, severity tiers, and the post-mortem loop. Use this sequence end-to-end for a greenfield build, or jump directly to the stage that matches your current decision.
Payment operations leads, PSP product teams, and merchant payments engineers making architecture, vendor, or operational decisions across the payment lifecycle.
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.
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.
PSP Switching Reading List
Switching your PSP — or evaluating whether to — is one of the highest-stakes commercial decisions a payment operator makes. The contracts are complex, the exit costs are hidden, and the negotiating window closes the moment you sign. This reading list builds the complete picture: from operating model choice through pricing mechanics, contractual traps, and how to negotiate when you're already locked in.
Payment operators evaluating a PSP migration or benchmarking their current stack, product or engineering leads planning a switch, and CFOs reviewing PSP contracts for the first time.
Recurring Payments Reading List
Recurring payments sit at the intersection of rail mechanics, mandate compliance, and revenue retention — and the choices operators make here (which rail, which mandate type, how to handle failures) directly determine subscription churn, cost, and dispute exposure. This reading list builds the operator picture in sequence: a cross-rail taxonomy that maps the full decision space, direct debit mechanics across ACH/SEPA/Bacs/eGIRO, card recurring and MIT-CIT credential management, network token coverage and its impact on expiry churn, SEPA SDD implementation detail, regional recurring rails across Asia-Pacific, the VRP and open banking alternative, and finally the retry and authorization optimization layer that recovers revenue after failures. Read in order for the complete picture, or jump directly to the rail your stack relies on.
Payments engineers and product managers building or operating subscription billing, SaaS, insurance, or any recurring-revenue product.
Stablecoin Treasury Reading List
Stablecoin settlement has crossed from crypto-native curiosity to real payments infrastructure for specific B2B corridors. This reading list builds the complete operator picture: from the settlement loop mechanics and corridor economics, through on/off-ramp costs and issuer selection, to the regulatory frameworks now governing compliant stablecoin payment operations.
Treasury and finance operators evaluating stablecoin rails for B2B cross-border payments, payment engineers integrating on/off-ramp infrastructure, and compliance leads navigating GENIUS Act, MiCA, and MAS obligations.