Reading List
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.
Who this is for
Payment operations leads, PSP product teams, and merchant payments engineers making architecture, vendor, or operational decisions across the payment lifecycle.
Reading order
The full reading list
-
How to Choose a PSP: A Decision Matrix for Payment Operators
The pre-comparison filter: a multi-axis decision matrix mapping volume, model, and geography to a provider class before any head-to-head.
15 min read
-
PSP vs PayFac Operations: A Model Reference for Operators
Five operating models (direct PSP / PayFac / acquirer / aggregator / MoR) compared by account ownership, KYB obligation, chargeback liability, and settlement responsibility.
14 min read
-
MoR vs PSP: When the Premium Beats Doing It Yourself
The operating-model decision before the shortlist: whether to use a MoR or direct PSP changes your liability exposure, payout timing, and switching cost profile at exit.
11 min read
-
Authorization, Capture, and Settlement: Payment Lifecycle for Operators
The auth→capture→settlement lifecycle: holds, capture windows, partial capture, reversal vs void vs refund, and the failure modes that break settlement before it reaches your bank.
11 min read
-
PSP Reconciliation Failure Runbook: Break Types, Matching IDs, and Escalation Checklists
Three-way match (ledger / PSP report / bank statement), 10 break-type taxonomy, per-PSP matching-ID chain, and the escalation and evidence pack for every reconciliation failure.
15 min read
-
Payout and Disbursement Failure Runbook for Payment Operators
Four outbound-money failure flows (payout / settlement delay / refund failure / bank return): localize-the-leg, retry vs repair vs reissue vs cancel, idempotency controls, and the 6-KPI payout scorecard.
11 min read
-
Refund Operations: Controls, the Chargeback Double-Pay Trap, and Refund Fraud
The operator control stack for refunds: refund vs void vs reversal vs chargeback decision table, the double-pay trap, refund fraud controls, failed-refund recovery, and the reconciliation close loop.
13 min read
-
Marketplace Payment Operations: The Split-Payment & Connected-Account Runbook
Day-2 operator runbook for live platforms: three funds-flow models, seller KYB and capability gating, payout holds, negative-balance recovery, split refunds, and platform-scale reconciliation.
13 min read
-
Fraud Incident Response Runbook for Payment Operators
Cross-attack incident-command runbook: detect, triage, contain, communicate, recover, post-mortem — with severity tiers, proportional containment levers, and 7 incident-lifecycle KPIs.
11 min read