Payment APIs
Payment APIs are where partner enablement, idempotency and developer experience meet regulation. Essays here cover API surface design, local payment methods and the developer experience underneath.
Field notes for this hub.
UAE Open Finance Needs a Control Plane
The UAE Open Finance question is not only whether APIs exist. It is whether consent, service initiation, participant identity and settlement evidence survive the operating model.
UK Open Banking Has a Product Scale Scorecard Now
UK Open Banking's one billion payments and 100 billion API calls should push product teams from adoption storytelling into a harder scale scorecard: reliability, consent completion, VRP quality, fraud, disputes, and cash-flow outcomes.
Stripe Projects Shows Agentic Products Need Cost Boundaries
The product lesson is not that agents can provision services. It is that agent-native products need explicit cost, credential, environment, and evidence boundaries.
Mercado Pago's Claude Plugin Turns Payment Docs Into Controls
Faster scaffolding is easy; faster confidence is the real product. Mercado Pago's four Claude Code workflows move payment rules, webhook tests, credential checks, and review into the developer's path, as long as version drift is governed.
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.
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.