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.
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
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.