Key Takeaways

  • Real-time rails eliminate the clearing buffer: Zelle dominates US consumer volume while FedNow and RTP struggle for parity.
  • The UK mandated bank reimbursement up to £85,000 for Authorised Push Payment (APP) fraud after instant account-to-account rails made scams irreversible.
  • Settlement finality is political, not technical: US banks answer to Regulation E, meaning legal enforcement dictates who pays regardless of software architecture.
  • Japan's post-fraud legal remedies fall flat because scammers pull cash out of mule accounts within minutes, dropping the balance to zero before court freezes arrive.

Speed Kills the Fraud Buffer

Most software engineers think finality is a database state. You flip a bit, funds transfer, and the transaction closes. Patrick McKenzie shows that in banking, finality is an illusion negotiated between statutes, banks, and the state.

When clearing took three business days, banks had time to spot suspicious patterns, freeze wires, and reverse errors. Instant payment rails strip away that buffer.

McKenzie points out the current race in American banking: “And there are two competing standards for doing substantially instantaneous payments between bank accounts in the United States, but Zelle is the one that has mostly the adoption right now. One is FedNow, which the payment wag joke for many, many years has been calling it FedLater, and the other is RTP, which stands cleverly for Real-Time Payments.”

When you build payments around instant settlement, push transactions change the game. In a credit card swipe, the buyer can dispute the charge through a chargeback. In a push payment, the sender actively authorizes the transfer. If a con artist convinces a user to push money, the user approved it. From a strict protocol perspective, the transfer is valid. From a social perspective, someone just lost their life savings.

Who Eats the Cost of Speed?

Nations answer this problem differently, and the choice determines who survives in fintech.

In Britain, instant transfers through Faster Payments created an epidemic of push fraud. “So the UK, as a broad feature, bank accounts allow you to do instantaneous payments between bank accounts at almost any pound amount. And this has caused a lot of what's called APP fraud, A-P-P, APP fraud.” Rather than letting users absorb the damage, UK regulators stepped in with a strict rule: banks must reimburse victims up to £85,000.

McKenzie explains the shift: “So the UK said, 'Okay, well we're going to make the banks eat that one in the same way that Regulation E in the United States makes banks largely finally responsible for certain forms of fraud committed against users, and then the banks in the US offload it elsewhere.'”

Technologists often imagine payment networks can self-regulate through code. McKenzie cuts through that fantasy: “Until the people with guns stop enforcing Regulation E, guidance to customer service representatives about finality is not actually controlling.”

Look at Japan for the counter-example. Japan tried to fight scams with physical friction, including bank teller questions and freezing accounts tied to money mules. But instant rails bypass physical friction.

McKenzie notes the breakdown: “The problem with this is that in Japan, since money movement is substantially instantaneous, and since getting cash out of the financial system is still not all that weird of a thing to do, very frequently the amount of money that was in the mule's account at the point of the legal process being sent against it was nearly zero.”

By the time the victim calls their branch and police initiate paperwork, the money is paper yen in an envelope.

What to Do With This

Audit your product's withdrawal and payout logic by Friday. If you allow immediate outbound transfers to freshly linked accounts, insert a mandatory 24-hour delay or a $500 velocity cap on first-time payees. Do not rely on bank-level finality to protect you from clawbacks or regulatory pressure once your users get tricked.