transaction_not_allowedDeclined for an unknown reason
Stripe's transaction_not_allowed decline is a hard decline: Billing won't retry without a new payment method. What it means and what to tell customers.
- Next step
- Customer should contact their bank
- Hard decline
- Yes, on Stripe's list
- Share the reason
- Yes
What does transaction_not_allowed mean?
The card was declined, and the issuer didn't give Stripe a specific reason.
Stripe documents the reason as unknown, but the code is on Stripe Billing's hard decline list.
What Stripe says to do
The customer needs to contact their card issuer for more information.
What to tell the customer
Ask the customer to contact their bank or add a different payment method.
Your bank didn't allow this payment. Please add a different payment method, or contact your bank to find out why.
Should you retry transaction_not_allowed?
No. Stripe lists this code as a hard decline. Stripe Billing won't retry the invoice on its own: scheduled retries stay on the invoice, but they only run after the customer adds a new payment method.
Before any retry, check the charge's outcome.advice_code. try_again_later means the issuer allows a retry, do_not_try_again means don't use the card again for this transaction, and confirm_card_data means some card details need checking.
Where transaction_not_allowed shows up
On a failed PaymentIntent, read last_payment_error.decline_code. On the Charge, the same code is in outcome.reason. Card declines usually come with the error code card_declined and the reason in decline_code.
Get failed payments in Slack
ChargeBell posts a Slack alert when a Stripe payment fails, with the amount, the customer, and Stripe's decline message. Open the payment from the alert to see its decline code, such as transaction_not_allowed, and follow up from there.