Electronic Commerce Indicator: ECI Liability Shift and Exclusions

An Electronic Commerce Indicator is a two-digit code attached to every card-not-present transaction that tells the issuing bank how thoroughly the cardholder was verified during checkout. The code matters because it decides who pays when a transaction later turns out to be fraud: a fully authenticated code shifts fraud chargeback liability from the merchant to the card issuer, while a non-authenticated code leaves the merchant on the hook.

The value isn’t something a merchant chooses. It’s generated automatically by the 3D Secure authentication protocol based on what happened when the cardholder’s identity was checked, and it travels with the transaction permanently as the key piece of evidence if a dispute arises.

The Three Security Tiers and What Each Network Calls Them

Every ECI value maps to one of three outcomes: fully authenticated, attempted authentication, or no authentication. The confusion is that Visa and Mastercard use different digits for the same tier.

Visa, American Express, and Discover share one numbering scheme. A value of 05 means the cardholder was fully authenticated through a security challenge. A value of 06 means authentication was attempted but did not fully complete. A value of 07 means no authentication was performed.1Cybersource. Payer Authentication Processing – Providing Payer Authentication Information for Authorization American Express runs its program under the SafeKey brand, but the resulting ECI values are identical: 05, 06, or 07.2Cybersource. American Express SafeKey

Mastercard flips the numbering. Full authentication is 02, an attempt is 01, and no authentication is 00.1Cybersource. Payer Authentication Processing – Providing Payer Authentication Information for Authorization The meaning is the same as Visa’s; only the digits change. Payment processors that handle multiple card brands translate between the schemes automatically.

How the Code Gets Assigned

When the checkout page triggers a 3D Secure check, the protocol communicates with the issuer to verify the cardholder, and the outcome of that exchange produces the ECI code that rides with the authorization request. The current standard is EMV 3D Secure 2.x.

3DS 2.x introduced frictionless authentication, in which the issuer analyzes device data, transaction history, and risk signals in the background and approves without any visible challenge. The cardholder never sees a popup or enters a one-time password. A challenge flow, by contrast, asks the cardholder to actively verify.

For ECI purposes, the method doesn’t matter. A successful frictionless authentication and a successful challenge both produce ECI 05 on Visa or ECI 02 on Mastercard. The code reflects the outcome. If the 3DS check fails or the issuer’s system is unavailable, the protocol assigns a non-authenticated code (07 for Visa, 00 for Mastercard). If the merchant attempted authentication but the issuer did not participate, the result is the attempt code (06 or 01).

What the Liability Shift Actually Covers

When a transaction is fully authenticated (ECI 05 for Visa or 02 for Mastercard), fraud chargeback liability shifts from the merchant to the card-issuing bank. If a fraudster uses stolen card data and the transaction passed 3DS, the issuer absorbs the loss. Transactions with the attempt code (ECI 06 or 01) also qualify for liability shift protection in most cases, with more conditions attached.

When a transaction carries a non-authenticated code (ECI 07 for Visa or 00 for Mastercard), no liability shift occurs. The merchant bears full responsibility for fraud chargebacks. Visa’s own rules state explicitly that transactions submitted with ECI 07 do not receive fraud liability protection.3Visa. Visa PSD2 SCA Implementation Guide

When the Shift Does Not Apply

The protection is narrower than many merchants assume. It covers one specific category of chargeback: fraud. Several common scenarios strip it away.

Non-Fraud Disputes

If a customer files a chargeback because the product arrived damaged, wasn’t as described, or never showed up, the liability shift doesn’t apply regardless of the ECI code. These are consumer-related disputes rather than fraud, and the merchant has to defend them through the normal representment process with delivery proof, tracking, or communication records. A fully authenticated code won’t help when the dispute is about what was delivered rather than who authorized the purchase.

Missing or Invalid Cryptographic Data

Even a fully authenticated transaction can lose its liability shift if the CAVV (the cryptographic value that proves authentication actually occurred) isn’t properly included in the authorization request. The ECI code alone isn’t enough. The cryptographic proof has to accompany it, or the network treats the transaction as if authentication never happened. Poorly configured payment integrations frequently fail here.

Exclusions on Attempted Authentication

Transactions with the attempt code (ECI 06 on Visa) face additional disqualifiers. If the authorization message is missing a valid CAVV, the transaction gets reclassified to ECI 07 and loses protection. Non-reloadable prepaid cards authenticated at the attempt level also get reclassified to ECI 07. Merchants enrolled in Visa’s Fraud Monitoring Program or 3D Secure Fraud Monitoring Program lose liability shift protection, and certain merchant category codes are permanently excluded, including wire transfer services, betting and gambling operations, and stored-value card providers.

Recurring and Card-on-File Charges

Subscription businesses face a specific wrinkle. The first transaction in a recurring series goes through full 3DS authentication and earns the liability shift. Every charge after that follows different rules. Visa requires that subsequent recurring authorizations be processed with a recurring indicator rather than the original authentication data, and merchants must not store or resubmit the original CAVV on follow-up charges. The chargeback protection from the initial 3DS authentication does not carry forward.4Visa. Verified by Visa Acquirer and Merchant Implementation Guide The same applies to installments: the initial charge requires authentication, but subsequent installment charges must not contain authentication data. Treating the first 3DS check as cover for the whole subscription leads to unpleasant surprises when a fraud chargeback hits a renewal months later.

Other Financial Upside

Liability shift gets most of the attention, but authenticated transactions carry other benefits. Card networks offer lower interchange rates for properly authenticated e-commerce transactions. Mastercard maintains separate interchange categories called “Full UCAF” and “Merchant UCAF” for authenticated transactions, with rate structures that differ from standard e-commerce rates.5Mastercard. Mastercard 2024-2025 U.S. Region Interchange Programs and Rates Actual savings depend on card type and transaction details, but qualifying through proper authentication can meaningfully reduce processing costs at scale.

Authenticated transactions also tend to see higher approval rates. Issuers treat a 3DS-backed transaction as lower risk and are more willing to approve borderline cases. For merchants losing legitimate revenue to false declines, implementing 3DS 2.x with frictionless authentication can recover sales without adding checkout friction that causes customers to abandon their carts.

This Is Network Rules, Not Federal Law

The ECI-based liability shift is governed entirely by card network rules. The Fair Credit Billing Act gives consumers the right to dispute billing errors and unauthorized charges with their card issuer, and it caps consumer liability for unauthorized use at $50.6FTC. Fair Credit Billing Act The FCBA says nothing about which party between the merchant and the issuer ultimately absorbs the loss. That allocation is set by Visa Core Rules, Mastercard’s chargeback guidelines, and the other networks’ operating regulations. Chargeback liability depends on those private contractual frameworks and the ECI code attached to the transaction, not on the text of federal consumer credit law.