A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Payments And Banking: The Shape Of The Answer," Kin Lane, October 22, 2026, https://apievangelist.com/2026/10/22/payments-and-banking-the-shape-of-the-answer/
Marisol works in payments operations at a mid-sized lender. Her job is mostly exceptions: the invoices, remittance notes and complaint emails that don't fit anywhere cleanly. She read the post on Thursday afternoon with a cold coffee and a queue of forty items she'd have to work by hand before five.
The line that stopped her was "Nobody in this industry wants a creative answer." She laughed, because it matched her week. Then she kept reading and felt a small, irritated resistance. The post says the hard part is agreeing on the shape, and that payments should be the easy case because the shapes were written down long ago. In her experience the shape was never what hurt. What hurt was the supplier who typed a reference number into the wrong field, or the remittance email that said two invoices and paid one. A grammar wouldn't fix that. She wrote a note to herself saying so.
But the post had already said it. It argues that a structured answer which is valid 99 percent of the time is a queue of exceptions somebody has to work by hand. Constraining output, it says, moves the remaining errors from formatting into meaning, which is where a human reviewer should be spending time anyway. Marisol read that twice. It conceded her point and then claimed it as the benefit. She wasn't sure she was persuaded, but she couldn't call it wrong.
She also noticed what the author didn't pretend to know. He couldn't load the registration authority's site and said so. He left card dispute codes out because he couldn't source them publicly. He warned that many of the catalog's schemas were derived work, not published by the providers. That made her trust the numbers a little more, though she still found the cohort scores hard to weigh. A mean of 38.4 for US open banking told her something about publishing and nothing about whether any bank's data was good.
The sentence that landed hardest was "That translation is still left to every team." She knew her own team was one of those teams. Somewhere in a shared drive was a pain.001 sample that someone had converted by hand into a JSON description years ago. Nobody owned it, and nobody could say whether it matched the XML anymore.
She didn't propose a model project. She didn't open a ticket or call a meeting. She had forty items to work.
At four-thirty she opened the repository and searched for pacs.008 and pain.001. She found seven files. She pasted their paths into a plain text list and added one line beside each: XML sample, prose description, or JSON that someone wrote by hand. Four were the last kind. She put the list in the team's notes page under a heading that just said what it was, and she left the question of what to do about it for Monday.
Then she went back to the queue. The next item was a remittance email that mentioned two invoices and paid one.