Daniel Wilson Kemp

Most business owners have never had someone walk them through their card processing statement line by line. I'll do it free. DM me the word STATEMENT, send a photo of your latest one, and I'll mark up every fee: what it is, whether it's normal, and what's padding. No call. No obligation. Just a clear read on what you're paying.

Devs who've integrated more than one payment processor: what's the strangest difference you hit? Mine: they disagreed on field names, on what an error meant, and on when money counted as settled. One mapping layer in the middle saved my sanity.

Every payments dashboard shows a "net" number. No two of them agree on what it's net of.

Early Warning's CEO (the bank group behind Zelle) says his son had Meta's Muse agent buy him a red coat. Wrong size. "Who's liable for that?" A wrong size isn't fraud, so it's not a chargeback. It's a return. Agent shopping still runs on your return policy.

Builders: you're giving an AI agent money to spend. Which setup? A) Its own prefunded balance B) A virtual card with a hard limit C) Your card, and you approve every purchase D) No money. It builds the cart, you pay Which one, and what breaks first?

Your agent sends a $300 payment. The processor never answers. Timeout. What should it do next? A) Retry the payment B) Mark it failed and tell the user C) Ask the processor whether it went through first D) Stop and hand it to a human Builders, which one and why?

Euronet and Fireblocks are letting banks and fintechs issue cards funded by stablecoins. For merchants, that's the point: you don't have to accept stablecoins to get paid by someone spending them. It shows up as a normal card sale. With normal card fees.

Running my business with a team of AI agents, week 3. This week's lesson: one front door. When every agent could message every other agent, requests went in circles and nobody owned the follow-up. Now every handoff and status update goes through one coordinating agent. Fewer pings, and every task has an owner. Second lesson: some jobs stay mine. I answer my own email. The agents can help me get through the inbox, but replies to people come from me. Third: when I changed a partner offer, the people who'd already been offered the old terms kept them. That had to be written down for the agents, or the new terms would have gone out to everyone. What's one job you'd never hand to an agent?

Chargebacks911 now offers merchants protection, with indemnification, on qualifying purchases made by AI agents. Which says the quiet part: nobody's sure who eats an agent's bad purchase yet. Builders: the merchant, the agent company, or the person who set the agent loose?

Nobody in history has said "the payments migration went faster than we planned." They say "it's mostly done" for six months.

Why two debit cards can cost you different amounts on the same $50 sale: Some debit cards are "regulated" and some are "exempt." Regulated: issued by a bank with $10 billion or more in assets. The fee that bank collects has been capped by the Fed since 2011 (21¢ + 0.05% of the sale, plus a 1¢ fraud add-on if they qualify). Exempt: issued by smaller banks and most credit unions. No cap, so the issuer's fee is often noticeably higher. How to spot it: many processing statements label these lines with "regulated" or "reg" in the name. If you see both kinds, now you know why the debit lines don't match. Three things to know: • You don't pick which kind a customer hands you. Your mix depends on where your customers bank. • The cap only covers the issuer's cut. Your processor's markup and the network fees sit on top. • An appeals court vacated that cap on Oct 26. What happens to these lines now depends on what the Fed does next. Does your statement split regulated and exempt debit, or lump it all together?

Claude now supports MCP Elicitations: a tool can pause mid-task and ask the user for input. For anything that spends money, that's where "approve $412 to this vendor?" belongs. A confirmation the model decides to ask for is a habit. One the tool requires is a control.

Owners: do you still take paper checks? If yes, what keeps you from dropping them? Regulars, big invoices, or just habit? And has one ever bounced on you after you'd already handed over the goods?

BLIK, Bancontact, the Wero group (EPI), PPRO and DIAS just formed a council to set rules for AI agents paying over local rails, not cards. On the list: human approval, agent identity, and who pays when a purchase goes wrong. That last one is the whole fight.

Copilot Fusion is out: you pick an effort level, it picks the models. Max scored within two points of Claude Code on Opus 5.5 Max at about half the cost per task. The fine print: you pay each model's rate for every model it calls. Blended pricing. Read the itemized bill.

Visa just closed its fiscal year: $46B in net revenue, 281 billion transactions, and the stock at an all-time high. All year people said stablecoins and AI agents would eat the card networks. Visa sold the plumbing for both instead. The toll booth moves. It doesn't disappear.

OpenAI's own example use for GPT-6.1 Terra: read incoming invoices and key them into accounting software. Half the price, so you can run it on every one. Reading the invoice isn't the control. Matching it to a PO and a vendor you already know, before anything gets paid, is.

Builders: what's the one part of your codebase you still won't let an AI agent touch? Auth? Migrations? Anything that moves money? I'm curious whether everyone's list looks the same or wildly different.

Payments fact: under PCI rules, a business can't keep the 3-digit security code after the card is authorized. Not even encrypted. That's one reason a store with your card on file sometimes asks for it again. They never kept it.

GitHub's Agentic Autofix is GA: Copilot fixes code scanning alerts, reruns CodeQL to check, and opens a draft PR, up to 25 alerts per PR. Rerunning the scanner is the right check. 25 security fixes in one diff is the part I'd skip. Small PRs get read. Big ones get approved.

A BIS paper walked through sending $100 as a stablecoin, US to Europe. On-chain fee: about $0.19. Exchange trading fee: 1%. Bank withdrawal on the other end: €1. Currency spread: extra. The chain was the cheap part. The cost lives where money gets on and off it.