Free tools / Stripe decline codes / mobile_device_authentication_required
Stripe decline code: mobile_device_authentication_required
mobile_device_authentication_required is one of the decline codes Stripe returns when a card payment fails, in last_payment_error.decline_code on the PaymentIntent or outcome.reason on the Charge. Stripe's label for it is "Mobile device authentication required". Here is what it means, whether a retry can succeed, who can fix it, and what to tell the customer.
- Decline code
- mobile_device_authentication_required
- Type
- Authentication required
- Who can fix it
- The customer — needs to act
- Will a retry help?
- No: do not retry
What it means
The bank wants the customer to authenticate the payment on their phone or watch (in-person payments). Stripe's advice is to have the customer tap their device again.
Authentication required. The bank wants the cardholder to confirm the payment (3-D Secure / SCA). Stripe cannot retry headlessly; the customer must complete it from the hosted invoice.
Should you retry?
No: do not retry. No. The bank will refuse the same card as is, or Stripe or the network asked not to try again. Retrying wastes an attempt and can breach the card networks' reattempt rules. Change what is wrong, or ask for another card.
Recommended action
Who can fix it: The customer — needs to act. Ask the customer to tap their device again and authenticate. Not applicable to online subscriptions.
What to tell the customer
Short and neutral, ready for a checkout error, a billing page or a support reply. No placeholders — ready to paste.
Your bank asks you to confirm this payment on your phone or watch. Please tap again and confirm on your device, or pay with another card.
Customer email template
Neutral wording for this situation. Replace {name}, {product}, {link} and {company}.
Hi {name},
The payment for {product} needs the card to be used in person (PIN or phone confirmation), which isn't possible for this payment. Please pay with another card here: {link}
Thanks,
{company}Stripe's documentation
Stripe lists this code, with its advice for the customer, in its decline codes reference. The data on this page was last checked against it on 12 November 2026.
Related decline codes
Codes that behave the same way, to read next.
Handling many failed payments? See how FlowMRR helps you prioritize failed Stripe payments by revenue at risk.
Try FlowMRR free