Payment Infrastructure
Payment infrastructure is the product surface where orchestration, ledger, settlement and risk meet. These essays and case studies cover what it actually takes to ship and operate a multi-rail platform at scale.
Shipped in this domain.
Simpaisa Payment Infrastructure Platform
A regulated, multi-rail payments platform processing $1B+ annual GTV and 270M+ payments a year across pay-in, payout, wallets (DCB/IBFT), card acquiring (MPGS/MDES), settlement, FX and cross-border corridors, PCI DSS and ISO/IEC 27001 certified.
Settlement + Reconciliation Engine: 99.95% Accuracy at $1B+ GTV
A multi-rail settlement and reconciliation engine, canonical double-entry ledger, three-way auto-reconciliation, exception management and corridor-aware payout windows. Closed the gap between treasury, finance and product at $1B+ GTV.
MPGS Acquirer Integration Programme: Hosted Session, 3DS2, Tokenisation and the Recurring Stack
Took a regional acquirer-processor from a single Hosted Checkout flow to a full MPGS surface, Hosted Session, EMV 3DS2 step-up, scheme tokenisation, recurring billing and dispute ingestion, across a 150+ merchant portfolio in three primary markets without a 24-hour outage.
MDES + VTS Network Tokenisation Rollout: 92% Coverage and the Auth-Rate Lift That Pays For Itself
Migrated 150+ merchants from PAN-on-file to scheme-token credentials across MDES (Mastercard) and VTS (Visa), replaced three vault providers, rewired the recurring engine, and lifted post-tokenisation authorisation rate by 1.8 points portfolio-wide.
3DS2 Step-Up Optimisation: From 38% Frictionless to 73% Without Lifting Fraud
Rebuilt the EMV 3DS2 step-up programme for a regional acquirer-processor — per-issuer risk-based authentication, the full 3DS2 frictionless / data-only path suite, abandon-recovery flows — lifting frictionless rate from 38% to 73% over three quarters while holding portfolio fraud below the 6 bps scheme fraud-monitoring threshold.
Click to Pay (VCTP + MCTP) Programme: Scheme-Led Checkout, Recognised Cardholders, and 7.2pt Conversion Lift
Designed and shipped Click to Pay across a regional acquirer's top-tier merchant cohort, VCTP (Visa Click to Pay) + MCTP (Mastercard Click to Pay), recognised-cardholder enrolment, multi-card wallet, lifting CNP checkout conversion by 7.2 points on the routed traffic.
Field notes for this hub.
Satispay's Mastercard Cards Turn a Wallet Into a Card Programme
Satispay is turning a closed-loop wallet into an open-loop card programme with Mastercard. The hard part is keeping the wallet's simplicity while absorbing card tiers, FX rules, disputes, and scheme discipline.
Checkout.com Shows Pay-In and Payout Need One Control Plane
One vendor for acquiring and issuing removes handoffs, but the value only lands when customer collection, supplier payout, liquidity, risk, and reconciliation agree in one control plane. Travel exposes the gap first.
Cross River and Stripe Show Why Agentic Cards Need a Mandate Ledger
A single-use virtual card can protect credentials. It cannot, by itself, prove that an agent stayed within the user's mandate.
Amex and Apple Pay Turn Rewards Into a Checkout Control Plane
Putting Membership Rewards inside Apple Pay makes the wallet an issuer product surface, not merely a place to store a payment credential.
Processor-Only Card Issuing Moves the Work, Not the Risk
Processor-only issuing hands you the ledger, regulatory reporting, dispute operations, fraud policy, and the sponsor-bank relationship. If you cannot name who owns each one, you are not ready for it.
Visa and Mastercard Join Open USD: The Stablecoin Battle Moves to Distribution
Forget the 140-partner logo wall. Open USD's real move is sharing reserve earnings with everyone who distributes the token, and Visa and Mastercard joining that compact rather than fighting it.
Revolut and Adyen's UAE Licences Show What Dubai Wants From Fintech
Revolut and Adyen got different UAE licences in June 2026. The shared message is that Dubai wants locally controlled payment operations, not thin market-entry stories.
Thredd and Sutton Turn BIN Sponsorship Into an Operating Model
A BIN sponsor shortens the route to a US card launch; it does not shorten the list of decisions someone must own. Thredd and Sutton Bank make the three-party split, sponsor, processor, and programme manager, explicit.
AmEx and ABA Show Vertical Cards Are Infrastructure
The ABA American Express Business Card is a useful signal: vertical card programmes are moving from affinity branding into operating infrastructure for professional services.
The Bank of England's Stablecoin Rules Are an Operating Model
The Bank of England's systemic stablecoin rules are not just a regulatory update. They define the operating model that serious payment products will have to build around.
Zodia's Luxembourg Licence Turns Stablecoin Custody Into Payment Infrastructure
Zodia's new Luxembourg Payment Institution licence lets it custody and transfer stablecoins under one roof. Custody, EMT transfer, settlement, treasury, and reconciliation are collapsing into a single institutional product surface.
Mollie's EEA Expansion Is a Localisation Infrastructure Bet
Mollie is committing EUR350 million over five years to ship local payment methods, onboarding, support, settlement, and reconciliation as one merchant operating system. Country coverage was always the weak proxy.
Boku's UPI Launch Is a Local-Rail Export Story
Boku's first cross-border UPI transactions are not just another local payment method. They show how domestic instant rails are becoming export infrastructure for global checkout.
SWIFT vs Card Rails vs Local Wallets: When to Use What
There is no universal best rail. There is the best rail for this corridor, this amount, this customer, this use case.
Agentic Commerce: What Visa and Mastercard Are Really Building
A shopping agent that compares, selects, and pays under authority you set is a new economic actor. Visa, Mastercard, OpenAI, and Stripe are racing to build the trust layer that lets merchants and issuers accept it.
Payments PRD Template: The 9 Sections Every Senior PM Should Write
A payments PRD is not a SaaS feature brief with a money movement appendix. It has to explain state, risk, settlement, compliance and operational failure before engineering starts.
Layered Fraud Controls in the Payments Stack
No single fraud control survives a determined attacker. Layered controls do, and they do it without crushing conversion.
Why Local Payment Methods Are a Developer-Experience Problem
A merchant adopts a local payment method only if integrating it is as easy as integrating cards. Most LPM integrations fail that test.
Financial Controls Are Product Requirements, Not Compliance Afterthoughts
If your audit trail is reconstructed from logs, you do not have controls. You have archaeology.
Ledger Design for Multi-Rail Payments
The ledger is the source of truth for the entire platform. Most teams discover this after they have shipped the wrong one.
Hosted Checkout vs Direct Card Processing: A Product Maturity Guide (MPGS, MDES, 3DS)
Why hosted checkout is the right first step and the wrong last step, and what direct card processing actually demands from a product team.
Settlement Windows and Merchant Trust
Merchants do not churn because of fees. They churn because of settlement uncertainty.
BIN Routing and Scheme Selection: When To Override the Card-Brand Default
BIN routing is the last unglamorous lever in card acquiring. It sits below product, below 3DS2, below tokenisation, and on a portfolio the size of a billion, it moves more authorisation rate than most things the team will ship this year.
Click to Pay (VCTP / MCTP): The Scheme-Led Checkout Standard, How It Actually Works
Click to Pay is the schemes' answer to Apple Pay and Google Pay: a scheme-owned checkout standard that lifts authorisation rate and removes card-number entry. It works. It is just badly marketed. This is the practical map.
Compelling Evidence 3.0 (Visa): What Changed, and How To Actually Win Disputes Now
Compelling Evidence 3.0 is the most consequential dispute-rule change Visa has shipped in a decade. The mechanics look like a documentation update; the operating implication is a complete rework of how acquirers capture, store and present transaction evidence.
CyberSource Architecture: The Visa-Owned Payment Gateway, How It Differs From MPGS
CyberSource is the gateway Visa wants you to standardise on. The product surface is broader than MPGS: Decision Manager and Flex Microform have no Mastercard equivalents, but the integration patterns and lifecycle traps are different in important ways.
EMV 3DS2: Step-Up Logic, Frictionless Flow and the Auth-Rate Optimisation Nobody Explains
3DS2 is the most consequential auth-rate lever most merchants never touch. Default config gives you maximum step-up and minimum conversion. This is the field guide to the exemption logic that lifts auth rate without breaking compliance.
How Credit Scoring Systems Actually Work: From Feature Pipeline to Bureau Reporting
Reaching for an off-the-shelf credit-scoring vendor is easy; the trap is stopping there. The vendor's output is a number. The substance an operator has to own is the pipeline that produces it, the governance that protects it, and the bureau reporting cycle that keeps it current.
Mastercard Send + Visa Direct: Push-Payment Architecture Compared
Mastercard Send and Visa Direct are the two card-rail push-payment products that quietly underpin the gig-economy, insurance-disbursement, gaming, marketplace-payout and remittance flows users now treat as instant. They look interchangeable in marketing decks. They are not.
MENA + South Asia Payment Infrastructure: A Country-By-Country Operating Map
Every operator entering MENA or South Asia gets a market deck from the local consulting partner. The deck is well-presented and operationally useless. This is the deck that would actually have helped, the regulators, the rails, the wallets, the flows that matter, and the launch sequence that does not collapse.
Nigerian Payment Rails: NIBSS, NQR, eNaira: How the Stack Actually Works
Nigeria has built one of the most ambitious public-rail payment stacks of any emerging market: NIBSS, NIP, BVN, NQR, eNaira, all interlinked under the CBN. Anyone entering Nigeria gets a stack deeper than the deck suggests and a regulator more active than they expect.
Payment Infrastructure Is Not Just APIs, It Is State, Trust and Failure Handling
APIs are the easy part. The hard part is what happens between the auth response and the bank statement.
PSD2 SCA Exemptions: TRA, Low-Value, Recurring, Trusted Beneficiary, MIT, and How To Actually Use Them
PSD2 SCA exemptions can materially lift card-not-present conversion. The five exemptions are well-documented in the RTS; the mechanics that make them ship are not.
Three-Way Reconciliation at Scale
Three-way reconciliation is the only model that survives multi-rail growth. Here is how to actually build it.
What Is A Core Banking System (And When Do You Actually Replace It)?
A core banking decision is usually inherited, not made, and it shapes the next decade of the company. This is the operator's view: what cores actually do, when to replace them, and why marketing-deck replacement timelines are nearly always wrong.
MDES + Network Tokenisation: How It Actually Works (and Why You Should Default to It)
Network tokens are the most under-explained product in payments. They are the difference between a 60% authorisation rate and a 90% authorisation rate on stored cards. Default to them. Build for them. Migrate to them.
MPGS Architecture: How Mastercard Payment Gateway Services Actually Works (and Where It Breaks)
MPGS is a payment gateway the way SAP is an ERP: vast, powerful, and indifferent to whether you understand it. The integration choices you make in the first sprint decide whether the platform scales for five years or rots for five.
Reconciliation Is Product Infrastructure, Not Back Office
If finance is your reconciliation system, you do not have one. A practitioner view from running multi-rail settlement at scale.
Virtual Card Accounts (VCA): The Quiet Backbone of B2B, Travel and Marketplace Payments
VCAs look like a card primitive. They are actually a control primitive. The product job is to decide which controls travel with the number, and which sit in the platform.
Open Banking Product Architecture: Aggregator vs Direct, AISP vs PISP, and Where the Value Actually Lives
Teams that treat open banking as data access ship pretty dashboards and weak businesses. The ones who treat it as a workflow product, with bank data as raw material, build category leaders.