In the previous article, we examined how domestic batch rails move money. Batch rails trade speed for computational efficiency, while instant rails (like FedNow) trade deferred state for immediate finality. But both operate under a silent architectural assumption: liquidity is effectively infinite.If a million consumers send $500…
We had a performance problem. So we did what seemed like the obvious thing. We added more application capacity. The system got slower. At first, the numbers didn’t make sense. The system was serving traffic across multiple regions, and workload…
A card payment looks simple from the outside. A customer taps a card. The terminal displays “Approved.” The merchant continues serving the next customer. But underneath that two-second interaction is a global messaging protocol that allows thousands of independent financial…
You sit at a closing table and sign a mountain of paperwork to buy a house. A few days later, the seller receives a wire transfer for €300,000. To understand where that €300,000 came from, you have to look past…
A payment system can be healthy in almost every traditional sense. CPU utilization looks reasonable. The database is responding normally. Kafka is processing messages. Network latency is within limits. There are no obvious application errors. And yet payment latency suddenly…
On Friday afternoon, you receive an email from your employer: “Your direct deposit has been processed.” You open your banking app. The money is not there. You check on Saturday. Still not there. It finally appears on Monday morning. The…
