3D Secure Failures at Checkout: Why UK and EU Customers' Cards Get Declined
Short answer: In the UK and EU, the card issuer often has to confirm that the real cardholder is paying, which is what 3D Secure does. Payments fail at this step when the customer never sees the bank prompt (blocked pop-up, in-app browser, closed tab), cannot complete it (old phone number, banking app not set up), or when your integration charges a saved card without the customer present and the bank asks for authentication anyway. Most of these are fixable: use a provider-hosted or properly embedded authentication flow, set up saved cards and subscriptions with the right flags, explain the step to customers, and read the actual failure reason in your payment dashboard before changing anything.
Strong Customer Authentication in plain words
Strong Customer Authentication is a rule for card payments in the UK and European Economic Area. It asks for two out of three things: something the customer knows (a passcode), something they have (their phone or card reader) and something they are (fingerprint or face). 3D Secure is the technical protocol card schemes use to carry out that check between your checkout, the payment provider and the customer's bank.
From the shopper's side it looks like this: they type the card, press pay, and then a screen from their bank appears, or their banking app sends a notification asking them to approve. If they approve, the payment continues. If they do nothing, the payment fails or stays incomplete.
Frictionless versus challenge flow
Not every payment shows the customer a bank screen.
| Flow | What happens | Customer effort |
|---|---|---|
| Frictionless | Bank approves silently using device and transaction data | None |
| Challenge | Bank asks for app approval, code or biometric check | One extra step |
| Exemption | Provider or bank applies an exemption, e.g. a low-value payment | None, but the bank can still refuse |
Your shop does not decide which one happens. The issuing bank does. A customer who paid without any prompt last week can get a challenge today because the basket is larger or they are on a new device. That inconsistency confuses people, and it explains why "it worked before" is a common complaint.
Why authentication fails
The prompt never appears
Older integrations open the bank page in a pop-up window, and browsers or ad blockers can block it. Customers browsing inside the Instagram, Facebook or TikTok app use an in-app browser that sometimes handles redirects and app switching badly. The shopper taps "approve" in their banking app, switches back, and finds the in-app browser has reloaded the product page.
Fix: use your provider's current hosted checkout or its official payment element, which shows the challenge in a modal or a full redirect that survives app switching. Test the full flow from inside a social app on both iPhone and Android.
The customer cannot complete the check
Typical stories: the SMS code goes to a number they no longer use, they have a new phone and have not re-registered the banking app, or the approval request times out while they look for their glasses. None of these are your fault, but you can soften them with clear wording (see below) and by letting them retry or choose another method such as a wallet.
Saved cards and subscriptions charged without the customer
This is the big one for subscription businesses. When a customer saves a card, the first payment or setup should be authenticated and marked for future off-session use. Later renewals are then sent as merchant-initiated transactions, which banks usually accept without a challenge. If the card was saved without this setup, or the bank decides it still wants authentication, the renewal comes back with an "authentication required" decline.
What to do:
- Make sure your integration saves cards through the provider's setup flow intended for future payments, not by storing a raw token.
- For subscriptions, enable the provider's automatic emails or hosted page that asks the customer to authenticate a failed renewal.
- Retry on a schedule, but stop retrying payments that need the customer to act; repeated attempts will not pass.
Wallets and liability
Apple Pay and Google Pay usually include device authentication, so they often pass SCA without an extra bank screen. Offering them is one of the most practical ways to reduce friction at the payment step.
Reading failure reasons in your dashboard
Before changing anything, open ten recent failed payments and note the details. In Stripe, open the payment and look at the timeline and the decline code. Common patterns:
- Authentication required: the bank wanted 3D Secure and the payment was attempted without it, typical for saved cards or old integrations.
- Authentication failed: the customer saw the challenge and failed or cancelled it.
- Incomplete / requires action: the customer was shown the challenge and never finished. Often an in-app browser or an abandoned tab.
- Generic decline after successful authentication: a funds or fraud issue at the bank, not a 3D Secure problem.
Group your ten examples by pattern. If most are "requires action" on mobile from social traffic, focus on the browser flow. If most are renewals with "authentication required", fix the saved-card setup. Your provider's guide to 3D Secure lists the exact statuses.
What to tell customers
A short line near the pay button reduces panic: "Your bank may ask you to confirm this payment in its app or with a code. Keep this page open until it finishes." On the failure screen, avoid blaming language and give two options: try again, or use Apple Pay, Google Pay or another card.
For subscription renewals, the email should say what happened in one sentence, link straight to a page where they can approve the payment, and mention the date when access would pause. Leave out technical terms like SCA.
A quick audit you can run this week
- Place a test order on an iPhone from inside a social app, using a real card with a challenge.
- Repeat on Android in Chrome with an ad blocker enabled.
- Save a card, then trigger a renewal in test mode with a card that requires authentication.
- Review ten live failures and tag each with one of the four patterns above.
- Check your checkout library is on a supported version and that wallets are switched on.
FAQ
Can we turn 3D Secure off to get more payments through?
Not for UK and EEA cards where the bank requires it. Providers apply exemptions where allowed, but the issuing bank has the final say, and skipping authentication when it is needed simply produces more declines.
Why do some customers get a challenge and others do not?
Each bank scores the transaction using device, amount and history. Two customers buying the same product can get different results, and the same customer can get different results on different days.
Are customers outside the UK and EU affected?
Banks elsewhere can also request 3D Secure, but the mandatory SCA rules apply to the UK and EEA. Most authentication friction for UK shops comes from those cards.
Do failed authentications count against our account?
They show up as failed payments, but a high rate usually points to checkout flow issues rather than fraud. Reducing them improves conversion more than anything else.
If your checkout keeps losing customers at the bank step and you want someone to trace the flow end to end, send us the details and we will help find where it breaks.