Tip from SmartRetry Avoid immediately forcing the cardholder back into a 3D Secure challenge, which frequently triggers cart abandonment. Instead, route the authorization forward using the captured attempt cryptogram to secure liability protection, only re-prompting the user if the issuer explicitly responds with a soft decline demanding full step-up authentication.
Mastercard
Mastercard ECI Code 01: Attempted Authentication
soft declinetechnical decline
Last updated: September 25, 2026
About 01 - "Authentication was attempted but not completed (e.g. timeout, user abandon)"
Key details
- 01
- ECI Codes
- 01
- Authentication was attempted but not completed (e.g. timeout, user abandon)
soft declinetechnical decline
What it means
Mastercard ECI Code 01 indicates that a payer-authentication flow was initiated, but the cardholder authentication could not be fully completed. This typically corresponds to a PARes status of 'A', meaning proof of the authentication attempt was generated despite an interruption like a timeout, user abandonment, or the issuer not participating. It is an authentication indicator passed to the subsequent authorization, rather than an authorization decline itself.
Classification & retryability
softtechnicalRetryable: conditional
Do not repeatedly resubmit the same payment authorization. Instead, consider one controlled re-authentication attempt if the root cause appears to be transient, such as a session timeout or customer abandonment during checkout.
Why does code 01 occur?
- The cardholder abandoned the checkout process while the 3D Secure authentication window was open.
- The authentication session timed out before the customer could successfully verify their identity.
- Authentication was unavailable because the specific card or issuer is not currently participating in the program.
How to solve 01?
First, ensure your payment gateway integration correctly captured the attempted authentication data, including the directory-server transaction ID, raw ECI, and Mastercard UCAF authentication data. You must pass this data in your subsequent authorization request to qualify for a merchant-only liability shift and prevent the transaction from being downgraded or refused. If the issue is persistent across customers, verify that your 3D Secure integration is not prematurely timing out.
Solving as a merchant
Pass the complete set of authentication data (including the ECI 01 value and PARes status A) in the subsequent authorization request. Assess your risk tolerance, as this status generally grants a merchant-only liability shift rather than full protection. If the customer is still active in the checkout flow, you may prompt them to try authenticating again or offer an alternative payment method.
Solving as a customer
If you encountered a timeout or closed the verification window by mistake, please try completing the checkout process again. Alternatively, use a different payment method to finalize your purchase.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.