Tip from SmartRetry Ensure your payment pipeline does not misinterpret this authentication status as an authorization failure or route it into retry queues. Instead, decouple authentication verification from authorization processing to avoid triggering unnecessary dunning alerts while ensuring downstream merchant-initiated requests retain their required tracing data.
Mastercard
ECI 07 (Mastercard): Recurring Payment
Last updated: November 20, 2026
Key details
Code by card network
| Network | Code | Official wording |
|---|---|---|
| Mastercard | 07 | Recurring payment: liability shift for initial, but not subsequent transactions |
| Maestro | 07 | Recurring payment: liability shift for initial, but not subsequent transactions |
| Visa | 07 | Non-authenticated e-commerce transactionDifferent meaning: see Visa 07 |
What it means
Why does code ECI 07 occur?
How to solve ECI 07?
Solving as a merchant
Solving as a client
Frequently asked questions about this topic
Author
Kyle Regacho
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
When Processing Stops: Navigating Gateway Locks and Account Holds
When aggregators freeze processing, standard support tickets fail. Discover how fintech operators diagnose automated underwriting triggers, appeal held funds, and deploy redundant routing to eliminate single points of failure.

Fine-Tuning Stripe for Subscriptions: How to Stop Losing Customers to Failed Payments
Default billing setups quietly surrender recurring revenue to preventable declines. Discover how adjusting stored credential flags, deploying network tokens, and timing retries protect subscriber retention and improve authorization health.

Understanding CAVV: How 3D Secure Tokens Secure Approvals and Shift Liability
Mastering 3D Secure CAVV tokens helps payment teams prevent false declines and secure fraud liability shifts. Learn how cryptographic validation impacts issuer authorization decisions and recurring payment retry performance.

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