Getting Started

Owned by Siddhartha Chikatamalla
Last updated: Jan 16, 2024 by Kayleigh LaSalle
2 min read

Development Notice

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.

You will need credentials provided by Cardinal to complete testing as we move through this process. Please reach out to your representative at Cardinal if you need to obtain them.

Overview

The Cardinal Virtual SDK is an implementation approach to achieve the 3DS 2.x authentication functionality as defined by the EMVCo 3DS 2.x specification in an environment where the Native App SDK for iOS and Android as defined within the specification is not feasible due to security, internal policies, or technology limitations on the host device.

  • The Virtual SDK provides for the ability to split the functionality of the EMVCo SDK into client and server components.
  • The Virtual SDK client discussed in this document, as well as sequence flow is to delineate the functionality that occurs with the merchant app as it related to the SDK implementation and does not infer any type of 3rd party code.
  • The Virtual SDK client is completely developed, controlled and rolled out by the Merchant.
  • The Virtual SDK approach is envisioned to operate within the current definition of EMVCo 2.1,2.2 specifications without requiring specific modifications to the other parties in the ecosystem such as 3DS Server, DirectoryServer, ACS.
  • Future EMVCo 3DS 2 specification version might include enhancements related to Virtual SDK


On this page:

Flow

Process Overview

Component Overview

The component overview describes the systems and terms that this integration will be touching.

Step 1: Device Data Collection & Encryption

To start the authentication process, device data will need to be sent to Cardinal for the transaction.

Step 2: Submitting & Receiving the Lookup

To proceed with authentication, it is necessary to make a cmpi_lookup call into Cardinal.

Step 3: The Lookup Response is a Challenge, What's Next?

So you got a challenge? We will walk through how our systems will talk to your systems during this event.

Step 4: Get the Needed information for Authorization

To complete authorization, details from the authentication process will be needed. These are the details.