ECI codes

[ { "title":"Testing", "link":"https://docs.solidgate.com/payments/testing/", "text":"Simulate payments to test your integration before launching in production.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-customizable.svg" } , { "title":"Create your payment form", "link":"https://docs.solidgate.com/payments/integrate/payment-form/create-your-payment-form/", "text":"Understand how to integrate the payment form into your product.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-payments.svg" } , { "title":"Billing", "link":"https://docs.solidgate.com/billing/", "text":"Smart billing solutions designed for diverse business models.", "imgSrc":"https://solidgate.com/wp-content/uploads/2022/06/icon-global.svg" } ]

Get in touch
Sign in
ECI codes
ECI value represents authentication, affects authorization and liability protection

ECI value indicates the level of authentication performed on the transaction, which is forwarded to the authorization request and determines whether the transaction receives liability protection.

To get three_ds object with eci value use:

Visa, American Express, JCB, Discover/Diners, Cartes Bancaires (VISA), UPI

Value Description
05 Cardholder authentication is successful.
06 Authentication was attempted but was not or could not be completed.
  • For 3DS 1, the ECI 06 value may be used as an authentication response from the issuer ACS, at the issuer’s discretion.
    For example, issuers that use risk-based authentication may provide an ECI = 06 for a transaction that does not require step-up, also known as frictionless authentication. These issuers may reserve an ECI = 05 for transactions that were successfully stepped up.
  • For EMV 3DS, the ECI 06 value can only be used to indicate that authentication was attempted.
07 Non-authenticated e-commerce transaction.

Mastercard, Cartes Bancaires (Mastercard)

Value Description
00 3DS1 and EMV 3DS: 3DS authentication either failed or could not be attempted. Possible reasons include both the card and issuing bank not being secured by 3DS, technical errors, or improper configuration.
01 3DS1 and EMV 3DS: 3DS authentication was attempted but was not or could not be completed. Possible reasons include either the card or its issuing bank having yet to participate in 3DS or the cardholder running out of time to authorize.
02 3DS1 and EMV 3DS: 3DS authentication is successful. Both card and issuing bank are secured by 3DS.
04 EMV 3DS: Data share only, non-authenticated e-commerce transaction, but merchants have chosen to share data via the 3DS flow with the issuer to improve authorization approval rates.
06 EMV 3DS: Acquirer exemption.
07 EMV 3DS: Recurring payments might be applicable for the initial or subsequent transaction. If this value is received on initial recurring payments, the merchant will have a liability shift. Subsequent transactions are considered as MIT and liability remains with the merchant.
Looking for help? Contact us
Stay informed with Changelog