| Warning | ||
|---|---|---|
| ||
The Cardinal Virtual SDK is currently in Beta and is subject to changes within the codebase and documentation. Please reach out to your AE if there are any questions. |
Step 2 Overview:
| Info |
|---|
OverviewTo get started with the Cardinal Virtual SDK we will need device data from the SDK. This data allows the issuer to build 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 likeand 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 will be used to the collection and encryption of the Device Data. |