Review date: October 26, 2026. 3D Secure (3DS) is an identity-verification step used for online card payments. Messages such as “3DS authentication failed” usually mean that the verification was not completed. Common causes include an incorrect or expired code, a missing bank-app prompt, a timed-out challenge page or an issuer authentication error.
A failed 3DS challenge does not prove that the card lacks funds or has been frozen. Identity verification and final transaction authorization are separate steps: a payment can still be declined after verification succeeds.
Common symptoms
- The SMS code does not arrive or has expired.
- The challenge page is blank, keeps loading or closes unexpectedly.
- The bank app does not show an approval prompt.
- Authentication succeeds but the card is still declined.
- The bank shows a pending amount while the order or subscription is not completed.
Where can the failure occur?
The merchant starts the payment, the issuer decides whether a challenge is needed, the cardholder completes it and the issuer returns an approval or decline. A successful challenge is not the same as a completed charge. Limits, risk controls, merchant category and cross-border settings can still cause a decline.
If the SMS code does not arrive
- Confirm that the issuer has the correct phone number and check SMS blocking, roaming and dual-SIM settings.
- Wait for the previous code to expire before requesting another.
- Check whether the bank app offers push approval or another verification method.
- Ask the issuer whether international SMS, online foreign payments and 3DS are enabled.
Verification codes are sensitive. Enter them only on the legitimate bank or merchant verification page; never send them to support agents, payment intermediaries or strangers.
If the challenge page is blank
- Allow necessary cookies and pop-ups for the official checkout page.
- Restart from the merchant’s current checkout rather than refreshing an expired challenge.
- Use a supported browser and stable network without frequently changing device, region or connection.
- Check the system clock and update the browser and bank app.
If the domain, certificate or page design looks suspicious, exit and restart from the merchant’s official website.
If the payment is declined after verification
Check the balance or credit limit, card number, expiry, CVV and billing address. Ask the issuer whether the transaction was seen, whether a 3DS record exists and why the final authorization was declined. For virtual cards, also check per-transaction limits, daily limits and supported currencies.
If the bank shows Pending
A pending amount may be an authorization hold from a failed transaction rather than a completed charge. Check the merchant order and bank status before retrying. Avoid creating repeated orders while the hold is unresolved. If multiple holds remain, provide the order numbers and transaction records to both the merchant and issuer.
Recommended troubleshooting order
- Stop repeated retries and record the error and time.
- Check whether an order was created and whether the bank shows pending.
- Confirm the phone number, bank-app approval, online foreign payments and 3DS status.
- Use accurate billing details and try once from the official checkout.
- Ask the issuer for a specific decline reason if it still fails.
- Only then consider another payment card in your own name.
Avoid increasing risk controls
Do not submit the same order repeatedly within minutes, frequently change proxy or region, use mismatched names and addresses, share verification codes, or create new orders simply because a transaction is pending.
Content type: Rules summary; no live transaction test. Content review: ChecksPilot Editorial Department. English adaptation reviewed on October 29, 2026. Results vary by issuer, merchant, region and card.
