PSPs are prioritizing their engineers' experience above anyone else's| news.alvaroduran.com
Building Payments to fail as soon as possible| news.alvaroduran.com
PSPs are satisfied when you receive the data you need, even if you get it multiple times| news.alvaroduran.com
How domain knowledge turns caching into an easy problem| news.alvaroduran.com
How the boundaries between the conflicting ledger modes inform the design of a ledger that could do both.| news.alvaroduran.com
Choosing Relational Databases for Payments was the result of a historical accident. Should the payment industry move on to better alternatives?| news.alvaroduran.com
Why Building Payments, Why Doing it in Python, and How To Do It Effectively| news.alvaroduran.com
When to hedge fraud risk, and when not to, in the land of strict regulation.| news.alvaroduran.com
What a database paper can teach us about scaling payment systems beyond a single relational database| news.alvaroduran.com
Payments technology is improving fast, and it would be a shame if your customers abandoned you because you didn't pay attention to it.| news.alvaroduran.com
A Revolution in Payments Technology May Start With Lego-like Primitives and Narrow Focus on a Commoditized Complement| news.alvaroduran.com
Me-as-a-Service is a superior business model to domain-specific software| news.alvaroduran.com
Paradigms succeed when you can strip them for parts. Protocols allow precisely that.| news.alvaroduran.com
Why Open Source Payment Applications Is An Opportunity Hidden in Plain Sight| news.alvaroduran.com
Well-run payment systems are developed by engineers who understand what is the best use of their time: to catch unknown unknowns, and to do it fast.| news.alvaroduran.com