We scan new podcasts and send you the top 5 insights daily.
Different countries handle push payment fraud on instantaneous rails through contrasting liability frameworks. The UK mandates that banks absorb customer fraud losses up to a set cap, leading to measurable fraud reductions. India established a specialized central fund through the Reserve Bank to cover one-time customer reversals, whereas Japan relies heavily on ATM friction and tellers.
A Medallion Guarantee is a contractual risk-transfer tool, not insurance or a notary service. For high-value transfers, a customer's bank can issue a medallion to guarantee their identity, shifting the financial liability for fraud from the receiving institution (with little customer history) to the bank (with deep customer history), usually at no cost to the client.
In the Voyager bankruptcy, customers successfully reversed ACH payments by claiming fraud. The financial liability didn't fall on the bankrupt Voyager but on its partner, Metropolitan Commercial Bank. This shows how fintechs can unknowingly expose their banking-as-a-service providers to catastrophic, unpriced risk.
Binary decisions are brittle. For payments that are neither clearly safe nor clearly fraudulent, Stripe uses a "soft block." This triggers a 3DS authentication step, allowing legitimate users to proceed while stopping fraudsters, resolving ambiguity without losing revenue.
Businesses and financial institutions intentionally accept a certain level of fraud. The friction required to eliminate it entirely would block too many legitimate transactions, ultimately costing more in lost revenue (lower conversion) than the fraud itself. It is a calculated trade-off between security and usability.
Unlike with physical theft, victims of brokerage fraud are typically 'made whole.' This is not simply customer service; financial institutions have dedicated budgets for operating and fraud losses. Reimbursing customers is a planned, quantifiable cost of doing business in a system that prioritizes transaction velocity.
The slowness in traditional banking is often intentional, not a sign of outdated technology. These "bugs" are features designed to protect the most vulnerable 5-10% of customers from fraud like romance scams or elder abuse, which is a massive liability for banks.
Regulation E, a 1979 law, legally mandates that financial institutions bear liability for unauthorized electronic fund transfers. This forces banks to create robust, consumer-friendly dispute systems like chargebacks, making them appear responsive when they are simply complying with strict federal rules that protect consumers.
Unlike profitable credit cards, Zelle is a low-monetization service banks created to compete with fintech apps. Because it can't afford the fraud costs mandated by Regulation E, banks attempt to argue that customer-authorized (but fraudulent) transfers aren't their responsibility, creating a major policy conflict.
Growing prediction markets like Polymarket and Kalshi tolerated high fraud rates until their payment providers (like checkout.com), pressured by Visa and Mastercard, threatened penalties or de-platforming. This external pressure from upstream partners proved a stronger catalyst for action than the company's own financial losses from chargebacks.
Purely model-based or rule-based systems have flaws. Stripe combines them for better results. For instance, a transaction with a CVC code mismatch (a rule) is only blocked if its model-generated risk score is also elevated, preventing rejection of good customers who make simple mistakes.