Skip to main content
SmartRetry - Payment Recovery Platform

Mastercard

Mastercard ECI Code 02: Authentication Successful

Last updated: October 8, 2026

Key details

Brand
Mastercard
Code
02
Response
02
Detailed Response
Authentication successful (liability shift applies)

What it means

Mastercard ECI 02 is a 3D Secure Electronic Commerce Indicator, not a payment decline. It signifies that the cardholder was fully and successfully authenticated, granting liability shift from the merchant to the issuer for eligible fraud-related disputes.

Why does code 02 occur?

  • The cardholder successfully completed a 3D Secure authentication challenge, such as entering a one-time password or using biometrics.
  • The transaction qualified for a frictionless authentication flow, allowing the issuer to verify the user passively.
  • The 3D Secure authentication resulted in a successful authentication status (ThreeDResult Y) and returned a valid CAVV.

How to solve 02?

No resolution is needed as this is a successful authentication indicator. Proceed directly to card authorization using the generated authentication data.

Solving as a merchant

Proceed with the authorization request. No troubleshooting or retry of the authentication is required.

Solving as a client

No action is required from the customer as the authentication was successful.

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
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.