A working knowledge base on regulated payments.
Practical writing from inside payments product, infrastructure, cross-border, settlement, risk, onboarding and the product decisions that shape them.
How SWIFT Payment Works: A Complete Overview
SWIFT is messaging, not movement. Understand the difference and most cross-border problems become legible.
Read essay→A SWIFT Compliance Checklist for Banks and Fintechs
A working checklist of the SWIFT compliance items that audits, sponsors, and regulators actually ask about.
The Role of SWIFT in Emerging-Markets Banking
For emerging-market banks, SWIFT is not optional. The fragility is in the correspondents on either end of the message.
SWIFT Messaging Formats: MT vs MX (and Why It Matters Now)
MT was a printer-line format. MX is structured data. The difference is the entire next decade of cross-border product.
SWIFT and Cryptocurrency: The Honest Take
Stablecoins solve a real cross-border problem in specific corridors. They do not solve every cross-border problem in every corridor.
How to Track a SWIFT Payment Step by Step
If your bank cannot tell you where the payment is, the bank does not have the system. The system exists.
SWIFT in 2026: ISO 20022, Instant Rails, and the Pressure on Correspondent Banking
ISO 20022 is the past-tense story by 2026. The future-tense story is interoperability with instant domestic rails.
SWIFT Payment Delays: What Actually Causes Them
Most SWIFT 'delays' are not network delays. They are compliance reviews, cut-offs, or bad data.
SWIFT Fees, FX, and the True Cost of a Cross-Border Payment
The sticker fee is the smallest part of the cost. The FX margin is most of it. The product decisions decide both.
Correspondent Banking and the Reality of Emerging-Market Corridors
De-risking did not reduce risk. It moved the risk to the corridors that need access most.
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.
SWIFT, AML/CFT, and Sanctions Screening in Practice
Sanctions screening is where compliance theory meets throughput reality. The product decisions live in the list overlay, the matcher, and the review queue.
SWIFT gpi, Tracking, and the End of Payment Uncertainty
Before gpi, a cross-border payment was send-and-hope. After gpi, it is send-and-track.
ISO 20022 Migration: What Payment Product Teams Must Know
MT messages truncated reality to fit a 1980s field length. MX (ISO 20022) finally gives payments room to be structured.
SWIFT Payment vs Wire Transfer: Key Differences
'Wire transfer' is the outcome. 'SWIFT' is one way to instruct it. The two are not the same thing.
Sanctions Screening Without Killing Throughput
Sanctions screening is a latency problem and a false-positive problem dressed up as a compliance problem.
AML/CFT: Rules vs Models, and Why You Need Both
Rules are explainable and weak. Models are powerful and unexplainable. Production AML needs both, layered.
How Emerging Markets Pressure-Test Payment Product Strategy
Cards-first thinking, monthly settlement assumptions, and English-only UX do not survive contact with the markets that will define the next decade of payment volume.
PCI DSS and ISO 27001 as Product Programs
PCI DSS and ISO 27001 are not paperwork projects. Run as product programs, they make the platform measurably stronger.
Chargebacks Are a Product Problem
A rising chargeback line is product debt that finance is paying. The fix is upstream.
Payment Cost Is a Product Variable: From 50% to 1% (Tapmad Migration Playbook)
Payment cost is not procurement. It is product architecture. Here is the rail-mix playbook that pulled a subscription business from 50% to 1% cost-of-revenue.
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.
KYC and Conversion Designed Together
Splitting KYC from conversion produces the worst of both: friction that does not reduce risk, and risk that does not justify the friction.
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.
Cross-Border Corridors Are Operating Systems, Not Routes
Cards-first thinking breaks at the border. Owning the corridor abstraction is owning the margin in cross-border payments.
Financial Controls Are Product Requirements, Not Compliance Afterthoughts
If your audit trail is reconstructed from logs, you do not have controls. You have archaeology.
Onboarding Conversion vs. Default Rate: The Real Tradeoff
Conversion and default rate are not enemies. They are two sides of the same product surface.
Risk Tiering Merchants Is a Product Decision
Tiering is the single most leveraged product decision in a payments platform. Most teams hand it to risk and never recover.
KYB Automation Without Blowing Up Risk
Automated KYB is not about removing humans. It is about putting them where they actually add risk-adjusted value.
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.
Regulatory UX: Why the Name on a Payment Screen Can Block a Launch
Regulators do not read your roadmap. They read your screen.
Exception Management in Reconciliation
Exception management is where reconciliation either becomes a product or becomes a permanent ops queue.
Merchant Onboarding: Where Growth, Risk and Compliance Collide
Three teams own onboarding. The merchant only sees one experience. That gap is the product.
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.
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 consumer checkout standard that lifts authorisation rate and removes card-number entry. It works. It's just under-marketed. This is the operator-grade map.
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 don't touch. Default config gives you maximum step-up and minimum conversion. This is the operator's guide to the exemption logic that lifts auth rate without breaking compliance.
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.
Three-Way Reconciliation at Scale
Three-way reconciliation is the only model that survives multi-rail growth. Here is how to actually build it.
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.
Where ML Beats AI: Six Payment Problems an LLM Cannot Touch
There is a quiet AI-in-fintech mistake teams keep making: reaching for an LLM the moment the word 'AI' shows up on the roadmap. Sometimes the right answer is a gradient-boosted tree and a clean feature pipeline. This is the operator's argument for the boring choice.
Where PMOs Fail: Six Patterns I've Watched in Fintech Programmes
PMOs don't fail because the PMs are bad. They fail because the function gets miscast as governance theatre instead of decision-making infrastructure. Six failure shapes, the symptoms, the fix.
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
Open banking is not a data product. It is a workflow product that happens to use bank data as its raw material. Teams that miss this build pretty dashboards and weak businesses.
Product Management for Payments Platforms: What's Different, and What's Not
A payments PM is a SaaS PM with three extra constituencies and one extra reflex. Get the reflex wrong and the other constituencies stop trusting you.
GenAI in Fintech: 4 Production Use Cases That Actually Ship
Most fintech AI work in 2026 is still demos. These four use cases are not, they're running in production at $1B+ TPV across five regulated markets.
Project Management for Fintech Regulatory Programmes: PCI DSS, ISO 27001, SOC 2, AML/CFT
A regulatory programme is not a compliance exercise. It is a project with an immovable deadline (the audit), an external grader (the auditor), and a delivery cost (remediation) that gets paid up front or many times over.
Program Management vs Product Management in Fintech: Lane Lines That Actually Hold
Product and program management overlap because they have to. The overlap is where most fintechs break. Hold the lane lines and the overlap becomes the most productive seam in the org.
RAG for Merchant Integration Support: A Production Playbook
RAG is the right starting architecture for merchant integration support, but only if the corpus is curated, the citations are mandatory and the fallback paths are designed before launch.
AI-Powered Auto-Escalation: Cutting Payment Incident MTTR by 70%
The first 15 minutes of any payment incident is reconstruction work. An AI auto-escalation bot does that reconstruction in seconds, and your incident commander walks in with the diagnostic already done.
Value-Modeling GenAI Use Cases in Fintech: ROI, Feasibility, Data Readiness, Regulatory Risk
Most fintech AI roadmaps fail because they prioritise ambition over data readiness and regulatory risk. This is the four-axis framework that ships.
AI Fraud Detection vs Rule Engines: A Field Comparison
AI fraud detection beats rule engines on novel-attack detection. Rule engines beat AI on explainability and ops cost. The right answer is almost always a hybrid, and the design of the hybrid is the actual work.
Crypto On-Ramps: A Product Guide for Banks and Fintechs
A crypto on-ramp is a payments product, not a crypto product. The hard parts are KYC tiering, sponsor liquidity, FX exposure and Travel Rule, not the wallet integration.
Crypto Off-Ramps in Emerging Markets: The Real Plumbing
An off-ramp is only as good as the local payout rail underneath it. In emerging markets, that rail is the hardest, most fragile part of the entire crypto stack.
Stablecoin Payments in 2026: Where USDC, USDT and Bank-Issued Stables Actually Fit
Stablecoins are quietly winning the B2B cross-border settlement use case. They are still losing consumer acceptance. The interesting product work is at the boundary.
Building a PMO from Scratch in a Fintech: A 90-Day Playbook
A fintech PMO is not a governance overlay. It's the operating system that lets product, engineering, risk and compliance ship together at regulated-payments cadence.
PMBOK + Agile Hybrid Frameworks for Payments Teams
Pure Agile breaks on regulatory capital projects. Pure PMBOK breaks on product velocity. The right answer is a hybrid, and the design of the hybrid is the actual work.
Running a $3M Digital Transformation Programme: A Postmortem (TapmadTV)
What it actually took to land a $3M transformation programme on schedule across 5 technology workstreams and 8 vendors, and the three things I would do differently.
RAID Logs, SteerCo and the PMO Stack That Actually Ships at $1B+ Scale
Most PMO failure modes come from registers without owners, SteerCos without decisions, and OKRs without consequences. Fix the stack, fix the delivery.