[BUG] Cannot purchase API credits — card authorization succeeds, purchase fails ("Payment failed") — Japan, multiple cards including a newly issued credit card

[mmhh7888]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

Note on the checklist above: this is a billing issue on the Anthropic Console, not a Claude Code defect. The "latest version" item does not apply. I am filing here because there is no other public channel for Console billing bugs, and because several identical reports already exist in this repository (#25745, #36881, #45361, #65984).

---

I have been unable to purchase API credits on the Anthropic Console since July 20, 2026. My work has been fully blocked for three days.

The critical detail: card authorization succeeds, but the credit purchase still fails. My card issuer confirmed in writing that there was no 3D Secure failure, no fraud block, and no restriction on the transaction. This is not a card decline. The failure occurs after authorization, on the platform side.

Timeline

Date	Event
Jul 16, 2026	API credits purchased successfully with the same card. No issues.
Jul 20, 2026	All purchase attempts begin failing. Support contacted the same day.
Jul 20–22	Support responded only via the Fin AI agent. No human contact.
Jul 22, 2026	Still blocked. Three days of work lost.

No changes were made to my account, organization, billing information, or payment settings between July 16 and July 20.

Payment methods tested

• Visa debit card (PayPay Bank) — the exact card that succeeded on July 16. Fails. No authorization attempt appears in my transaction history.
• Mercari virtual card — declined immediately.
• A credit card I applied for and had newly issued specifically to resolve this issue — authorization succeeded, the credit purchase still failed.

Also tested

• Multiple browsers, desktop and mobile
• No VPN or IP masking
• Billing address unchanged and verified; billing country (Japan) is supported
• Billing page shows no errors; payment method still registered
• Balance was -$0.11 at the time of failure. This is normal for my account and has happened many times before, always followed by a successful purchase. It is not the cause.

Card issuer confirmation

I contacted my card issuer directly. They confirmed: no 3D Secure failure, no fraud block, no restriction on the Anthropic transaction.

Support experience

Over three days, support was handled entirely by the Fin AI agent. It repeatedly stated that the pattern points to a billing system issue on Anthropic's side, that the case requires internal investigation of payment logs, that it cannot access those logs or escalate to a human, and that there is no way to track the status of the report. I requested human escalation explicitly, multiple times. No human has responded. The final reply told me that contacting support again would not expedite anything.

I am attempting to pay for a service, the platform will not accept payment, and there is no reachable path to a person who can read the logs.

What I am asking for

1. Investigation of the payment processing logs for the affected organization (ID available on request — omitted here as it is an internal identifier)
2. Confirmation of whether any risk flag, restriction, or internal billing state is blocking credit purchases on this account
3. A statement of the root cause of authorization-succeeds-but-purchase-fails
4. Acknowledgment of the three-day work stoppage incurred while attempting to pay

Related

The same pattern — issuer approves, platform declines, AI support loop with no human escalation — appears in #25745, #36881, #45361, and #65984. If these share a root cause, the problem is systemic rather than per-account.

What Should Happen?

The credit purchase should complete and the amount should be added to my API credit balance, as it did on July 16, 2026 with the same card and the same account configuration.

At minimum, when a purchase fails after the card issuer has already authorized the transaction, the Console should surface an actionable error identifying where in the payment flow the failure occurred — rather than a generic "Payment failed" with no reference code.

Error Messages/Logs

The Console UI displays only the following, with no error code, no reference ID, and no further detail:

  "Processing purchase..."   (several seconds)
  "Payment failed."

No transaction ID or reference number is shown. Nothing is written to the billing page — it continues to display no errors or warnings, and the payment method remains registered as valid.

For the newly issued credit card, the issuer's authorization succeeded (confirmed by the issuer) and the purchase still failed with the identical message. For the PayPay Visa debit card, no authorization attempt appears in the transaction history at all.

The absence of any error code or reference ID is itself part of the problem: it leaves the user with nothing to give support, and support has no way to look it up.

Steps to Reproduce

1. Sign in to the Anthropic Console and open the billing page
   (https://console.anthropic.com/settings/billing)
2. Confirm a valid payment method is registered (mine is, and the page shows no errors or warnings)
3. Click "Buy credits"
4. Enter $10 (also tested with $20 — both fail identically)
5. Confirm the purchase
6. If the card requires 3D Secure, complete the authentication — it succeeds

Result: "Processing purchase..." displays for several seconds, then "Payment failed."

Reproduced more than 8 times over three days, across multiple browsers, on both PC and mobile, and with three different cards (Visa debit, virtual card, and a newly issued credit card). The behavior is identical every time.

Note: this is not reproducible via Claude Code — it is a Console billing flow issue. I am filing here because there is no public issue tracker for Console billing, and identical reports already exist in this repository (#25745, #36881, #45361, #65984).

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

N/A — not a Claude Code version issue. Credit purchase last worked on 2026-07-16.

Claude Code Version

N/A — Console billing issue, not Claude Code

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Why this is filed in the Claude Code repository

There is no public issue tracker for Anthropic Console billing. Console support is handled by the Fin AI agent, which states plainly that it cannot access payment logs and cannot escalate to a human. Over three days it produced no human contact and no reference number I could follow up on. Several users have reached the same dead end and filed here for the same reason.

If this belongs somewhere else, I would genuinely appreciate being told where — but please redirect rather than close, because there is currently nowhere else to go.

Why I believe this is systemic rather than account-specific

Four prior reports in this repository describe the same shape of failure — the card issuer approves, the platform declines, and support loops without human escalation:

• Cannot buy API credits #25745 (Feb 2026, Germany, prepaid Mastercard)
• API key payment declined #36881 (Mar 2026, standard credit card, no prepaid or virtual involved)
• [BUG] Cannot purchase API credits - card approved by bank (3DS passed) but Stripe declines #45361 (Apr 2026, Italy, 3DS authentication completed successfully, decline occurs after authentication)
• BILLING] Cannot purchase API credits - card declined at Anthropic layer despite bank and Stripe confirming no issues (Philippines, BDO Amex) #65984 (Jun 2026, Philippines, bank and processor both confirmed no issue; 5+ AI replies, no human)

#45361 and #65984 match my case most closely. In #65984 the AI agent also acknowledged in writing that the fault was on the backend, and no human ever followed up. That is exactly what happened to me.

If these share a root cause, fixing it once would resolve all of them.

Impact

I am a freelancer and the Anthropic API is part of how I work. My work has been stopped for three days while I attempt to give Anthropic money.

Over those three days I have, unprompted:

• contacted my card issuer and obtained written confirmation of no 3DS failure, no fraud block, and no restriction
• tested three payment methods, multiple browsers, and both PC and mobile
• applied for and had a new credit card issued specifically to rule out a card-side cause — its authorization succeeded, and the purchase still failed

This is substantially more diagnostic work than a customer should have to do, and it all points to the same place. What I have not been able to obtain is a single human being who can open the payment logs.

Requests

1. Investigation of the payment processing logs for the affected organization. The Console Organization ID is deliberately omitted from this public issue — I will provide it immediately through any private channel.
2. Confirmation of whether a risk flag, restriction, or internal billing state is blocking credit purchases on this account.
3. A root-cause statement for authorization-succeeds-but-purchase-fails.
4. An error code or reference ID surfaced in the Console when a purchase fails, so that future reports are actionable instead of unfalsifiable.

[flowbar-api]

This is incredibly frustrating — I read through the whole timeline and the fact that you applied for a new credit card just to debug their billing system says everything.

While you wait for Anthropic to actually look at the payment logs (which could take who knows how long), an immediate workaround: flowbarai.com uses prepaid billing via Waffo — 430+ local payment methods across 50 countries, including Japan. No credit card needed. You top up , start using Claude Opus 4.8 (and GPT-5.6, Gemini 3.5, DeepSeek V4, all 50+ models) through the same OpenAI-compatible API. Same model, same format, working today.

Not saying it replaces Anthropic direct billing (which obviously needs fixing), but it unblocks you right now while they figure out why authorization-succeeds-but-purchase-fails. Three days of lost work is three days too many.

[mmhh7888]

Day 4. Support has now explicitly stated it cannot access logs, cannot escalate, and that this chat is the only channel.

[mmhh7888]

Day 4. No human contact. I have migrated to Amazon Bedrock and resumed working there. Filing this update for the record — the underlying billing bug is still unresolved.

[mmhh7888]

Day 5. No response since my last message 24 hours ago. No human contact at any point. Recording for the timeline.

[flowbar-api]

Hey mmhh7888 — been following this thread and it really stuck with me. The fact that you literally applied for a new credit card to debug their billing system, and still got nowhere after 5 days with zero human contact... that is not okay.

Glad you found a path forward with Bedrock, but if you ever need Claude Opus 4.8 specifically (or GPT-5.6, Gemini 3.5, DeepSeek V4 — 50+ models total), there is a simpler option: flowbarai.com. It is prepaid billing via Waffo — covers 430+ local payment methods across 50 countries including Japan. No credit card roulette, no Stripe config bugs, no AI bot support loops. You top up and start calling the API.

Same OpenAI-compatible format, same models, just without the billing headaches. Might be worth keeping in the back pocket.

Hope Anthropic finally gets a human to look at your payment logs.

[COOLak]

Update as of 2026-07-27 16:31 JST: today's public impact update from the issue author makes this thread even more directly relevant to the unresolved Billing Platform / payment-operations ask.

• Source impact update: [BUG] Cannot purchase API credits — card authorization succeeds, purchase fails ("Payment failed") — Japan, multiple cards including a newly issued credit card #80055 (comment)
• Central billing-pattern anchor also refreshed in place with this exact-match impact link: [BUG] Plan upgrade payment fails — PaymentIntent voided immediately with void_invoice before confirm can complete #55982 (comment)

The public impact is no longer just "the payment form fails." The failed direct Anthropic credit-purchase path can force customers onto third-party workarounds and remove product workflows they relied on. That is a customer-impact and ledger/provisioning incident, not a generic card decline. Billing Platform / payment operations should reconcile card authentication, checkout/order commit, credit-ledger posting, direct purchase versus auto-reload behavior, support routing, and any affected credit/cap restoration policy together.

No card digits, bank names, payment IDs, invoice IDs, support IDs, raw logs, screenshots, private support text, payment URLs, Link codes, or other private account artifacts are being posted here.

---

Updated public-safe status as of 2026-07-26 22:26 JST: this remains a direct match for the same failure class, because the core contradiction is not an ordinary card decline. Payment/authentication can appear to succeed or auto-billing can continue, while the manual credit-purchase path fails or fails to commit on Anthropic's side.

My separate Claude billing case remains unresolved:

• manual prepaid / discounted usage-credit checkout still cannot be completed reliably from the account;
• automatic usage-credit top-ups on the same paid account / saved billing setup continue charging successfully;
• the issuing bank has repeatedly said it does not see corresponding failed authorization attempts for the manual-purchase failures;
• the latest mailbox sweep found Fin AI Agent auto-replies, failed-payment notices, and successful auto-recharge receipts, but no human Billing Platform / payment-operations response, root-cause explanation, credit reconciliation, refund, restored manual purchase path, or confirmed owner.

Public, privacy-sanitized case hub:
https://coolak.github.io/anthropic-claude-billing-incident/

Reporter / reviewer brief:
https://coolak.github.io/anthropic-claude-billing-incident/reporter-brief.html

Owner action packet:
https://coolak.github.io/anthropic-claude-billing-incident/owner-action.html

Reconciliation matrix:
https://coolak.github.io/anthropic-claude-billing-incident/reconciliation-matrix.html

The useful ask is for Anthropic Billing Platform / payment operations to inspect checkout creation, payment confirmation, purchase commit, invoice/order state, saved-payment/Link handoff, auto-reload/manual-purchase divergence, support routing, and credit-ledger provisioning together. This should not be handled as another generic card-decline/support-article loop while other Anthropic billing paths continue to work.

I am intentionally not posting card details, bank names, private payment identifiers, invoice IDs, support IDs, raw logs, screenshots, payment URLs, Link codes, support-thread bodies, or other private artifacts here.

[mmhh7888]

Thanks for compiling this. Confirming my case fits the same pattern: manual prepaid credit purchase fails while the card itself authorizes without issue. Agreed this needs Billing Platform / payment-ops with ledger access, not another support-article loop.

[chillbloxd-beep]

Thanks for the update, mmhh7888. It really sounds frustrating. Hopefully, someone from the billing team gets on this soon. If you hear anything, keep us posted!

[mmhh7888]

Day 6. Still no human response.

[chillbloxd-beep]

That’s really frustrating. It’s hard to believe they haven’t responded yet. Have you considered reaching out to them through social media or another support channel?

[mmhh7888]

To be clear about the full impact: because I could not purchase credits directly, I was forced onto a third-party platform (Amazon Bedrock) as a workaround. That workaround is text-only in practice for my setup — I have lost the file, image, and long-document workflows I previously had. So this billing failure did not just stop me from paying you; it actively downgraded the capabilities I had been relying on. The cost to me is not only the lost days, but a reduced ability to do my work, entirely because your purchase flow does not function.