Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

Customers cannot get through 3D Secure on my Stripe checkout

Short answer

3D Secure is the bank's check, triggered by rules such as Strong Customer Authentication, a bank's soft decline or your Radar settings. A payment that needs it waits in requires_action until your checkout shows the bank's screen and the customer finishes. If your page cannot display it, or the payment happens without the customer present, it fails.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • The payment spins forever or returns to the form.
  • Customers say the bank asked for a code and then it failed.
  • Failures cluster in European or UK customers.
  • Subscription renewals fail with authentication required.
  • It broke after I changed my checkout, my security policy or my app.

Why does this happen?

  1. The checkout never shows the bank's screen

    A payment that needs 3D Secure moves to requires_action, and your front end has to display the authentication step. If the code ignores that status, the customer sees nothing and the payment never completes.

  2. Regulations and banks can require it

    Stripe triggers 3D Secure automatically if regulations such as Strong Customer Authentication in Europe require it, when an issuer asks with a soft decline, or when your Radar rules request it. The requirement comes from the bank.

  3. The authentication frame is blocked or sandboxed

    If the bank's screen is shown in an iframe, a content security policy must allow js.stripe.com, hooks.stripe.com and your return address. Stripe says the sandbox attribute must not be used on that frame, because some issuers fail when sandboxed.

  4. Renewals happen with nobody there

    Not every transaction supports 3D Secure, for example off-session payments. For a subscription payment that needs the customer to authenticate, Stripe sends an invoice.payment_action_required event and your system has to tell the customer to complete it.

  5. Customers abandon or fail the step

    If authentication fails the payment returns to requires_payment_method and the customer has to try again or use another card. Stripe notes that card issuers control how the screen looks.

What can I do about it today?

  1. Test with Stripe's test cards in test modeStripe publishes test cards that require authentication, and the test flow shows a mock page where you can authorise or fail. Use that, never a real card.
  2. Try the checkout on phone and desktopNote whether a bank screen appears, and in which browser the payment fails.
  3. Check failed payments in StripeOpen the payment and read its status and decline reason. requires_action means the customer was never taken through the step.
  4. Ask what changedA new checkout, an app update, a security header or content security policy change, or new Radar rules.
  5. Do not look for a way to turn authentication offStripe says you cannot manually turn off 3D Secure through its APIs, and where regulations require it, unauthenticated payments are blocked anyway.

When should I bring someone in?

  • Many customers fail at the authentication step and sales are dropping.
  • Subscription renewals need authentication and your system does not email customers.
  • You use a custom checkout or an app that does not show the bank's screen.

How do I handle it?

  1. Reproduce it with test cardsI run authentication-required test cards through your real checkout, on web and mobile.
  2. Fix the displayThe checkout handles requires_action, opens the bank step in the way Stripe documents, and handles failure and retry.
  3. Check security headersContent security policy and iframe rules are checked against Stripe's required domains.
  4. Handle off-session casesCustomers are emailed when authentication is needed on renewals, with a page to complete it.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Does 3D Secure protect me from chargebacks?

Stripe says successful 3D Secure typically brings liability shift for eligible fraud disputes, but it cannot be assured for any specific payment or dispute.

Why only some customers?

The bank decides. Rules differ by region and by card, and some cards or wallets do not support it at all.

Do I have to build the screen myself?

Not always. Stripe says PaymentSheet on mobile supports 3D Secure automatically, and the bank controls the look of the screen. A custom checkout has to handle the step.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.