mobile_device_authentication_requiredThe customer needs to tap their phone again
Stripe's mobile_device_authentication_required decline means the payment needs authentication on the customer's phone. Ask them to tap again.
- Next step
- Customer should authenticate or use a PIN
- Hard decline
- Not on Stripe's list
- Share the reason
- Yes
What does mobile_device_authentication_required mean?
The transaction requires authentication, so the card was declined.
What Stripe says to do
Ask the customer to retry the payment by tapping their mobile device again.
What to tell the customer
Ask the customer to tap their phone or watch on the reader again.
Please tap your phone on the reader again to approve the payment.
Should you retry mobile_device_authentication_required?
Yes. Stripe's next step is to have the customer tap their device again. It isn't on Stripe's hard decline list, so Stripe Billing retries follow your Smart Retries or custom schedule.
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 mobile_device_authentication_required 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 mobile_device_authentication_required, and follow up from there.