Tip from SmartRetry Avoid re-initiating 3-D Secure authentication when receiving this outcome, as repeated attempts on non-participating BINs will continuously fail to yield full authentication. Instead, let the authorization proceed directly, applying internal fraud thresholds on higher-ticket orders where regional liability protections may be limited.
Visa
Visa ECI Codes 06: Authentication Attempted
technical decline
Last updated: September 25, 2026
About 06 - "Authentication was attempted but not completed (e.g. frictionless or passive)"
Key details
- 06
- ECI Codes
- 06
- Authentication was attempted but not completed (e.g. frictionless or passive)
technical decline
What it means
Visa ECI Code 06 (often displayed as ECI 6) indicates an 'Attempts Processing Performed' outcome during 3-D Secure authentication. It signifies that the merchant attempted to authenticate the cardholder, but the authentication was not fully completed because either the cardholder or the issuer is not participating in Verified by Visa/3-D Secure. Even though full authentication was unavailable, the system generated proof that the merchant made a valid attempt.
Classification & retryability
technicalRetryable: conditional
ECI 06 is an authentication outcome, not an authorization decline. Do not retry a payment solely because you received ECI 06. If the subsequent authorization is declined, base your retry strategy entirely on the specific issuer decline code provided.
Why does code 06 occur?
- The cardholder is not enrolled in the 3-D Secure program.
- The issuing bank or specific card BIN does not participate in Verified by Visa/3-D Secure.
- The Visa Directory Server returned an enrollment response of N during the attempt.
How to solve 06?
Proceed to authorization using the ECI 06 value. If a Cardholder Authentication Verification Value (CAVV) was returned in the authentication response, you must include it in the authorization message to preserve applicable chargeback protection. Ensure your gateway maps this authentication outcome correctly before submitting the authorization request.
Solving as a merchant
Inspect the complete 3-D Secure result and pass ECI 06 (along with any provided CAVV) into your authorization request. Retain all authentication response logs as proof of the attempt. If the subsequent authorization is declined, refer to the actual issuer decline code to determine your next steps or retry logic.
Solving as a customer
No direct action is required from the customer regarding ECI 06. If the subsequent authorization is declined by the issuer, the customer may need to contact their bank or provide an alternative payment method.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.