Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa ECI Codes 06: Authentication Attempted

hard decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
06
Response
06
Detailed Response
Authentication was attempted but not completed (e.g. frictionless or passive)
hard decline
This transaction is not retriable

Payments failing with code 06 are hard declines and typically cannot be recovered by retrying. SmartRetry still helps you avoid future hard declines with smarter routing and validation.

But many other declines in your payment flow may still be recoverable. SmartRetry identifies which failed transactions have recovery potential and applies the right strategy to recover them.

Find out what you can recover >

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.

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 client

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.

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.

See the full list of Visa's decline codes >Find code on Visa's website >

Frequently asked questions about this topic

Share this article

Share on XShare on FacebookShare on LinkedIn
Kyle Regacho

Author

Kyle Regacho
LinkedInFind me on Linkedin

Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue

Read all articles >

Articles you may find interesting:

View all
How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

Discover how automated risk reviews trigger gateway freezes and how payment teams can insulate revenue through multi-acquirer setups and smart retry logic.

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Payment rejections cost merchants billions in lost sales and unforced churn. Discover the root causes behind issuer declines and how intelligent recovery strategies salvage legitimate revenue.

Why Payment Tests Pass in Staging and Fail in Production

Why Payment Tests Pass in Staging and Fail in Production

Passing a sandbox check rarely guarantees live authorization success. Learn how real-world issuer ambiguity, webhook delays, and network retry rules impact revenue pipelines.

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Sandboxes verify API formatting, but live issuers determine transaction success. Discover how multi-layered testing, safe retry logic, and real-time observability safeguard authorization rates and reduce involuntary customer churn.

Decline codes tell you why. We fix it.

SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.