not_permittedhighAffects MRR

Stripe not_permitted Error — Causes, Fix & MRR Impact

The Stripe not_permitted error occurs when the issuer does not permit the payment (e.g. transaction type or merchant category), causing the decline and MRR risk for SaaS businesses processing subscription payments.

What this means

The bank does not allow this payment (e.g. card or account restrictions). The customer should try another card or contact their bank.

Why it happens

Transaction type not allowed

The card or account does not allow this type of transaction (e.g. recurring, international, online).

Merchant category restriction

The issuer restricts payments to certain merchant categories; your business may be in a blocked category.

Card product restrictions

The card product (e.g. certain prepaid or corporate cards) has restrictions that block this charge.

Account or region restriction

The issuer restricts by region, merchant, or account status.

MRR Impact

Charges fail until the customer uses a permitted method; offering alternatives and clear messaging protects MRR.

Not permitted declines require another payment method; strong update flow and alternatives protect MRR.

Avg. recovery rate: Good when customer can use another card or method; retries on same card rarely help.

Urgency: within 24h

How to fix it

  1. 1

    Do not retry same card

    When decline_code is not_permitted, do not retry the same PaymentMethod. The issuer has stated this payment is not permitted.

  2. 2

    Show clear message

    Tell the customer their card does not allow this type of purchase and they should try another card or contact their card issuer.

  3. 3

    Offer alternative payment method

    Provide a direct way to add another card or choose a different payment method (e.g. ACH, different card brand).

  4. 4

    Send dunning email

    Email that the payment could not be completed and ask them to update their payment method or contact their bank. Include link to billing.

  5. 5

    Log for insights

    Track not_permitted; if you see patterns (e.g. certain BINs or regions), consider promoting alternative payment methods for those segments.

Detect not_permitted automatically

Track not_permitted volume; consider offering alternative payment methods prominently for affected segments.

Monitor your Stripe health free →

FAQ

What does Stripe not_permitted mean?
not_permitted means the payment is not permitted (e.g. card or account does not allow this type of transaction). The customer should contact their card issuer. For SaaS, do not retry the same card without a change; prompt the customer to use another card or contact their bank.
Should I retry not_permitted?
Retrying the same card usually will not help; the issuer has indicated the transaction is not permitted. Ask the customer to use another payment method or contact their issuer to enable this type of purchase.
How do I message not_permitted?
Show a generic message: 'Your card was declined. This type of purchase may not be allowed on your card. Please try another card or contact your card issuer.'
Does not_permitted affect MRR?
Yes. Failed charges reduce MRR. Offering an alternative payment method and clear instructions (contact bank or try another card) helps recovery.

Related errors

card_not_supported

The Stripe card_not_supported error occurs when the card does not support the type of purchase (e.g. recurring or international), causing the charge to be declined and MRR risk for SaaS businesses processing subscription payments.

Affects MRRtransaction_not_allowed

The Stripe transaction_not_allowed error occurs when the card issuer does not allow the transaction (e.g. type or context), causing the decline and MRR risk for SaaS businesses processing subscription payments.

Affects MRRrestricted_card

The Stripe restricted_card error occurs when the card is restricted (e.g. reported lost or stolen) and cannot be used for the payment, causing the decline and MRR risk for SaaS businesses processing subscription payments.

Affects MRR