...
...
| 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. |
.png?version=1&modificationDate=1585668860629&cacheVersion=1&api=v2)
Below is a list of components that we will be discussing as we go through the Virtual SDK documentation.
Virtual SDK Client
The SDK Client will be implemented by the merchant directly within their application/device and can leverage conventional or proprietary languages. The Virtual SDK client will be responsible for assisting in the device data collection, render step-up challenge, and transport response.
...
Virtual SDK Server
The
...
Virtual SDK Server will be used to communicate with
...
Virtual SDK Client and Cardinal. The functionality will include, device data
...
Virtual SDK Server
The Virtual SDK server functionality is contained in the Cardinal Network. All interactions to the Virtual SDK server will be controlled using APIs with JSON/XML payloads.
...
encryption, sending/receiving CMPI Lookup and Stepup Messages, communicating encrypted Challenge Request (CReq), decrypting Challenge-Response before sending it to the Virtual SDK Client to displace the challenge.
Cardinal Centinel
Centinel is a rules-based authentication solution that gives merchants the ability to create customized, adjustable rules, from hundreds of different enhanced data fields. This in addition to various other technologies that determine whether a transaction is being conducted by a legitimate consumer while utilizing the 3-D Secure protocols.
For the Virtual SDK, the merchant will be utilizing Centinel to communicate with the card networks on behalf of the merchants.
...
Next Steps
With an understanding of the components that we are touching, let's move on
...
to Step 2:
...
Submitting & Receiving the Lookup
| Table of Contents |
|---|