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.

Overview

To get started with the Cardinal Virtual SDK we will need device data from the SDK. This data allows the issuer to build 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. 

Refer to this location for materials on Encryption Documentation