Reading List
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.
Who this is for
Payments engineers and product managers building or operating subscription billing, SaaS, insurance, or any recurring-revenue product. Useful whether you are designing a new billing stack, evaluating a switch from card-on-file to direct debit, or trying to reduce failed payment churn across an existing multi-rail setup.
Reading order
The full reading list
-
Recurring Payments: Cards, Direct Debit, A2A, and Wallet Billing Compared
The cross-rail taxonomy: card mandates, direct debit, A2A/VRP mandates, and wallet billing compared on mechanics, failure rates, dispute risk, and geographic coverage. Start here to understand the full decision space — every downstream article is a deep dive on one leg of this map.
10 min read
-
Direct Debit Payments Explained: ACH, SEPA SDD, Bacs, and eGIRO
How direct debit works across ACH (US), SEPA SDD (Europe), Bacs (UK), and eGIRO (Singapore) — mandate setup, the three-day Bacs cycle, Nacha return codes, SEPA pre-notification, and consumer refund windows that create reverse-flow revenue risk. The operational baseline for any bank-account billing program.
10 min read
-
Merchant-Initiated Transactions: SCA, Reason Codes, Auth Rate Impact
Card recurring requires an SCA-anchored Cardholder-Initiated Transaction to open the MIT chain — most subscription operators misconfigure this and pay in auth rate penalties. SEC codes, network transaction IDs, MIT sub-types, and the PSP configuration checklist that gets this right.
11 min read
-
Network Tokens vs PSP Tokens: When Each Wins
Card expiry is the single largest source of involuntary subscription churn on card recurring. Network tokens issued by Visa Token Service or Mastercard MDES survive card reissues, are portable across PSPs, and deliver measurable auth rate uplift. When to prioritise VTS/MDES over PSP vault tokens — and the integration work required.
10 min read
-
SEPA Credit Transfer, Instant, and Direct Debit: Operator Guide
SEPA SDD Core and B2B in full operator depth: Creditor ID requirements, 14-day pre-notification rules, the 8-week consumer refund right, the five R-transaction categories (Return, Refusal, Reversal, Refund, Reject), and SCA exemptions for recurring SEPA collections. The implementation guide before signing up any European subscriber to bank-account billing.
11 min read
-
Subscription Rails: eGIRO, UPI AutoPay, SEPA SDD, Pix Automático
eGIRO, UPI AutoPay, SEPA SDD, and Pix Automático compared as recurring rails for operators billing in Singapore, India, Europe, and Brazil. Settlement timing, mandate setup friction, failure rate profiles, and the MDR advantage over card recurring in each market.
12 min read
-
Variable Recurring Payments (VRP): Open Banking vs Card-on-File
VRP is the open banking alternative to card-on-file recurring — standing consent, no card network, near-zero MDR, no expiry churn. UK sweeping VRP is live; commercial merchant VRP is rolling out through 2026–2027. Economics, consent mechanics, current bank coverage gaps, and the integration decision framework for UK-heavy subscription operators.
11 min read
-
Authorization Optimization: The Hidden Margin in Card Acceptance
Failed payments are recoverable revenue — but only if the retry strategy distinguishes hard declines (R07 authorization revoked, R02 account closed) from soft declines (insufficient funds). Retry logic, soft decline handling, 3DS exemption selection, and acquirer-level monitoring. The capstone for any operator who has reduced payment failures by fixing the rail and now needs to recover what slips through anyway.
7 min read