Claude Pro Card Declined — Why It Happens and How to Fix It

Cause 1 — Your bank is blocking international or online-AI merchants

This is the most common cause by a wide margin, and the easiest to fix. Many banks — particularly in Nigeria, India, Pakistan, Egypt, Turkey and Argentina — block international online transactions by default, or cap them at a very low monthly limit in foreign currency.

The tell: the decline happens instantly, and your banking app shows either nothing at all or a declined entry with a code. Fix: open your bank app and look for a setting named "international transactions", "online/e-commerce transactions", or "foreign currency limit". Enable it, raise the limit above the plan price, and retry. In several countries you must call the bank or visit a branch to lift this, and some banks impose a monthly foreign-currency allowance measured in tens of dollars.

Cause 2 — The card is prepaid or virtual and the BIN is refused

Anthropic's payment processor rejects many prepaid and virtual card BINs as a fraud-control measure. This catches a lot of the crypto-funded card products people reach for after cause 1.

The tell: a physical bank card from the same country works, but your virtual card fails immediately regardless of balance. Fix: try a different issuer — BIN acceptance varies a lot between them, and issuers that present as a commercial credit BIN rather than a prepaid BIN fare better. There is no way to know in advance other than testing with a small balance. If two or three issuers fail, this route is closed for you and a gift subscription is the practical alternative.

Cause 3 — 3-D Secure / OTP is failing silently

If your card requires 3-D Secure and the OTP goes to a phone number you no longer have, or the verification popup is blocked, the charge fails without a useful message.

• Disable pop-up blockers and any aggressive privacy extension for claude.ai, then retry.
• Confirm the mobile number registered with your card issuer is current — this is the usual culprit for expatriates.
• Try a different browser in a normal (non-private) window; some 3-D Secure flows fail in private mode.

Cause 4 — Billing address mismatch (AVS)

The address you type at checkout has to match what your issuer holds. A mismatched postcode alone is enough to trigger a decline with a generic error.

Fix: copy the billing address exactly as it appears on your bank statement, including postcode format. If your country has no postal codes, try your bank's placeholder — many issuers store "00000" or the city name. Do not invent a US address to appear domestic; that mismatch fails AVS and looks like fraud.

Cause 5 — Country or sanctions restriction

Anthropic does not serve every country, and payment processors apply their own sanctions screening on top. If you are in a restricted jurisdiction the decline is a policy outcome, not a technical fault, and no card will work.

Cause 6 — Insufficient available balance including the FX buffer

The charge is in USD. Your issuer converts it and often adds a 1–3% FX fee, and some issuers place a temporary authorisation slightly above the charge amount. A card holding exactly $20.00 will fail a $20 charge more often than not.

Fix: keep at least 10% headroom above the plan price on the card.

The order to work through them

The six causes above are not equally likely and not equally expensive to test. This is the sequence that finds the answer fastest and cheapest.

1. Open your banking app and check whether international or online transactions are enabled, and what your monthly foreign-currency limit is. This is cause 1 and it is the single most common answer.
2. Confirm the card has at least 10% headroom above the plan price, to absorb the FX fee and the authorisation hold. That is cause 6, and it is free to rule out.
3. Re-enter the billing address exactly as it appears on your statement, including postcode format. Cause 4, thirty seconds.
4. Retry once in a normal browser window with pop-up blocking and privacy extensions disabled, keeping your banking app open for the verification code. That tests cause 3.
5. If it still fails and the card is prepaid or virtual, test a different issuer with a small balance before funding one properly. Cause 2 cannot be argued with, only worked around.
6. If every card from your country fails regardless of issuer, stop testing cards. That is cause 5, and no card will work.

Reading the actual decline code

Anthropic bills through Stripe, and Stripe passes back a machine-readable reason your issuer gave. Claude.ai shows you a generic message, but your banking app, your card statement or a call to the issuer will often surface the underlying code — and the code tells you which of the six causes you are actually in, which saves you working through all of them.

What to actually say to your bank

Most first-line bank staff will tell you "there is no block on your card" because they are looking at a fraud-hold screen rather than your channel permissions. That answer is usually wrong, and the way past it is to ask about specific settings by name rather than asking why a payment failed.

• Ask: "Are international online transactions enabled on this card?" — not "why was my payment declined".
• Ask: "Is there a monthly foreign-currency limit on this card, and what is it?" Some banks default this to the equivalent of $20–$100 a month, which a Max plan exceeds outright.
• Ask: "Is e-commerce or card-not-present spending enabled?" These are separate permissions at many issuers, and one can be on while the other is off.
• Ask them to whitelist the merchant by name if the decline persists after both are enabled. Give them the descriptor exactly as it appears — the merchant will show as Anthropic, not as Claude.
• Give the date and time of the attempt. Without it they often cannot find the authorisation record at all, and will tell you nothing was attempted.
• If the first agent insists there is no block, ask to be transferred to the cards or international-payments team. The first line frequently cannot see these flags.

One detail worth knowing before you call: a decline that never reached the issuer will not appear on their system at all. If the block is at the processor rather than your bank — which is what causes 2 and 5 both are — the bank will truthfully say they never saw the transaction. That is diagnostic information, not a dead end: it means the problem is not one your bank can fix.

The mobile app route, which costs you nothing to try

This one is underused and it is free, so try it before you pay anyone a markup. A subscription bought on the web goes through Stripe. A subscription bought inside the Claude iOS or Android app is billed by Apple or Google instead, against whatever payment method your app store account already holds — which can include store credit from a gift card bought locally in your own currency.

• Install the Claude app, sign in to the same account, and start the upgrade from inside the app rather than in a browser.
• If your store account has credit, the charge draws on that and never touches your bank card.
• App-store gift cards are sold in ordinary shops in most countries, in local currency, with no international transaction involved.
• The plan you get is the same plan on the same account. Only the billing rail differs.

Declines at renewal are a different problem

Everything above assumes a first purchase. A card that worked for months and then fails at renewal usually has a narrower set of causes, and people waste time re-checking settings that never changed.

• The card expired, or the issuer reissued it with a new number and expiry after a fraud event. The stored details are simply stale.
• The issuer withdrew standing authority for recurring foreign charges — some banks review these periodically, and a rule that allowed the charge last month can lapse.
• A one-off fraud hold is sitting on the card from an unrelated transaction, and every subsequent charge fails until you clear it.
• The renewal amount changed — a plan or currency change can exceed a per-transaction cap that the old amount cleared.

Update the card on file before the retry window closes rather than waiting for the plan to lapse. Failed renewals are typically retried on a schedule for a few days, and a card fixed inside that window restores the plan without a gap. This is also the failure mode a gift subscription cannot have, because there is no card on file to fail — which is the honest argument for the gift route rather than "it is faster".

What Anthropic support can and cannot do

Support is worth contacting, but only for a specific subset of these problems, and knowing which saves you several days of waiting.

If none of the six fixes work

At that point you are dealing with a structural block rather than a configuration problem, and the options narrow to two. A different card issuer with a better-accepted BIN, if you can pass their KYC. Or a gift subscription, which removes the card from the equation completely — you pay in crypto, receive a redemption code, and apply it to your own account.

The gift route costs more than a working card would. It is worth it when the alternative is no access, and not worth it if a five-minute setting change in your banking app would have fixed cause 1. Try the free fixes first — we would rather you did.