---
title: "Data-only flow"
description: "Implement 3D Secure 2 without sending an authentication request to the issuer."
url: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/other-3ds-flows/data-only"
source_url: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/other-3ds-flows/data-only.md"
canonical: "https://docs.adyen.com/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/other-3ds-flows/data-only"
last_modified: "2019-07-31T09:56:00+02:00"
language: "en"
---

# Data-only flow

Implement 3D Secure 2 without sending an authentication request to the issuer.

[View source](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/other-3ds-flows/data-only.md)

**Adyen is no longer developing the Classic API integration**

This page is for the Classic API (`/authorise`) integration, which we no longer accept new integrations with.

We strongly recommend migrating to the newer [data-only integration on Checkout API](/online-payments/3d-secure/other-3ds-flows/data-only) integration. To use this newer integration, you must also [migrate to the Checkout API](/online-payments/upgrade-your-integration/migrate-to-checkout-api).

In a regular 3D Secure 2 flow, the payment has to be authenticated by the issuer before it can be authorised. In a data-only flow, you send the same 3D Secure 2 data but the schemes directly handle the authentication request. The data-only request goes directly to the scheme, and then the scheme includes their own risk data in the authorisation message before sending it to the issuer.

Data-only is currently only available for Mastercard. Before using the data-only flow, make sure to check the regulations that apply to your country or region. Using the data-only flow in countries/regions where SCA is mandated (for example, within the EEA) can lead to an increased amount of authentication rejections.

## Using the data-only flow

The data-only flow allows you to use the scheme's 3D Secure-specific risk scoring models, which helps increase your authorisation rates in specific markets, without incurring additional fees.

You can also use the data-only flow when you integrate with Adyen as a standalone 3D Secure 2 provider with an [authentication-only implementation](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/native-3ds2/authentication-only-integration).

Because there is no authentication request sent to the issuer in a data-only flow, your shoppers will not be presented with a 3D Secure 2 challenge.

Because no strong customer authentication is applied to a data-only transaction, the chargeback liability stays with you and does not shift to the issuer.

## Before you begin

Before you can start accepting 3D Secure 2 authenticated transactions on browsers or in-app, make sure that you:

1. Sign up for an Adyen test account at <https://www.adyen.com/signup>. 
2. [Get your API Key](/development-resources/api-credentials#generate-api-key). Save a copy as you'll need it for API calls you make to the Adyen payments platform.
3. Install one of our [Libraries](/development-resources/libraries) to connect with the Adyen APIs. For more information on these steps, refer to [Get started with Adyen](/get-started-with-adyen).

## Submit a data-only payment request

To indicate that you want to use the data-only flow, specify in your [/authorise](https://docs.adyen.com/api-explorer/#/Payment/authorise)  request:

* `additionalData.threeDS2DataOnly`: **true**

Other required fields and the response to your [/authorise](https://docs.adyen.com/api-explorer/#/Payment/authorise) request are the same as in case of a regular 3D Secure flow, depending on your integration.

For more information, refer to [Browser-based integration](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/native-3ds2/browser-based-integration#submit-a-payment-request), [iOS 3D Secure 2 SDK](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/native-3ds2/ios-sdk-integration), [Android 3D Secure 2 SDK](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/native-3ds2/android-sdk-integration), or [Authentication-only integration](/online-payments/classic-integrations/classic-api-integration/3d-secure-authentication/native-3ds2/authentication-only-integration).

#### Request

```bash
curl https://pal-test.adyen.com/pal/servlet/Payment/v50/authorise \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
    ...
    "additionalData": {
      "threeDS2DataOnly": true
    },
    ...
  }'
```

## Testing the data-only flow

Use the test card below to try the 3D Secure 2 data-only flow.

| Card Type  | Card Number         | Expiry Date | CVC/CVV |
| ---------- | ------------------- | ----------- | ------- |
| Mastercard | 5201 2818 2278 3116 | 10/2020     | 737     |
