Results for

icon-search-large No search results yet
Enter your search query above

3D Secure is an abbreviation for Three Domain Secure, which is the payment industry’s Internet Authentication Standard. All major credit card brands support this standard under their own label:

  • Visa -  Verified by Visa
  • MasterCard -  MasterCard SecureCode
  • Diners -  ProtectBuy
  • Amex -  SafeKey

Consumer Enrollment

A one-time process the cardholder undergoes to participate in the 3D Secure scheme. Pending the type of method supported by the issuer, the cardholder will either use static or dynamic (via token or mobile/smartphone) authentication credentials.

Authentication

During online shopping a prompt from the card issuer appears and requests the cardholder to enter the authentication credentials . The card issuer checks the credentials and the identity of the cardholder, and provides unique authentication values  to the merchant.

Liability Shift

 If  both the cardholder and the merchant are participating in the 3D Secure scheme and the transaction has been successfully authenticated, the liability of a chargeback shifts from the merchant to the cardholder’s issuing bank. This only applies for chargebacks based on a fraud reason code.

Key benefits

  • Enhance trust and confidence for your consumer’s online shopping experience 
  • Additional layer of protection against fraud 
  • Especially valuable for high transaction amounts
  • In case of a fraud chargeback reason code, the liability shifts to the card issuing bank if the obtained authentication values were used during the authorization and settlement. 

Supported Card Types

Verified by Visa Securecode ProtectBuy Amex
Visa Credit MasterCard Credit Diners Credit Amex Credit
Visa Debit MasterCard Debit Diners Credit Amex Credit
Visa Electron Maestro Diners Commercial Amex Commercial
Visa Commercial MasterCard Commercial Diners Commercial Amex Commercial

Support in Latin America

In Latin America 3D Secure is supported in the following countries: 

Country Product
Argentina - Visa Argentina Visa (Verified by Visa)
Brazil - Elavon Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Brazil - Cielo* Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Mexico - Banorte" Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Peru - VisaNet* Visa (Verified by Visa)
* Acquirer approval is required for using the service. 

Process Flows

payment_flow_chart_3dsecure

Electronic Commerce Indicator

The authentication values provided by the issuer, the Electronic Commerce Indicator (ECI) and Cardholder Authentication Verification Value (CAVV) are exchanged in the authorization and settlement messages, and as such, enabled authenticated transactions can be distinguished from non-authenticated or partially authenticated transactions.

If certain conditions are met, and pending the level of the ECI and the presence of the CAVV, liability shift may also apply if the transaction was partially authenticated, for example when the merchant is participating but the cardholder is not.

Reporting

The Webcollect Payment Console (WPC) displays the Authentication result.

3dsecure_report

Additional Information

Chargeback Reason Codes

Visa

Reason codeChargeback conditions
75 The cardholder states that he does not recognize the transaction.
83 The transaction was processed without the permission of the cardholder, or a fictitious card account number was used and the transaction was not authorized.

MasterCard

Reason codeChargeback conditions
37 The cardholder states that he did not participate in the transaction, or that he did not perform the transaction.
63 The cardholder states that he does not recognize the transaction. Or the cardholder insists that he did not authorize the transaction.

Maestro

Reason codeChargeback conditions
22 The cardholder states that he did not initiate the transaction himself.

Diners

Reason codeChargeback conditions
C42 Card member did not authorize or participate in a card not present transaction - OR - any fraudulent charge where the Card is not present and the authorization data indicated that the Card was present.

Liability Shift Protection

Depending on where the card is issued, and the level of authentication, liability shift may or may not apply.

Liability Shift: Visa 

Region & card typeAuthenticationCAVVECIVisaDescription /ScenarioLiability Shift
All regions—consumer card No 6 Issuer, card range, or cardholder not enrolled Yes
  Full Yes 5 Authentication successful  Yes
  Full No 5 Authentication successful but no CAVV provided by the issuer Yes,
No, for US intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
Yes
  Attempt No 6 Authentication attempt but no CAVV provided by issuer Yes,
No, for US intra-region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
Yes, for Europe intra- region transactions
  Failed No   Authentication failed (status 180) No
All regions—commercial card No 6 Issuer, card range, or cardholder not enrolled. No
Yes, for Europe intra- region transactions
  Full Yes 5 Authentication successful  Yes
  Full No 5 Authentication successful but no CAVV provided by the issuer No
Yes, for Europe intra- region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
No
Yes, for Europe intra- region transactions
  Attempt No 6 Authentication attempt but no CAVV provided by issuer No
Yes, for Europe intra- region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
  Unable Yes 7 Standard response for  inter-regional authentication requests No
  Failed No 7 Authentication failed (status 180) No

Liability Shift: MasterCard/Maestro

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—consumer cards 1 Issuer, card range, or cardholder not enrolled. Yes
  Full Yes 2 Authentication successful Yes
  Full No 2 Authentication successful but no AAV provided by issuer Yes
No, for US intra-region transactions
  Attempt Yes 1 Cardholder not enrolled
AAV is provided in the authorization
Yes
  Attempt No 1 Authentication attempt but no AAV provided by issuer Yes
  Unable No Issuer is unable to authenticate Yes
No, for US intra-region transactions
  Failed No Authentication failed(status 180) No
All regions - Commercial Card 1 Issuer, card range, or cardholder not enrolled Yes
No, for intra US and Canada intra-region transactions
  Full Yes 2 Authentication successful Yes
  Full No 2 Authentication successful but no AAV provided by issuer Yes
No, for intra US and Canada intra-region transactions
  Attempt Yes 1 Cardholder not enrolled
AAV is provided in the authorization
Yes
No, for intra US and Canada intra-region transactions
  Attempt No 1 Authentication attempt but no AAV provided by issuer Yes
No, for intra US and Canada intra-region transactions
  Unable No Issuer is unable to authenticate No
  Failed No Authentication failed (status 180) No

Liability shift: Diners

  • The Issuer, Merchant/Acquirer, and Card Member are enrolled in ProtectBuy and the authentication response is either Full Authentication or Attempts Authentication.
  • Only the Issuer and Merchant/Acquirer are enrolled in ProtectBuy and the Card member is not participating. This includes when a Card Member opts-out of Activation During Shopping (ADS) or ADS is not offered. Liability shift occurs when the authentication response is Attempts Authentication.
  • The Issuer and Merchant/Acquirer are both participating but the Issuer’s Access Control Server (ACS) is unreachable, requiring the DCI Attempts ACS to perform stand-in authentication, and the authentication response is Attempts Authentication. This may occur whether or not the Card Member is enrolled.

Liability Shift: Amex

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—consumer cards No 6 Issuer, card range, or cardholder not enrolled. Yes
  Full Yes 5 Authentication successful Yes
  Full No 5 Authentication successful but no CAVV provided by issuer Yes
No, for US intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
Yes
  Attempt No 6 Authentication attempt but no CAVV provided by issuer Yes
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
Yes, for US intra-region transactions
  Failed No Authentication failed(status 180) No
All regions - Commercial Card No 6 Issuer, card range, or cardholder not enrolled No
Yes, for intra US and Canada intra-region transactions
  Full Yes 5 Authentication successful Yes
  Full No 5 Authentication successful but no CAVV provided by issuer No
Yes, for intra US and Canada intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
No
Yes, for intra US and Canada intra-region transactions
  Attempt No 6 Authentication attempt but no CAVV provided by issuer No
Yes, for intra US and Canada intra-region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
  Unable Yes 7 Standard response for inter-regional authentication requests No
  Failed No 7 Authentication failed (status 180) No

Liability shift: Ogone Platform Merchants

These ECI values are internal Ingenico values common to all schemes that are intended only for Ogone platform merchants and will be returned through Connect.

Note: These are temporary and “scheme independent” values which merchants will receive. Ingenico plans to change this behavior so merchants can receive the industry scheme-standard values of the ECI.

Liability Shift: Ogone Platform Merchants

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—All cards No Authentication No 1 MOTO (no 3DS available) No
  No Authentication No 2 Recurring (no 3DS available) No
  No Authentication No 3 Installment (no 3DS available) No
Full Yes 5 Authentication available and successful Yes
  Attempt Yes 6 Proof of authentication attempt Yes (with some exception depending on schemes)
  Unable/Not Requested No 7 Normal SSL e-commerce transaction (without 3DS)  No
  Attempt No 12 Issuer or Cardholder not participating Yes (except MasterCard)
Failed No 91 Authentication failed * No
  Unable No 92 Authentication service or Enrollment verification service unavailable * No

*The merchant has the ability to continue/interrupt the transaction for these scenarios under the 3DS configuration pages.

3D Secure is an abbreviation for Three Domain Secure, which is the payment industry’s Internet Authentication Standard. All major credit card brands support this standard under their own label:

  • Visa -  Verified by Visa
  • MasterCard -  MasterCard SecureCode
  • Diners -  ProtectBuy
  • Amex -  SafeKey

Consumer Enrollment

A one-time process the cardholder undergoes to participate in the 3D Secure scheme. Pending the type of method supported by the issuer, the cardholder will either use static or dynamic (via token or mobile/smartphone) authentication credentials.

Authentication

During online shopping a prompt from the card issuer appears and requests the cardholder to enter the authentication credentials . The card issuer checks the credentials and the identity of the cardholder, and provides unique authentication values  to the merchant.

Liability Shift

 If  both the cardholder and the merchant are participating in the 3D Secure scheme and the transaction has been successfully authenticated, the liability of a chargeback shifts from the merchant to the cardholder’s issuing bank. This only applies for chargebacks based on a fraud reason code.

Key benefits

  • Enhance trust and confidence for your consumer’s online shopping experience 
  • Additional layer of protection against fraud 
  • Especially valuable for high transaction amounts
  • In case of a fraud chargeback reason code, the liability shifts to the card issuing bank if the obtained authentication values were used during the authorization and settlement. 

Supported Card Types

Verified by Visa Securecode ProtectBuy Amex
Visa Credit MasterCard Credit Diners Credit Amex Credit
Visa Debit MasterCard Debit Diners Credit Amex Credit
Visa Electron Maestro Diners Commercial Amex Commercial
Visa Commercial MasterCard Commercial Diners Commercial Amex Commercial

Support in Latin America

In Latin America 3D Secure is supported in the following countries: 

Country Product
Argentina - Visa Argentina Visa (Verified by Visa)
Brazil - Elavon Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Brazil - Cielo* Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Mexico - Banorte" Visa (Verified by Visa), MasterCard (MasterCard SecureCode
Peru - VisaNet* Visa (Verified by Visa)
* Acquirer approval is required for using the service. 

Process Flows

payment_flow_chart_3dsecure

Electronic Commerce Indicator

The authentication values provided by the issuer, the Electronic Commerce Indicator (ECI) and Cardholder Authentication Verification Value (CAVV) are exchanged in the authorization and settlement messages, and as such, enabled authenticated transactions can be distinguished from non-authenticated or partially authenticated transactions.

If certain conditions are met, and pending the level of the ECI and the presence of the CAVV, liability shift may also apply if the transaction was partially authenticated, for example when the merchant is participating but the cardholder is not.

Reporting

The Webcollect Payment Console (WPC) displays the Authentication result.

3dsecure_report

Additional Information

Chargeback Reason Codes

Visa

Reason codeChargeback conditions
75 The cardholder states that he does not recognize the transaction.
83 The transaction was processed without the permission of the cardholder, or a fictitious card account number was used and the transaction was not authorized.

MasterCard

Reason codeChargeback conditions
37 The cardholder states that he did not participate in the transaction, or that he did not perform the transaction.
63 The cardholder states that he does not recognize the transaction. Or the cardholder insists that he did not authorize the transaction.

Maestro

Reason codeChargeback conditions
22 The cardholder states that he did not initiate the transaction himself.

Diners

Reason codeChargeback conditions
C42 Card member did not authorize or participate in a card not present transaction - OR - any fraudulent charge where the Card is not present and the authorization data indicated that the Card was present.

Liability Shift Protection

Depending on where the card is issued, and the level of authentication, liability shift may or may not apply.

Liability Shift: Visa 

Region & card typeAuthenticationCAVVECIVisaDescription /ScenarioLiability Shift
All regions—consumer card No 6 Issuer, card range, or cardholder not enrolled Yes
  Full Yes 5 Authentication successful  Yes
  Full No 5 Authentication successful but no CAVV provided by the issuer Yes,
No, for US intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
Yes
  Attempt No 6 Authentication attempt but no CAVV provided by issuer Yes,
No, for US intra-region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
Yes, for Europe intra- region transactions
  Failed No   Authentication failed (status 180) No
All regions—commercial card No 6 Issuer, card range, or cardholder not enrolled. No
Yes, for Europe intra- region transactions
  Full Yes 5 Authentication successful  Yes
  Full No 5 Authentication successful but no CAVV provided by the issuer No
Yes, for Europe intra- region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
No
Yes, for Europe intra- region transactions
  Attempt No 6 Authentication attempt but no CAVV provided by issuer No
Yes, for Europe intra- region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
  Unable Yes 7 Standard response for  inter-regional authentication requests No
  Failed No 7 Authentication failed (status 180) No

Liability Shift: MasterCard/Maestro

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—consumer cards 1 Issuer, card range, or cardholder not enrolled. Yes
  Full Yes 2 Authentication successful Yes
  Full No 2 Authentication successful but no AAV provided by issuer Yes
No, for US intra-region transactions
  Attempt Yes 1 Cardholder not enrolled
AAV is provided in the authorization
Yes
  Attempt No 1 Authentication attempt but no AAV provided by issuer Yes
  Unable No Issuer is unable to authenticate Yes
No, for US intra-region transactions
  Failed No Authentication failed(status 180) No
All regions - Commercial Card 1 Issuer, card range, or cardholder not enrolled Yes
No, for intra US and Canada intra-region transactions
  Full Yes 2 Authentication successful Yes
  Full No 2 Authentication successful but no AAV provided by issuer Yes
No, for intra US and Canada intra-region transactions
  Attempt Yes 1 Cardholder not enrolled
AAV is provided in the authorization
Yes
No, for intra US and Canada intra-region transactions
  Attempt No 1 Authentication attempt but no AAV provided by issuer Yes
No, for intra US and Canada intra-region transactions
  Unable No Issuer is unable to authenticate No
  Failed No Authentication failed (status 180) No

Liability shift: Diners

  • The Issuer, Merchant/Acquirer, and Card Member are enrolled in ProtectBuy and the authentication response is either Full Authentication or Attempts Authentication.
  • Only the Issuer and Merchant/Acquirer are enrolled in ProtectBuy and the Card member is not participating. This includes when a Card Member opts-out of Activation During Shopping (ADS) or ADS is not offered. Liability shift occurs when the authentication response is Attempts Authentication.
  • The Issuer and Merchant/Acquirer are both participating but the Issuer’s Access Control Server (ACS) is unreachable, requiring the DCI Attempts ACS to perform stand-in authentication, and the authentication response is Attempts Authentication. This may occur whether or not the Card Member is enrolled.

Liability Shift: Amex

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—consumer cards No 6 Issuer, card range, or cardholder not enrolled. Yes
  Full Yes 5 Authentication successful Yes
  Full No 5 Authentication successful but no CAVV provided by issuer Yes
No, for US intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
Yes
  Attempt No 6 Authentication attempt but no CAVV provided by issuer Yes
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
Yes, for US intra-region transactions
  Failed No Authentication failed(status 180) No
All regions - Commercial Card No 6 Issuer, card range, or cardholder not enrolled No
Yes, for intra US and Canada intra-region transactions
  Full Yes 5 Authentication successful Yes
  Full No 5 Authentication successful but no CAVV provided by issuer No
Yes, for intra US and Canada intra-region transactions
  Attempt Yes 6 Cardholder not enrolled
CAVV is provided in the authorization
No
Yes, for intra US and Canada intra-region transactions
  Attempt No 6 Authentication attempt but no CAVV provided by issuer No
Yes, for intra US and Canada intra-region transactions
  Unable No 7 Issuer is unable to authenticate, issuer did not respond No
  Unable Yes 7 Standard response for inter-regional authentication requests No
  Failed No 7 Authentication failed (status 180) No

Liability shift: Ogone Platform Merchants

These ECI values are internal Ingenico values common to all schemes that are intended only for Ogone platform merchants and will be returned through Connect.

Note: These are temporary and “scheme independent” values which merchants will receive. Ingenico plans to change this behavior so merchants can receive the industry scheme-standard values of the ECI.

Liability Shift: Ogone Platform Merchants

Region & card typeAuthenticationAVVECIMCDescription /ScenarioLiability Shift
All regions—All cards No Authentication No 1 MOTO (no 3DS available) No
  No Authentication No 2 Recurring (no 3DS available) No
  No Authentication No 3 Installment (no 3DS available) No
Full Yes 5 Authentication available and successful Yes
  Attempt Yes 6 Proof of authentication attempt Yes (with some exception depending on schemes)
  Unable/Not Requested No 7 Normal SSL e-commerce transaction (without 3DS)  No
  Attempt No 12 Issuer or Cardholder not participating Yes (except MasterCard)
Failed No 91 Authentication failed * No
  Unable No 92 Authentication service or Enrollment verification service unavailable * No

*The merchant has the ability to continue/interrupt the transaction for these scenarios under the 3DS configuration pages.