Versions Compared

Old Version 4

changes.mady.by.user Chris Bohatka

Saved on

compared with

New Version Current

changes.mady.by.user Kayleigh LaSalle

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Overview

Activation Steps

Cardinal wants to get you up and running with CCA as quickly and seamlessly as possible. This section of the document will outline the simple steps that are necessary in order to take advantage of Cardinal Mobile SDK.

Insert excerpt
Setting up CardinalMobileSDK - Android - V 2.2.5
Setting up CardinalMobileSDK - Android - V 2.2.5
nopaneltrue

Step 3 - Setup the Initial Call to Cardinal

Insert excerpt
Initial Call to Cardinal and Response - Android - V 2.2.5
Initial Call to Cardinal and Response - Android - V 2.2.5
nopaneltrue

Step 4 - Create a Lookup Request/Response to Centinel 

Create an API call to your backend server in order to send a Lookup Request (cmpi_lookup) to Cardinal's Centinel platform for initiating the Consumer Authentication transaction.  The Centinel platform manages all of the routing and connectivity, as well as the rules engine for all of the various 3-D Secure protocols and versions.  Please follow the Getting Started and Lookup Request/Response sections for completing your backend integration: Cardinal (cmpi) Messages

Note

Required Field for identifying as an SDK transaction : 

    • <DeviceChannel>SDK</DeviceChannel>
    • <DFReferenceId>ReferenceId</DFReferenceId>

ReferenceId is consumerSessionId returned on init completion, if no referenceID is passed in serverJwt. Else you can use that referenceID as DFReferenceId


Step 5 - Handle the Centinel Lookup Response and Create the Authentication Session

Insert excerpt
Handle the Centinel Lookup Response and SDK Handle the Challenge UI - Android - V 2.2.5
Handle the Centinel Lookup Response and SDK Handle the Challenge UI - Android - V 2.2.5
nopaneltrue

Step 6 - JWT Validation

Once the response JWT arrives in the onValidated, you will need to send the response JWT to your backend for verification and consumption. We recommend that any values sent to 3rd parties are sourced from the response JWT after it has been properly validated.

Note
titleSecurity Warning

For security reasons, all JWT validation must be done on the server side.


Info
titleLooking for more information?
For more in-depth information on JWT validation including code samples in a few languages, check out the JWT Validation page.

Insert excerpt
CC:JWT Validation
CC:JWT Validation

Step 7 - Cleanup

The cleanup method should be called after the transaction has completed. This clears Cardinal.java’s current instance so when Cardinal.getInstance() is called again, a new instance is created. This can be called from any location within your application.

Code Block
languagejava
themeEmacs
Cardinal.getInstance().cleanup();


Table of Contents