The API worked. The books did not. A clean REST interface with pretty JSON still leaves accounting stitching exports for three days to answer one question - what happened to this payment across every rail and every failure path. ERP-grade APIs treat the contract as a shared language with finance.
Subscription billing has two bad options today - store the card or chase a manual approval every cycle. Variable recurring payments add a third: pre-authorized variable amounts with limits enforced by the rail. The UK is building it now, and the lesson for everyone else is about regulatory cycles, not technology.
The CFO sees "save 3 percent on transactions" and the math looks obvious. Treasury sees continuous settlement at 3 AM and a reconciliation process built for batch. Before you switch to account-to-account, count the operating cost the savings slide leaves out.
A $2.3M wire hit the system at 2:47 AM on a Friday, the rule saw "large wire" and chose Fedwire, and Fedwire does not run weekends. The transaction waited until Monday. The fix is not a faster rule - it is routing that understands business context.
Every failed payment kicks off a chain of manual work that rarely shows up in a fraud dashboard. Across the top 15 US banks, dispute processing alone runs about $3 billion a year - and the wire flagged at $50K costs the same to investigate whether it is real or not.
ACH cleared overnight, wires ran on business hours, and float was predictable. FedNow and RTP ended that. With 42 percent of RTP payments landing nights, weekends, and holidays, treasury teams are positioning cash by the hour - and the Fed discount window still keeps bankers' hours.