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.

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.

Owners: what's a way customers want to pay that your system just can't handle? Split three ways, part on a gift card, half now and half at pickup? And what do you do instead, by hand?

Claude Code 2.1.309 closed some sandbox gaps: shell startup files running outside it, write-deny rules that didn't follow symlinks, auto-accepted edits that could change the MCP config. A sandbox is a claim. Test it the way an attacker would, through the side doors.

Polygon closed its Coinme deal, and the headline is the paperwork: 37 state money transmitter licenses plus exemptions, covering 48 states. In US money movement, collecting licenses state by state can take years. Buying a company that already has them is the shortcut.

Builders: what's one task you stopped giving your AI coding agent after it went wrong once? Not the stuff it's bad at in general. The one time it cost you enough that you took that job back for good.

The one number worth pulling off your processing statement: your effective rate. Total fees for the month ÷ total card sales for the month. Example: $1,180 in fees on $40,000 in sales is 2.95%. It's the only fair way to compare quotes that are priced differently. A flat rate, an "interchange plus" quote and a tiered one all collapse into one number. What it hides: • Your card mix. More rewards and business cards push it up even if nothing about your pricing changed. • Your average ticket. The per-sale part of the fee (the 10¢ or 30¢) hits a $6 sale far harder than a $600 one. • How you take cards. Keyed-in and online sales usually cost more than tapped or dipped ones. • Slow months. Monthly fees stay the same when sales drop, so the rate jumps. So track it for 3 months, not 1. A single month can mislead you in either direction. And when someone quotes you a lower rate, ask them to show it against your actual statement, not a sample one.

Every "simple" payments feature request ends with the word "except." Refund it, except it already settled. Bill them monthly, except the card expired. Split it evenly, except one of them paid cash.

Codex CLI 0.164 added credential masking for some remote shell commands. Good. But hiding a secret in what the agent prints isn't the same as the agent not having it. If it can read the key, it can use the key. Scope the key, not just the log.

Owners: what's the one report you actually open every day? Sales by hour, the deposit, voids and refunds, tips, something else? And which report came with your POS that you've never once opened?

Meta on Muse: about a quarter of users have it shop, and the average order is over $200. Best detail from the call: in week one, Meta had to get Stripe to raise credit limits. Agent shopping didn't hit a model problem first, or a checkout problem. It hit a limit.

An appeals court just threw out the Fed's cap on big-bank debit swipe fees: 21¢ + 0.05% per sale. The ruling: only costs tied to a single transaction count, not a bank's fixed overhead. Merchants won the argument. What it does to your statement depends on the Fed's next move.

Payments teardown #3: the "Visa FANF" line on your statement. What it is: Visa's Fixed Acquirer Network Fee. Visa charges it to your processor every month, and most processors pass it on to you. How it's figured: • In-person sales: by your type of business and how many locations you have under one tax ID. • Online and phone sales: by how much Visa volume you run that way each month. • Do both and you can owe both parts. Who sets it: Visa publishes the fee tables. Your processor decides whether to pass it through at cost or add to it. What to look for: 1. Usually one FANF a month per tax ID, not one per terminal. 2. An amount that fits your size. A one-location shop shouldn't be paying like a chain. 3. A clear label. A vague "network fee" with no breakdown is worth a question. The question to ask: is my FANF passed through at Visa's cost?

Every AI agent shopping demo ends at "order placed." Real commerce starts at "this isn't what I ordered." Returns, partial refunds, the wrong size. That's the part nobody's demoing yet.

Owners: what's a payments lesson you only learned after it cost you money? A chargeback, a held deposit, a fee nobody mentioned, a contract you couldn't get out of. The expensive lessons are the ones most worth passing on.

Builders: your agent hits a permission check and gets told no. What should it do next? A) Stop and ask a human B) Try another way C) Log it and move on B is how you end up with an agent calling the bank's support line.