A 3D Secure authentication error means the cardholder verification step did not complete successfully. A wrong or expired code, an unfinished app approval, a timeout or a technical problem may be responsible. Check the message shown at checkout before retrying. Successful authentication does not guarantee that the payment will be authorised.
This guide covers checks for individual cardholders and employees using business cards, with a separate section for merchants investigating checkout errors.
How to Fix a 3D Secure Authentication Error
Start with the symptom you can see. If the checkout has stopped responding after you approved a payment, check the order status with the merchant before starting another attempt.
| What You See | What to Check First | Who Can Help |
|---|---|---|
| Checkout asks for approval, but no code or app request arrives | Check the selected confirmation method and the contact details registered with your issuer. Open its app if app approval is expected. | Your card issuer |
| A verification code is rejected or has expired | Use the latest code for this purchase and follow the expiry instructions shown. Stop repeated attempts if it is still rejected. | Your card issuer |
| The verification window is blank or the browser is unsupported | Check your connection and use an updated browser supported by the checkout. Keep the original error message. | The merchant or card issuer |
| The app says approved, but checkout is unfinished | Return to the original checkout and follow any remaining instructions. Check whether the order completed before paying again. | The merchant, then its payment provider |
| Verification succeeds, but the payment is declined | Check the decline message, available funds and applicable card limits. Authentication and payment authorisation are separate. | Your card issuer or the merchant |
| The message says “3DS lookup failed” or “3D not authenticated” | Record the exact message and the stage where it appeared. The wording alone does not identify one cause. | The merchant and its payment provider |
What Does 3D Secure Authentication Failed Mean?
3D Secure, or 3DS, is a process used to authenticate the cardholder during an online card payment. The card issuer assesses information about the transaction and may ask you to confirm the purchase. That request can involve a one-time code or approval in the issuer’s app, depending on the method it supports.
Some transactions complete authentication without an extra question or approval screen. This is called a frictionless flow. A missing prompt on its own does not prove that authentication failed. The troubleshooting steps above apply when checkout reports an error or requests an action that you cannot complete.
The verification step helps the issuer assess whether the person making the purchase is authorised to use the card. It does not eliminate fraud or guarantee that a payment will succeed. For background on the process, see our guide to 3D Secure authentication.
Why 3D Secure Authentication Fails and What to Do
The Verification Code Does Not Arrive
First check what the checkout is asking you to do. If it expects approval in an app, waiting for a text message will not complete the check. Open the issuer’s official app and look for the purchase request.
If an SMS code is expected, check that your issuer has your current mobile number and that your phone can receive messages. A changed number or an outdated contact record needs attention through the issuer’s official account settings or support team. Follow its resend instructions; repeatedly requesting codes makes it harder to identify the current request.
Confirm that the request is for your purchase before approving it. Never share a one-time verification code with someone who calls or messages you, even if they say they are helping resolve the failed payment.
The Code Is Incorrect or Has Expired
Use the latest code issued for the purchase you are completing. If you requested a replacement, check that you are not entering the earlier message. Follow the expiry time and retry instructions shown by the issuer; there is no single time limit or retry allowance that applies to every card.
When a fresh code is still rejected, record the error and contact your issuer. Repeatedly entering codes will not fix an outdated contact record or a problem with the authentication service. Your issuer can explain whether another attempt is appropriate.
App Approval Does Not Complete Checkout
An approval in your card issuer’s app can leave the original browser checkout waiting for the result. Return to that checkout and follow any remaining instructions. Avoid closing the checkout tab while you switch to the app.
EMVCo identifies the switch between a browser and an authentication app as a point where the payment journey can fail, including when the browser does not receive the completion signal before a timeout. If the order remains unconfirmed, ask the merchant to check its status before trying again. Keep any order reference and note whether the app showed a successful approval.
The Verification Page Will Not Load
A blank screen, a stalled challenge or a browser compatibility error can prevent you from completing the requested step. Check your connection, then follow the checkout’s browser requirements. If necessary, use an updated supported browser after confirming that the earlier order did not complete.
A blocked verification window may also interrupt the process. Check the browser’s message for the specific site and follow the issuer’s guidance. You do not need to disable security software across your device or install an unfamiliar extension to approve a purchase.
If the same failure continues, send the exact error to the merchant. Include whether the problem happened before a verification screen appeared or after you approved the purchase. Those details help it distinguish a page-loading problem from an incomplete authentication result.
The Error Says “3DS Lookup Failed” or “3D Not Authenticated”
These messages need to be interpreted in the context of the merchant’s payment provider. They do not, by themselves, prove that your card is blocked or that you entered a wrong code. A lookup error can occur before you receive an authentication challenge.
Give the merchant the exact wording and the approximate time of the attempt. Its payment provider can check the recorded result and identify the failed stage. Your card issuer can help with card support, account details and the verification methods available to you.
Authentication Succeeds but the Payment Is Declined
Authentication checks the cardholder; authorisation determines whether the payment is approved. A successful code or app confirmation can therefore be followed by a decline. Completing another verification attempt does not guarantee a different authorisation decision.
Check the issuer’s payment message, your available funds and the limits or restrictions that apply to the card. An employee using a company card may need the card administrator to check an applicable spending limit. If the reason remains unclear, contact the issuer through its official support channel or ask the merchant for its payment reference.
A pending transaction and a confirmed order are also different records. If the card account shows a pending amount but the merchant has not confirmed the order, ask the merchant to check the payment before you submit another purchase. The issuer can explain the status of the pending entry.
How to Check Your Card’s 3D Secure Setup
Your card issuer determines which authentication methods are available and how to set them up. There is no universal activation menu for every bank or business card. Visa says its service works at participating online merchants without downloading software or registering an account, and that you may be asked to verify your identity if and when needed.
Check your issuer’s instructions for keeping contact details current, using its app and confirming online purchases. If the card or verification method is unavailable, ask the issuer for the next step. Your usual cash-machine or shop-terminal PIN is not a one-time 3DS verification code.
Checking a Wallester Business Card
For a Wallester Business card, open the Wallester mobile app, go to the card’s 3DS Settings and check which confirmation method is selected. Business and Payroll cardholders find the card under My cards; expense card users open Card Settings.
Selecting In-App confirmation replaces SMS and email confirmation for that card. Only one confirmation method can be active at a time, and In-App confirmation works for one user per card; another user can take it over by disabling and re-enabling the method. This matters when an employee is waiting for a text message but the card is configured for app approval.
If an iOS push notification does not arrive, open the Wallester app while logged in. On Android, check the app and device notification settings. Follow the Wallester in-app confirmation guide for the current steps, and check the order status before restarting an interrupted purchase.
Contact Wallester support if the expected confirmation request is still unavailable. Wallester Business brings a business account, company cards and expense management into one platform; the cardholder’s authentication settings still need to be checked for the specific card and user.
Checks for Merchants Investigating Failed Payments
If several customers report authentication errors at the same checkout, ask your payment provider to investigate the transaction records. A customer cannot repair a checkout integration by requesting another verification code.
- Identify the payment attempts using your provider’s transaction references, timestamps and the exact error or status recorded.
- Check which stage failed: starting authentication, completing a challenge, returning to checkout or requesting payment authorisation.
- For app approval problems, review the return to the browser, the completion signal and any timeout with your provider.
- Compare the affected browser or app versions and check the provider’s service status and supported integration guidance.
Use your provider’s documentation to interpret its result codes. A generic message shown to the customer is not enough to diagnose the underlying technical fault. Keep full card details and verification codes out of ordinary support emails.
When to Contact Your Issuer or the Merchant
Contact your issuer when the code does not arrive, registered contact details are wrong or a card-specific approval method is unavailable. Contact the merchant when checkout is stuck, the order status is unclear or the error needs to be traced through its payment provider. If authentication succeeded and authorisation failed, the issuer or merchant may need to check the decline record.
Have the merchant name, approximate time, displayed error and order reference ready. Explain whether you received a challenge and whether you completed it. Share a redacted screenshot if support requests one through its official channel; never include a verification code, full card number or security code.
For teams using Wallester Business, checking the selected confirmation method and the person linked to the card gives support a clear starting point. Resolve that specific issue before restarting an interrupted payment.
Frequently Asked Questions
It means the cardholder verification step did not complete successfully. The cause may involve a code, an app approval, a timeout or a technical problem. Check the exact checkout message to decide whether to contact your card issuer or the merchant.
Match the error to the step that failed: receiving a code, entering it, approving in an app or returning to checkout. Use the current request and follow your issuer's instructions. If the problem continues, contact the issuer or merchant with the exact error, and check the order status before paying again.
A missing code can result from outdated contact details or a different confirmation method being selected. Check whether checkout expects app approval and whether your issuer has your current mobile number. For a Wallester card with In-App confirmation selected, SMS and email confirmation are disabled while that method is active.
The message means the checkout could not complete the step it labels as a 3DS lookup. Its precise cause depends on the payment provider's result and integration. Ask the merchant to check the recorded error; the wording alone does not prove that your card is blocked or a verification code was incorrect.
It indicates that the checkout has not recorded successful 3DS authentication for the attempt. The exact reason needs to be checked against the payment provider's result. Record the message and tell the merchant whether a verification challenge appeared and whether you completed it.
Use an updated browser supported by the merchant's checkout and follow any issuer-specific guidance. Check whether a verification window was blocked for that site. If the error persists, contact the merchant with the browser details and error message; do not install an unfamiliar extension or disable device-wide security to proceed.
Yes, payment authorisation is separate from 3DS authentication. The issuer can decline a payment after you have completed verification. Check the payment message, available funds and applicable card limits, then contact the issuer or merchant if the reason is unclear.
Virtual cards can support 3D Secure, depending on the issuer and card settings. The issuer determines the verification method, which may include app approval or a code. A virtual card is not necessarily a disposable card, so check the authentication instructions for the specific card you use.
