Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa ECI Codes: 07 (Non-Authenticated E-Commerce Transaction)

hard decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
07
Response
07
Detailed Response
Non-authenticated e-commerce transaction
hard decline
This transaction is not retriable

Payments failing with code 07 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 07 indicates that an e-commerce transaction was processed without being authenticated through 3-D Secure (Visa Secure). This value acts as an authentication and liability indicator, typically meaning that fraud liability remains with the merchant. It is used when authentication is not attempted, or when a properly authenticated transaction is technically downgraded due to missing data (such as the CAVV) in the authorization request.

Why does code 07 occur?

  • The merchant does not participate in Visa Secure or chose not to attempt 3-D Secure authentication.
  • An authenticated transaction (ECI 05 or 06) was submitted without the required Cardholder Authentication Verification Value (CAVV), causing a downgrade to ECI 07.
  • The transaction is legitimately utilizing an EEA/UK Strong Customer Authentication (SCA) exemption.
  • The transaction is being processed via the Visa Delegated Authentication Framework.

How to solve 07?

Verify that your payment gateway properly maps and transmits all payer-authentication fields into the authorization message. Missing data, particularly the CAVV, will strip fraud-liability protection and downgrade the transaction to ECI 07. If an issuer rejects the transaction due to missing authentication (SCA code 1A), you must initiate a 3-D Secure challenge and resubmit with the new authentication data.

Solving as a merchant

Monitor your ECI 07 transaction volume to detect gateway configuration errors that might be dropping CAVV data. If you are intentionally bypassing authentication, utilize other fraud controls like CVV2 and AVS, as standard ECI 07 transactions do not carry chargeback protection.

Solving as a client

If a transaction fails because the issuer requires authentication, the customer should be prepared to complete a 3-D Secure challenge (like an SMS OTP or app approval) presented by their bank upon retry.

Tip from SmartRetry Avoid automated background retries for ECI 07 declines, as re-sending unauthenticated payloads will repeatedly fail with security-focused issuers. Instead, immediately route the user into an inline step-up 3DS challenge within the active session to capture valid authentication before resubmitting.

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.