What happened
An Anthropic Console bug turned a $5.04 top-up into a $504 charge — a hundred times what the developer meant to spend — and it all happened on a single click. The developer is based in Costa Rica and was trying to add credit to his Anthropic API account.
The person behind the report is a LegalTech attorney who runs a development team out of Costa Rica. He was topping up his Anthropic API balance, the prepaid credit you need in order to use Claude through the company's developer platform, at claude.com. According to his account, the Anthropic Console bug swallowed the decimal point, read '5.04' as '504,' and processed the payment instantly.
Why the decimal point disappeared
Quick locale lesson, no engineering degree required.
In the US and the UK, we write five dollars and four cents as 5.04. In most of Latin America and large parts of Europe, the comma and the dot swap jobs: they'd write 5,04, and they use the dot for thousands — 5.000 means five thousand there.
So '5.04' is genuinely ambiguous depending on where you're sitting. Good payment software spots that ambiguity and either asks you to confirm or refuses the input. This one did neither. It silently stripped the decimal separator, kept the digits, and charged $504.00.
Think of it like a cashier reading your handwritten note wrong and swiping your card before reading the number back to you. You'd never accept that at a register. Online, we do it every day without noticing.
There was no confirmation screen
The missing second look is what turned a formatting quirk into a real loss. Nothing on screen summarized the final amount. No review page, no 'you're about to be charged $504.00' modal, no pause button. The transaction went through the same way a $5 top-up would.
In financial software, that's the guardrail most people assume is there. Here, it wasn't.
What it means for you
You don't need an Anthropic account for this to matter. Any form that takes your money can carry the same flaw. Here's how it plays out in ordinary life.
At home
You pay a utility bill through an app, fat-finger a decimal, and the same class of bug could overcharge you. The habit that protects you: never tap 'pay' until you've seen the number written out one final time. If there's no final number, treat that as a warning sign, not a shortcut.
At work
If you're the person who buys your team's software, one field like this can blow a monthly tooling budget in a single click. Ask whoever owns the accounts to keep a card just for subscriptions, so a weird charge is easy to spot the same day instead of at month-end.
For your business
This is where the math gets ugly. $504 hurts an independent developer. Type 50.00 into the same field, and by the reporter's own reasoning you're looking at $5,000.00 gone instantly. For a small agency or a two-person startup, that's payroll. Payment forms that don't restate the total before charging aren't a UX nitpick — they're a business risk.
For students
If you're learning AI on a student budget, never test a paid API with a card you can't afford to have frozen for a few months. Free browser tools give you most of the practice you need while you're still figuring out what a token even is. Here's a starter: MyKreaTool rounds up free AI tools you can use without handing over card details.
For creators
Subscriptions, credits, stock libraries, render minutes — creators juggle a dozen small payments a month, and every one of them is a chance for a silent overcharge. Screenshot the amount before you hit pay. It takes four seconds, and it's the difference between a refund and a fight.
For your income
The reporter has already filed a chargeback with his bank in Costa Rica. Here's the part people skip past: that money is gone from his account in the meantime, and banking processes there can take up to 120 days to resolve. Four months. So 'just dispute it' isn't a plan — it's a slow, uncertain recovery.
How to try it right now
Step 1: Start with something free
If you're curious about AI assistants and don't want a card on file, start there. MyKreaTool — the free toolbox I mentioned above — needs no payment details at all. You can test prompts, drafts and ideas without risking a cent.
Step 2: Know the number before you pay it
If you do want API access, head to the Anthropic Console and type your amount in whole numbers wherever you can. When a decimal is unavoidable, say the number out loud — 'five dollars and four cents' — then check that the screen agrees with you.
Step 3: Screenshot before you click
Capture the amount field and any confirmation that follows. If nothing asks you to confirm, that's your cue to slow down. The reporter's entire complaint is that a $504 charge moved exactly as fast as a $5 one.
Step 4: Watch for the charge
Check your banking app within minutes, not days. The sooner you spot a wrong number, the easier the dispute.
Upsides and what changes
Here's the honest upside: bugs like this get fixed when enough people make noise, and this story is already making noise. Locale handling is a known blind spot in payment code, and public reports push companies to validate input and show a confirmation screen before money moves.
For the rest of us, the change is behavioral. We stop trusting a payment form just because it looks polished. We stay on free tools while we're experimenting and only move to paid credits once we know what we're doing. And we stop treating 'file a chargeback' as a magic undo button, because in plenty of countries it isn't one.
Limitations
This is one person's account, and Anthropic hasn't publicly confirmed what happened on its side. We don't know how many users hit the same bug, whether it depends on a specific browser, region or card, or whether it's still live today — so treat the $5,000 figure as the reporter's own worst-case math, not a measured outcome. It's also worth saying clearly that this is about one payment flow, not the quality of the AI assistant you're buying; the model and the checkout page are separate things. Chargeback timelines, card rules and consumer protections also vary wildly by country, so your experience may look nothing like Costa Rica's 120-day window.
Conclusion
A decimal point cost one developer $504, plus a wait that could run four months.
The lesson isn't 'avoid AI tools.' It's 'never let a machine guess what you meant to spend.' Today's one action: open your banking app and check your last three software or subscription charges against what you expected to pay. If a number looks off, flag it now — the clock starts the moment the money leaves.
Comments 0