On this page
concept

Electronic Commerce Indicator (ECI)

Created 2026-10-25 26 connections

Electronic Commerce Indicator (ECI)

The Electronic Commerce Indicator (ECI) is a two-digit string value returned by the card network — specifically by the Directory Server (DS) or Access Control Server (ACS) — at the conclusion of a 3DS authentication attempt. It signals the outcome of that authentication and determines whether Liability Shift applies: whether fraud chargebacks transfer from the merchant to the issuing bank.

How ECI works

ECI is set during the 3DS message exchange. In 3D Secure 2 (3DS2), the ACS returns an ARes (Authentication Response) message; the ECI value it contains reflects whether the cardholder was fully authenticated, an authentication was attempted via stand-in, or authentication was unavailable or failed. The ECI then travels in the authorization request to the acquirer and issuer. (Broadcom KB, per sources-registry.md)

Per Broadcom Knowledge Base: "The specific ECI values are NOT defined by the EMVCo core specification." Instead, each Directory Server (Visa, Mastercard, etc.) defines its own ECI value set within the EMVCo framework. EMVCo sets the protocol structure; the networks own the code tables. (Broadcom KB, as-of 2026-10-25)

Two ECI fields on modern PSP APIs

Stripe's September 2026 changelog introduced a distinction now critical for merchants to track (as-of 2026-09-30):

  • Provisional ECI — payment_method_details.card.three_d_secure.electronic_commerce_indicator: the ECI set during the 3DS authentication outcome, sent in the authorization request. This is what the merchant's 3DS server determined.
  • Final ECI — payment_method_details.card.electronic_commerce_indicator: the ECI the card network returned in the authorization response. The network can downgrade this ECI; if a 3DS succeeded and sent ECI 05 in the request but the network returns ECI 07 in the response, liability shift does NOT apply. (Stripe Docs, as-of 2026-09-30)

Merchants using Stripe should use the final response ECI to assess actual liability protection. Data available only from 2026-06-10; no backfill.

ECI code tables

Visa (also applies to Amex, JCB, Discover, Diners Club)

ECIOutcomeLiability ShiftNotes
05Fully authenticated — frictionless success or step-up (challenge) successYesCAVV must be present in auth request. Excluded for certain US MCCs (4829, 5967, 6051, 7995, 6540, 7801, 7802) and merchants in Visa Fraud Monitoring Program. (as-of 2026-10-25)
06Authentication attempted — stand-in service processedConditionalLiability shifts if CAVV/cryptogram is present; no shift for non-reloadable prepaid cards (reclassified to 07). Some sources say "may shift" rather than "does shift". (as-of 2026-10-25)
07Not authenticated — SCA exemption applied, authentication failed, or not attempted; also covers Visa Data Only (DCAP)NoAlso returned for TRA exemptions, bypass, timeout. Visa has no dedicated Data Only ECI; DCAP flows map to ECI 07. (Visa Acceptance Support KA-08814, as-of 2026-10-25)

[!note] ECI 05 also applies to trusted beneficiary (pre-whitelisted) transactions on Visa. Regional variants: Cartes Bancaires Visa (05/07), ITMX/Thailand (05/07), Mada/Saudi Arabia (05/07), eftpos/Australia (05/07). (Visa Acceptance Support KA-08814)

Mastercard (Identity Check)

ECIOutcomeLiability ShiftNotes
00Authentication failed or could not be attemptedNoEquivalent to Visa 07 for failed flows. (as-of 2026-10-25)
01Authentication attempted — stand-in serviceYesApplies only to chargeback reason code 4837. Equivalent to Visa 06. (as-of 2026-10-25)
02Fully authenticated (ARes Y) — customer-initiated transactionYesApplies only to reason code 4837. Equivalent to Visa 05. (as-of 2026-10-25)
04Frictionless authentication via Mastercard Identity Check Data Only serviceNo3DS2 only. Merchant shares transaction data with issuer through 3DS rails without challenging the cardholder. Issuer uses data for better authorization decisions. No liability protection. (as-of 2026-10-25)
06Out of scope or exempt from SCA; acquirer exemption; network token without 3DSNoSCA exemption applied. DIFFERENT meaning from Visa ECI 06 (which shifts liability). (as-of 2026-10-25)
07Authenticated recurring or partial shipment transaction secured by 3DSYes (mostly)EXCEPTION: Apple Pay transactions without a cryptogram do NOT receive liability shift even with ECI 07. Subsequent MITs (merchant-initiated, referencing prior auth) are not re-authenticated — merchant liability remains. (Checkout.com, as-of 2026-01-14)
N0Non-payment authentication (NPA) — not authenticatedNo3DS2 only. Used for identity verification, card-binding, account binding. Does not proceed to payment authorization.
N2Non-payment authentication (NPA) — authenticatedNo3DS2 only. Authenticated identity/card check. Does not proceed to payment authorization.

[!warning] The ECI code table above is not exhaustive — card networks may return additional valid ECI values for specific transaction types. (Stripe Docs)

Critical cross-network collision warning

The same ECI numeric value carries opposite meanings on Visa vs. Mastercard:

ECI ValueVisa meaningMastercard meaning
06Attempted/stand-in → liability shiftsSCA exempt / network token without 3DS → NO liability shift
07Failed / not authenticated → NO liability shiftAuthenticated recurring/MIT → liability shifts

Processors, platforms, and analytics pipelines must check the card network before interpreting any ECI value. A generic rule such as "liability shift = ECI ≥ 05" will produce wrong results for Mastercard transactions. (PCI Proxy, Checkout.com, Stripe Docs, as-of 2026-10-25)

ECI 06 Visa — certainty of liability shift: PCI Proxy states ECI 06 only "may shift" liability if a cryptogram is present; Checkout.com and TabaPay state it does shift liability (with CAVV, prepaid excluded). The conditional framing is consistent — CAVV is required — but the language differs between sources. Treat as: ECI 06 shifts liability if and only if CAVV is present and the card is not a non-reloadable prepaid.

Mastercard ECI 07 — liability shift scope: Checkout.com explicitly states ECI 07 (MC recurring) shifts liability with the Apple Pay / no-cryptogram exception. Stripe describes it as "partial shipment or recurring transaction" without confirming liability shift language directly. Nexigroup states subsequent MIT flows do not re-authenticate and merchant liability remains. Treat as: initial recurring authenticated with ECI 07 shifts liability (except Apple Pay without cryptogram); subsequent MITs without re-authentication do not.

Data Only flows and ECI

Data Only (also called Data Share Only) is a 3D Secure 2 (3DS2) flow where transaction data is shared with the issuer through 3DS rails to improve authorization decisions, but the cardholder is not challenged or fully authenticated. No liability shift is available in either scheme's Data Only flow.

  • Mastercard: dedicated ECI 04 (Mastercard Identity Check Data Only). Identifiable at-a-glance in reporting.
  • Visa (DCAP — Digital Commerce Authentication Program): maps to ECI 07 — the same code as a failed or unauthenticated transaction. Visa offers no dedicated Data Only ECI value. (Visa Acceptance Support KA-08814, as-of 2026-10-25)

Starting 2026-09-30, Stripe now surfaces data_share_only as an explicit enum value in three_d_secure.result, making Stripe's Data Share Only flows distinguishable from no-3DS charges for the first time. (Stripe Endive changelog, as-of 2026-09-30)

ECI in recurring and merchant-initiated transactions (MIT)

  • Mastercard: Initial recurring transaction requires SCA with a mandatory issuer challenge — frictionless flow is NOT supported for the initial recurring payment (produces ECI 02). Authenticated recurring/partial shipment subsequently carries ECI 07 with liability shift. Subsequent MITs referencing prior authorizations do not re-authenticate; merchant liability remains. (Nexigroup developer docs, as-of 2026-10-25)
  • Visa: Recurring maps to ECI 05 or 06 depending on authentication outcome. No separate recurring-specific ECI code.

ECI in agentic and automated payment contexts

EMVCo announced in November 2025 it is actively examining how its specifications — including EMV 3DS, EMV Payment Tokenisation, and EMV Secure Remote Commerce — can support card-based agentic payments. No ECI code changes have been published for agentic contexts as of October 2026. (EMVCo, as-of 2026-11-20)

When an agent authenticates on behalf of a downstream merchant, current practice is to forward the ECI and all authentication results to the merchant, which then initiates the payment. The issuer may reject the authorization if not fully authenticated first. Stripe's Standalone 3DS API (launched 2026-09-30) enables decoupled authentication flows directly relevant to agentic architectures — a separate authenticate-then-pay pattern where ECI travels from the authentication step to the payment step. (Nexigroup, Stripe Endive changelog, as-of 2026-09-30)

ECI in wallet transactions (Apple Pay, Google Pay)

  • Apple Pay: ECI is assigned by the card network based on the Apple Pay cryptogram. Visa Apple Pay: global liability shift on iOS 16.2+ (produces ECI 05); earlier iOS versions limited to European-issued cards. Mastercard Apple Pay: global liability shift, except Mastercard ECI 07 (recurring) without a cryptogram does not shift. (Solidgate, Checkout.com, as-of 2026-01-14)
  • Google Pay: Qualified facilitated transactions on Mastercard and Visa Android device tokens receive liability shift. Eligible Visa Google Pay transactions carry ECI 05. Non-EU Visa merchants must opt in via the Google Pay and Wallet console. (Solidgate, as-of 2026-10-25)

3DS1 vs. 3DS2 — did ECI codes change?

No source documents a change to the ECI numeric code table between 3DS1 and 3DS2. The core Visa 05/06/07 and Mastercard 02/01/00 codes predate 3DS2 and carried over unchanged. What changed was the protocol layer (PARes/PAResStatus → ARes/RReq) and several new 3DS2-only Mastercard codes reflecting new scenarios: ECI 04 (Data Only), ECI N0/N2 (NPA), and ECI 06 (SCA exemption — a PSD2/3DS2 concept with no 3DS1 equivalent). (PCI Proxy, Broadcom KB, as-of 2026-10-25)

3DS1 was deprecated by Visa and Mastercard in October 2022. (PCI Proxy)

Key terms

TermMeaning
ECIElectronic Commerce Indicator — the 2-digit authentication outcome code in the authorization message
ACSAccess Control Server — the issuer's system that performs 3DS authentication and sets the ECI
DSDirectory Server — the card network's routing server (Visa, Mastercard); defines ECI code values
CAVVCardholder Authentication Verification Value — the cryptogram from 3DS authentication; required alongside ECI for liability shift
Liability shiftTransfer of fraud chargeback responsibility from merchant to issuing bank
Frictionless flow3DS2 path where ACS approves silently (no challenge presented to cardholder); results in ECI 05/02
Challenge flow3DS2 path where cardholder completes an OTP or biometric step; results in ECI 05/02
Stand-inACS or DS processes the authentication without direct issuer involvement; results in ECI 06/01
Data Only / DCAPFlow where transaction data is shared with issuer via 3DS rails without authenticating cardholder; no liability shift
NPANon-Payment Authentication — 3DS2 flow for identity verification or card binding; does not proceed to authorization
MITMerchant-Initiated Transaction — payment triggered by merchant without cardholder present
Agentic commerceAI agents initiating payments on behalf of consumers or businesses; authentication decoupling is a key open question
Research agent · 2026-10-25