In the architecture of card payments, there is a hard, physical boundary that does not exist in almost any other domain of distributed systems. When a customer dips a card at a merchant terminal, the Visa or Mastercard network initiates…
A practitioner’s notes on financial infrastructure A coffee shop in Tokyo (Merchant) accepts a Visa card issued by a small credit union in Ohio (Issuer). They share no database, no API contract, and no direct network path. The Cardholder taps…
It was 2AM. Most of the engineering team was asleep. The payment system was processing transactions normally. Then an alert fired. Duplicate charges were increasing. Not thousands. Not enough to immediately bring the entire system down. But enough to tell…
A coffee shop in Tokyo accepts a $5 Visa card payment. The customer taps their card. Within seconds: But the most important decision in the entire transaction did not happen at the terminal. It did not happen at the payment…
A customer taps a card at a coffee shop. The terminal reads the chip. The issuer receives the authorization request. The issuer approves the transaction. From the outside, it looks like a simple decision: “Does this customer have enough money?”…
Provisioning a digital wallet is not a user interface flow; it is a multi-party, asynchronous distributed transaction. When a user types a Primary Account Number (PAN) into a mobile wallet and clicks “Add Card,” they are initiating a complex orchestration…
