The Payments Engineer Playbook

The Payments Engineer Playbook

Home
Glossary
Archive
About

payment-systems

Modern Treasury's Stablecoin Sandwich
After acquiring Beam, Modern Treasury wants to become the developer-first API for moving money in any form.
 • Alvaro Duran
Why AI Commerce Isn't Going Anywhere
Human Not Present payments are technically possible, but socially unacceptable
 • Alvaro Duran
How To Prevent Cache Stampedes
Think cache invalidation and naming things are hard?
 • Alvaro Duran
How To Review Code That Deals With Money
You're probably focusing on the wrong things. It doesn't look as good as you think.
 • Alvaro Duran
How to Build Payment Webhooks Fast
It's not that webhooks are difficult.
 • Alvaro Duran
The ID Gapless-Latency tradeoff
You can get unique identifiers at scale either by Coordinating or by Centralizing ID creation. But you can't get gapless sequences without having to…
 • Alvaro Duran
Paying At The Pump: Why Auth and Preauth Are Not The Same Thing
And how it affects implementing new payment methods that look "similar" from the outside
 • Alvaro Duran
Testable Payment Webhooks
PSPs are prioritizing their engineers' experience above anyone else's
 • Alvaro Duran
The Joy of Being On Call For Payment Systems
How to be at ease when every second counts
 • Alvaro Duran
Why Payments Are Path-Dependent
A winning strategy to go around DNHs and improve payments authorization
 • Alvaro Duran
Code-First Reliability in Payment Systems
Building Payments to fail as soon as possible
 • Alvaro Duran
Why Payments Aren't Money Movements
Payments are contracts, and require an ecosystem of tools on top of transfers
 • Alvaro Duran
© 2026 Alvaro Duran Barata · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture