# ECI values

When you authenticate with 3D Secure (3DS), you receive Electronic Commerce Indicator (ECI) values that indicate the authentication level and liability shift.

> **Note**
>
> See [Apple Pay](https://www.checkout.com/docs/payments/add-payment-methods/apple-pay.md#Liability_shift) and [Google Pay](https://www.checkout.com/docs/payments/add-payment-methods/google-pay.md#Liability_shift) for more information on how liability shift applies to each digital wallet.

---

## Mastercard liability shift

The following ECI values and liability shift rules only apply to Mastercard.

| ECI value | Transaction type | 3DS version | Liability shift |
| --- | --- | --- | --- |
| 00 | 3DS authentication either failed or could not be attempted. | 3DS 2.2.0 and 2.3.1 | No |
| 01 | 3DS authentication was processed by a stand-in service, and is classed as successful. | 3DS 2.2.0 and 2.3.1 | Yes |
| 02 | 3DS authentication was successful. The transaction is secured by 3DS. | 3DS 2.2.0 and 2.3.1 | Yes |
| 04 | Frictionless authentication via the Mastercard Identity Check Data Only service. | 3DS 2.2.0 and 2.3.1 | No |
| 06 | Transaction is out of scope or exempt from [Strong Customer Authentication (SCA)](https://www.checkout.com/docs/business-operations/ensure-regulatory-compliance/sca-compliance.md). | 3DS 2.2.0 and 2.3.1 | No |
| 07 | 3DS authentication was successful. The recurring transaction is secured by 3DS. | 3DS 2.2.0 and 2.3.1 | Yes<br><br>Liability shift does not apply to transactions processed through Apple Pay without a cryptogram. |
| N0/N2 | A non-payment authentication was processed.<br><br>This type of transaction does not go to authorization so liability shift does not apply. | 3DS 2.2.0 and 2.3.1 | No |

##  Non-Mastercard liability shift

The following ECI values and liability shift rules apply to:

- American Express
- Diners Club International (DCI)
- Discover
- JCB
- Visa

| ECI value | Transaction type | 3DS version | Liability shift |
| --- | --- | --- | --- |
| 05 | 3DS authentication was successful. The transaction is secured by 3DS. | 3DS 2.2.0 and 2.3.1 | Yes |
| 06 | 3DS authentication was processed by a stand-in service, and is classed as successful. | 3DS 2.2 and 2.3 | Yes |
| 07 | 3DS authentication was processed successfully using an SCA exemption, failed, or could not be attempted. | 3DS 2.2.0 and 2.3.1 | No |