Thank you very much for your support with this. I appreciate you stepping in, acknowledging the engineering flaw, and escalating my case.

As additional feedback on the automated support pipeline: I understand the desire to automate and make processes more efficient. However, a person should not have to rely on getting a post to the top of Hacker News just to bypass AI bots and get a human to look at an obvious financial error. Luckily, you were here and acted proactively, which I truly value.

I will await the support team's communication.

Pura vida!

Note to others who are blaming Amthropic in various ways. This is what taking responsibility is.

Note also that Anthropic outsources the billing and metered billing to a third party still, who is doing very well with the growth. It’s a more recent company in the space so it comes with a lot of bugs that are getting learned with time which is why there are so many interesting (at scale) and obvious errors (billing systems are build over years not months) being corrected with time.

I’ve reported this 3 months in a row and nobody seems to be hearing.

Is it possible? I guess, but I doubt they're being honest about what was being displayed on the screen.

Please note that I typed 5.04 (with a dot), not a comma.

I was doing a manual account recharge (adding credits), where the user defines an arbitrary prepaid amount. On a localized system/keyboard setup, entering the dot did not alter the total due or warn me of a 100x increase before hitting the submit button.

Also, the core issue is the complete lack of a final checkout/confirmation step for an arbitrary recharge amount. In proper financial UX, clicking the primary button should trigger a modal stating: "You are about to recharge your account with $504.00 USD + $65.52 VAT. Total due: $569.52. Confirm payment?". Executing an instantaneous credit card charge on a single click while silently processing ambiguous inputs is precisely the dangerous design flaw I am pointing out.

Saludos,

Thanks for validating my point, and I understand your frustration too. Luckily, in your case, as the seller, you can edit the listing afterward; I can’t. I have to deal with Anthropic, which already charged me $569.52.

Sad....

Going back to your serious notes, I successfully replicated the exact mechanics of this bug inside the Console, and it is a classic frontend race condition/bypass flaw:

When your system/keyboard is in a locale that uses commas, the input text box still physically allows you to type a dot (like typing 5.04 or 0.5). The catastrophic UX failure happens because if you press the "Enter" key immediately after typing, the form submits the raw, un-sanitized string to the backend before the frontend validation layer can intercept it, block it, or refresh the "Total due" box.

It completely bypasses its own validation rules (like the $5.00 minimum enforced minimum), skips any error prevention, and fires the single-click payment request to the gateway instantly with the misinterpreted value.

I uploaded the live replication screenshot here: https://ibb.co/HTY88MZ3

Please note that English is not my native language. I used AI to make sure that my technical explanation of the decimal bug was clear and well structured so that the community here could understand it.

I agree that the text structure might look robotic, but the $569.52 unauthorized charge on my credit card right now is 100% real.

Pura vida!

To be 100% clear: I wanted to load exactly five dollars and four cents ($5.04) into my account. I typed 5.04.

The core problem here is that in secure financial pipelines, ambiguous inputs must trigger a validation error and reject the transaction, not silently guess the amount and execute a 100x overcharge.

If Anthropic's backend expected a comma due to my regional settings and couldn't parse the dot, the correct engineering behavior is to throw an "Invalid Format" message and disable the pay button. Silently stripping the decimal character and instantly draining $569.52 (including local VAT taxes) from a user's card with zero confirmation screen is a catastrophic failure in error prevention.

Gracias!