Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard ECI Code 04: Data Share Only

hard decline

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
04
Category
ECI Codes
Response
04
Detailed Response
Data share only, not authenticated, improves approval rate (EMV 3DS only)
hard decline
This transaction is not retriable

Payments failing with code 04 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

Mastercard ECI 04 is an authentication-result indicator for Mastercard Identity Check Data Only (IDCI) transactions within EMV 3DS. It indicates that the merchant submitted device and transaction data to Mastercard for risk scoring without challenging the cardholder to authenticate. This data is passed to the issuer to improve authorization approval rates, though it does not result in an authenticated transaction or provide a liability shift.

Why does code 04 occur?

  • The merchant intentionally initiated a Mastercard Identity Check Data Only flow to reduce checkout friction while passing rich transaction data.
  • The issuer successfully received the EMV 3DS device and transaction data without requiring a cardholder challenge.

How to solve 04?

ECI 04 is a successful data-share authentication response, not a payment decline. The returned authentication data—specifically the ECI 04 indicator, the CAVV, and the Directory Server transaction ID (and paresStatus U)—must be correctly carried into your subsequent authorization request. If the ensuing authorization is declined by the issuer, you must evaluate the separate authorization decline code to determine if a retry or different payment method is appropriate. Repeating the same ECI 04 authentication result is not a remedy for an authorization decline.

Solving as a merchant

Ensure your payment gateway captures the ECI 04, CAVV, and Directory Server transaction ID from the 3DS response and correctly passes them into the authorization message. Do not treat ECI 04 as fraud protection or a chargeback liability shift, and avoid using the Data Only flow in regions where Strong Customer Authentication (SCA) is legally mandated.

Solving as a client

No action is required from the customer. The Data Only flow is entirely frictionless and happens in the background without prompting the cardholder to complete a challenge.

Tip from SmartRetry If downstream authorizations linked to ECI 04 fail, avoid re-submitting the data-only check; instead, configure your 3DS logic to escalate high-risk transactions to a full challenge flow to secure an issuer liability shift.

See the full list of Mastercard's decline codes >Find code on Mastercard'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
Does Numeral Offer Load Balancing for Payment Requests?

Does Numeral Offer Load Balancing for Payment Requests?

Discover why traditional load balancing fails across banking rails and multi-acquirer setups, and how intelligent routing protects your transaction approval rates.

How Raise Cut Chargebacks by 45% and Eliminated Manual Reviews

How Raise Cut Chargebacks by 45% and Eliminated Manual Reviews

Manual fraud reviews create costly fulfillment bottlenecks and high false decline rates. Discover how deploying machine learning models and behavioral biometrics slashes disputes while protecting genuine transaction approval rates.

Managing Chase Stop Payments: Why Recurring Billing Retries Backfire

Managing Chase Stop Payments: Why Recurring Billing Retries Backfire

Blindly retrying stopped payments exposes subscription merchants to Nacha compliance fines and dispute spikes. Discover how to interpret Chase ACH and card revocation codes to protect recovery operations and merchant account health.

Why Good Transactions Go Bad: Unpacking Payment Failures and How to Fix Them

Why Good Transactions Go Bad: Unpacking Payment Failures and How to Fix Them

Payment failures are rarely simple rejections. Discover how leading fintech teams eliminate false declines, optimize network tokens, and deploy intelligent recovery to protect recurring revenue and preserve issuer relationships.

SmartRetry - Payment Recovery Platform

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.