DEV Community: Tung@fizen

A field guide to Stripe decline codes, and what to actually do about each

Tung@fizen — Fri, 17 Jul 2026 13:00:00 +0000

TL;DR: Stripe tells you why a card failed. Most checkouts hide it. Here is the decode, mapped to the fix, so you stop guessing.

Every failed card payment comes with a reason from Stripe. The problem is most checkouts swallow it and show you "your card was declined." If you can see the actual decline_code (your dashboard, the API response, or support), the fix is usually obvious. Here is the cheat sheet I wish I had.

Disclosure: I work on Fizen, a payments product. No pitch here, this is the reference I use myself.

The ones you will actually hit

insufficient_funds. The honest one. Top up or use another card.
incorrect_zip / incorrect_cvc. AVS or CVC mismatch. Match the billing details to your bank exactly. Very common for non-US cards.
card_not_supported. The card type or country is not accepted for this purchase. Use a card from a supported region.
currency_not_supported. The card cannot do this currency. Same fix, different card.
do_not_honor. The vaguest one. The bank said no without saying why. Call the bank or try another card. Usually a risk flag.
generic_decline. No reason shared by the bank. Treat like do_not_honor.
transaction_not_allowed. The bank blocks this category or online use. Toggle international and online payments in your bank app.
fraudulent / lost_card / stolen_card. The bank flagged risk. Do not retry, contact the bank.
expired_card. Self-explanatory.
processing_error. Transient on Stripe or the bank side. Wait and retry once.
testmode_decline. You used a test card on a live key. Switch keys.

How to read them in practice

Soft declines (do_not_honor, generic_decline, processing_error) sometimes clear on retry or with a different card. Retrying a hard decline like stolen_card just digs the hole deeper.
AVS and CVC declines are on you and fixable in seconds. Most cross-border failures are one of these.
A code that says "country" or "not supported" is a policy or region problem, not a money problem. A different card from a supported region is the only fix.

Bookmark this for the next time a checkout just says "declined." If a code is missing here, add it in the comments and I will fold it in.

If your declines are specifically cross-border on USD tools, I wrote up the card side of it here.

You got into Kiro, SuperGrok or Manus. Now the payment will not go through

Tung@fizen — Mon, 13 Jul 2026 13:00:00 +0000

TL;DR: New AI tools ship payments last. Invite or region gates plus a half-built checkout mean a valid card still fails. Here is how to get through.

Getting off the waitlist for a hot new tool feels great. Then checkout greets you with a generic error and you are back to square one. I have hit this with Kiro, SuperGrok, Manus and a few vibe-coding tools that shipped access before they finished billing.

Disclosure: I work on Fizen, one of the card options below. I listed the non-crypto ones first because they fix most cases.

Why new tools are extra painful

Region rollout. Access opens globally, billing does not. The tool takes US and EU cards weeks before the rest.
Strict defaults. Early checkouts run strict Stripe Radar defaults and reject anything that looks cross-border.
Half-built flows. No 3DS handling, no clear error, no retry. You get "something went wrong," which tells you nothing.
Crypto-curious, card-only. Plenty of AI tools talk web3 and still only take a US card at checkout.

What clears it

Same pattern as older tools, the tolerance is just lower:

Use a card issued in a supported region (Wise, Revolut, or Mercury for a US entity).
If you hold USDT, a crypto-funded Visa (Fizen, Gnosis Pay, RedotPay) presents a real BIN in a supported region. Caveats: KYC, the supported list shifts weekly for new tools, and a merchant can still block the BIN.
Match the billing country on the form to the card, not your home address.

Before you waste an evening on it

Check the tool's billing or region docs. If billing is not live in your region, no card fixes that. Use a supported-region card or wait.
Read the exact error. "Not available in your country" is a policy gate. "Card declined" is a risk decline. Different fixes.
Try one supported-region card. If that fails too, it is the tool, not you, and a note to their support with the decline detail usually gets it fixed.

Which new tool tripped you up? Drop it plus your country and I will tell you if it is a known region gate.

I keep a running list of which new tools gate which regions here.

I give every SaaS subscription its own disposable card. Here is why

Tung@fizen — Wed, 08 Jul 2026 13:00:00 +0000

TL;DR: One card per subscription caps the blast radius when a vendor leaks, a trial auto-renews, or a price quietly jumps. Virtual cards make this free.

A while back a vendor I used got breached and my card was replayed on three other sites. I spent a weekend rotating one card across every subscription I owned. Never again.

Now every recurring service gets its own virtual card. It sounds fussy. It takes about ten seconds per signup and it has saved me real money and a few bad weekends.

Disclosure: I work on Fizen, one of the virtual-card options below. The others are here because I used them first.

Why one card per service is worth it

Kill switch. If a vendor leaks, or you hit a sticky cancellation, you delete the card and the charge dies. No support ticket.
Trial control. Set the card to a low limit. The "we charged you $240 for the annual plan" surprise stops happening.
Clean accounting. Each statement line maps to one tool. Reconciling spend across Cursor, Vercel, Supabase and ten others takes seconds.
Leak isolation. A breach at one vendor cannot replay on the rest, because each has a different number.

The options

Privacy.com. The original for this, per-merchant cards with limits. US only.
Revolut. Disposable virtual cards that regenerate per transaction, plus normal virtual cards you can freeze. Available in many countries.
Wise. Virtual cards you can freeze and replace, with good FX.
Crypto-funded cards. If you already hold USDT, cards like Fizen let you spin up many virtual cards under one account and fund from stablecoins. Caveats: KYC applies, and a merchant can still block the BIN.

How I actually run it

New tool, new virtual card. Name it after the tool so the statement reads cleanly.
Set a limit just above the plan price. A surprise annual upgrade gets declined instead of charged.
Cancelling something painful? Delete the card first, then cancel. The renewal cannot go through.

It is the cheapest security and budgeting habit I have. What is your setup? I am curious how others isolate SaaS spend.

Longer writeup on the card side, including limits, is here.

ChatGPT Plus and Claude Pro reject your card? It is probably the billing country, not the card

Tung@fizen — Sat, 04 Jul 2026 13:00:00 +0000

TL;DR: ChatGPT Plus and Claude Pro can reject a perfectly good card because your country is not on their billing list. The card is not the problem. The billing country is.

This one confused me for a while. My card was fine, address matched, no fraud flag, and OpenAI still bounced the Plus upgrade. Claude Pro did the same. Different failure from a normal decline, and the fix is different too.

Disclosure: I work on Fizen, one of the crypto-card options I mention below. The non-Fizen options are here because they genuinely work.

What is actually being checked

A normal Stripe decline is a risk score. This is a policy gate. OpenAI and Anthropic only sell subscriptions in a list of supported countries, and they infer your country from a few signals:

The issuing country of your card (from the BIN).
The billing country on the payment form.
Sometimes IP and account region.

If those say "unsupported country," you get a clean rejection with no useful error. It is not fraud. It is geography. A VPN alone almost never fixes it, because the card BIN still says where you are.

What actually clears it

The signal that counts most is the card's issuing country, so that is what you change.

Wise or Revolut, where the issued card maps to a supported region. Check which country your specific card is issued in, not where you live.
A US-issued card (Mercury if you have a US entity, Privacy.com if you are US based) clears almost everything.
A crypto-funded card if you already hold USDT. Fizen, Gnosis Pay, and RedotPay issue Visa cards whose BIN sits in a supported region, so the policy gate sees a supported country. Honest caveats: you still pass KYC, the supported-country list changes, and you are holding USDT, which is a custody choice, not free money.

Whichever you pick, set the billing country on the form to match the card, not your home address. Mismatched country is the most common reason these still fail.

A quick checklist before you upgrade

Confirm the tool supports your billing region at all. If it does not, only a card from a supported region will work.
Use a card issued in a supported country.
Match the billing country on the form to the card.
If it still fails, save the exact wording. "Not available in your country" is a policy gate. "Your card was declined" is a risk decline, which is a different fix.

Same trap exists on a bunch of AI tools right now. If you hit it on a specific one, name the tool and your country in the comments.

Longer breakdown, with the supported-region notes and which cards map where, is here.

Your card keeps getting declined by US dev tools. Here is what is actually happening

Tung@fizen — Tue, 30 Jun 2026 08:47:37 +0000

TL;DR: SaaS declines outside the US are almost always a risk decision, not a balance problem. Fix the billing address first, then use a card built for global online spend.

If you build outside the US, you know the moment. You pick a plan for Cursor, GitHub Copilot, or Vercel, hit Subscribe, and get "Your card was declined." No reason given. The same card works at the grocery store.

I dug into this as a developer, and now I work on payments. Here is what is actually happening, and what fixes it.

Disclosure: I work on Fizen, one of the crypto-card options below. I included the tools I would recommend either way.

Why it gets declined

It is rarely "no money." Most US SaaS bill through Stripe, so a decline is a risk score, not a balance check. The usual causes:

AVS mismatch. Stripe checks your billing ZIP against your bank. Non-US address formats fail this quietly.
BIN blocking. Your card's first digits encode the issuing country. Some Radar rules down-rank or block specific countries.
Prepaid and virtual filters. Many SaaS block prepaid BINs to stop trial abuse. A lot of "virtual cards" share those BINs.
3DS friction. Your bank wants an OTP the checkout never triggers, so the auth fails.

Stripe returns a decline_code. If the tool surfaces it (or support tells you), incorrect_zip vs card_not_supported vs do_not_honor points straight at the cause. That one string saves hours.

The fixes, lowest effort first

1. Fix the free stuff. Match the billing address exactly to what your bank has on file. Turn on international and online payments in your bank app. Retry in incognito to clear a device flag.

2. Use a card built for global online spend. Wise and Revolut behave well with USD SaaS and show the real FX rate. Mercury works if you have a US entity. Privacy.com is great but US only.

3. If you already hold stablecoins, a crypto-funded card. Fizen, Gnosis Pay, and RedotPay let you fund a Visa with USDT. What matters at checkout: it carries a real Visa BIN, you can spin up a virtual card per subscription, and there is no FX markup on recurring USD billing. Caveats worth saying out loud: you still pass KYC, a merchant can still block the BIN, and you are holding USDT, which is a custody choice, not free money.

What I run

One clean card with a correct billing address for strict merchants. One virtual card for the ones that reject the first. I log the decline_code every time. After two or three failures the pattern for your country is obvious and you stop guessing.

Stuck on a specific tool? Drop the tool and your country in the comments and I will tell you which lane usually clears it.

I keep a longer writeup on the crypto-card side, including limits and which merchants block which BINs, here. The fixes above stand on their own.