Page Comparison

Step 2 Overview:

info an overview of the customer and decide the corresponding actions.

Device Data is an object sent to Cardinal that allows you to pass information, both required and not required, to complete a 3DS 2.0 transaction using the Virtual SDK.

Below you will find tables that define the required and non-required fields for each group passed through on the SaveBrowserData object. At the end of this document, you will see an example JSON object, showing what the SaveBrowserData object looks like.

EMVCo Documents

SDK- Device Information

and enhance their risk models based on the consumers device information.

The Device Data will use the EMV 3DS requirements and specification for collecting and encrypting the device data on the user's device. Below you'll find the SDK - Device Information which represents the types of data and field names, where the Protocol and Core Functions Specification (Chapter 6.2 - Security Functions) will be used to the collection and encryption of the Device Data.

Tip

title	Device Data URLs

Please reach out to our Cardinal Account Executive for a list of URLs to use while testing and deploying Device Data Collection

Table of Contents

Device Parameters JSON Structure

JSON Keys	Description
DV	Data Version
DD	Device Data
DPNA	Device Parameter Not Available
SW	Security Warning

Device Parameter Unavailability Reasons

Reason Code	Description
RE01	Market or regional restriction on the parameter.
RE02	The platform version does not support the parameter or the parameter has been deprecated.
RE03	Parameter collection not possible without prompting the user for permission.
RE04	The parameter value returned is null or blank.

Android Sample

Code Block

{
    "DV": "1.0",
    "DD": {
        //Common Data Fields 
        "C001": "Android",
        "C002": "HTC One_M8",
        "C004": "5.0.1",
        "C005": "en-US",
        "C006": "Eastern Standard Time",
        "C007": "06797903-fb61-41ed-94c2-4d2b74e27d18",
        "C009": "John's Android Device"
        ...
        //Android-specific Device Parameters
        "A060": "REL",
        "A119": "1",
        "A117": -1,
        "A118": 0,
        "A115": "1",
        "A116": 0,
        "A113": "0",
        "A114": "30000",
		...
    },
    "DPNA": {
        "C010": "RE01",
        "C011": "RE03"
    },
    "SW": [
        "SW01",
        "SW04"
    ]
}

iOS Sample

Code Block

{
    "DV": "1.0",
    "DD": {
        //Common Data Feilds 
        "C001": "Android",
        "C002": "HTC One_M8",
        "C004": "5.0.1",
        "C005": "en-US",
        "C006": "Eastern Standard Time",
        "C007": "06797903-fb61-41ed-94c2-4d2b74e27d18",
        "C009": "John's Android Device"
        ...
        //iOS-specific Device Parameters
        "I008": "12.0",
        "I012": [
            "en"
        ],
        "I001": "2A9678FB-15D2-4554-8F70-F438AB62A146",
    },
    "DPNA": {
        "C010": "RE01",
        "C011": "RE03"
    },
    "SW": [
        "SW01",
        "SW04"
    ]
}

EMVCo Documents

SDK—Device Information V 1.5

View file

name	EMVCo_3DS_SDKDeviceInfo_1_45_102019 20213009 (21).pdf
height	250

Protocol and Core Functions Specification V 2.2.0

View file

name	EMVCo_3DS_Spec_v220_122018.pdf
height	150250

Versions Compared

Old Version 6

New Version Current

Key

Step 2 Overview:

Overview

Device Parameters JSON Structure

Device Parameter Unavailability Reasons

Android Sample

iOS Sample

EMVCo Documents

SDK—Device Information V 1.5

Protocol and Core Functions Specification V 2.2.0