Skip to content

Foxhound menu

Card Not Supported

`card_not_supported` is Stripe's decline code for a card that doesn't support the type of purchase being attempted. In practice this shows up on some prepaid cards, certain international card products, or card types that aren't set up to handle recurring or subscription billing at all. The card itself may work fine for other kinds of purchases, it just isn't built for this particular transaction type.

card_not_supportedNo automatic retry

Why it happens

This one is worth calling out because it behaves a little differently from the purely technical declines above. Recurring billing is a specific transaction type, and not every card product is provisioned to support it. Some prepaid cards are issued only for one-time point-of-sale purchases and reject recurring authorization attempts by design. Certain cards issued outside the merchant's primary market carry network restrictions that block subscription-style charges even though the card works for standard purchases. And some card products, regardless of country, are simply configured by the issuing bank to not permit recurring charges. It is not a fraud signal and not a closed-account signal, but the underlying cause is a card capability limitation rather than a bank outage, so Foxhound does not file it with the technical network declines.

How to fix it

Stripe's guidance for this code is that the customer should use a different card. Retrying the same card asks the same card product to do something it isn't set up to do, so switching payment methods is the real fix. Foxhound sends no silent retry for this code and goes straight to customer outreach. The ask to the customer should be specific: this card doesn't support recurring charges, please add a different card, rather than a generic "your payment failed" message that doesn't explain what's actually needed.

How Foxhound recovers it

This code has no dedicated bucket in the recovery engine's classification sets, so it fails closed rather than defaulting to a silent retry: no repeat charge runs against a code Foxhound cannot classify. Recovery goes straight to the same email sequence expired cards get, carrying the hosted card-update link, until this code earns its own bucket.

Questions

  • Why would a working credit card get declined with `card_not_supported`?

    The card product itself may not be provisioned for recurring or subscription-style charges, even though it works fine for one-time purchases. This is common with certain prepaid and international cards.

  • Is `card_not_supported` a sign of fraud?

    No. It's a capability limitation on the card product, unrelated to fraud screening or the legitimacy of the transaction.

  • Will retrying a `card_not_supported` decline eventually work?

    Sometimes, if the block was a temporary network-level restriction. But if the card product structurally doesn't support recurring billing, retries will keep failing and a different payment method is needed.

  • How should the customer email differ for `card_not_supported` versus a technical network decline?

    It should be specific: explain that the card doesn't support recurring charges and ask for an alternative payment method, rather than a generic payment failure notice.

  • Does Foxhound retry `card_not_supported` the same way it retries a technical decline like `processing_error`?

    No. A technical decline gets a background retry before any customer email, but `card_not_supported` gets no silent retry: retrying the same card rarely helps, so Foxhound starts with the email asking the customer for a different card.

See what this looks like on your account

The free audit shows what Stripe already recovered and what is still dying, no signup required.

Run your free audit