Data Only

What is Data Only?

Data Only is an optional parameter that can be used to contribute to the card brand and issuer’s database, improving authentication performance. Data Only transactions are part of the 3DS protocol but exclude the challenge authentication request step. Thus, the Data Only transaction flow will always be frictionless and without liability shift (the risk in case of chargeback remains with the store).

When to use Data Only?

Data Only can be used to share transaction data with the issuer, frictionless. If the Data Only field is parameterized in the script, the card brand will receive the data and share this information with the issuer. Over time, the issuer will have more transaction data from that card and cardholder, providing more elements for authentication.

Is there a liability shift in Data Only transactions?

In Data Only transactions there is no liability shift; the merchant is responsible in case of chargeback.

⚠️

  • 3DS Full: for authenticated transactions, the liability in case of chargeback shifts to the card issuer;
  • 3DS Data Only: for authenticated transactions, the responsibility in case of chargeback lies with the merchant (there is no liability shift).

How to use Data Only?

Simply parameterize the bpmpi_auth_notifyonly. Authorization occurs in the same way as any Authorization with Authentication.

To use Data Only, in the script integration, parameterize the bpmpi_auth_notifyonly field described in the item Authentication Step – step 3 – Class Mapping.

In the Data Only model, all authentication is frictionless.


Which brands accept Data Only?

Data Only is valid for Mastercard and Visa brands.

For Data Only Mastercard, the ECI will always be 4;
For Data Only Visa, the ECI will always be 7.


ℹ️

3DS protocol version 2.2 is required for Visa and Mastercard Data Only authentication.

What are the benefits of Data Only?

  • Frictionless for the shopper, as there is no challenge;
  • Improve conversion by enriching the issuer’s database.

What are the differences between standard 3DS transactions and 3DS Data Only?

Feature3DS full3DS Data Only
Frictionless experienceWith challenge or frictionlessAlways frictionless (no challenge)
Transaction latencyHigherLower or none
Liability shift (in case of chargeback)Brand or issuer, if successfully authenticated*Merchant
Influence on issuer approvalYesYes
Authentication cycleYesNo

*It is important to check the ECI value to ensure whether the transaction was authenticated or not.

⚠️

Important

  • In Data Only transactions, the liability in case of chargeback due to fraud remains with the merchant;
  • It is possible to use Antifraud in 3DS Authentication transactions with Data Only.