Overview
The Cardinal Mobile SDK for Android makes it easy for you to activate and integrate Cardinal Consumer Authentication (CCA) into your checkout flow. In just a few simple steps, you will be able to create a great user experience for your consumers, while utilizing the benefits of CCA.
.png?version=1&modificationDate=1610557531483&cacheVersion=1&api=v2&height=250)
| Excerpt |
|---|
Minimum Requirements
PrerequisitesWithin the Cardinal Mobile SDK ecosystem, authentication between the Merchant and Cardinal is handled via a JWT (JSON Web Token). To initialize the system for processing, a JWT must be generated server-side and passed into the first call in the chain. Within the JWT, you will need to specify your Org Unit Id, API Key & API Identifier. If you weren't given these values upon registration, please contact your account manager. For more information on generating a JWT, please see the following instructions: |
API Documentation
/wiki/spaces/STAG/pages/3190685727Cardinal Implementation
This is a simple 6-Step process to get your application up and running 3DS 2.0 transactions, with the option to customize challenge screens using UI Customization.
Link to documentation: Cardinal implementation with optional UI Customization
| Page Tree | ||||
|---|---|---|---|---|
|
Tutorial and Examples
A Quick Start guide is available to help you set up your build environment and get started with the Cardinal Mobile SDK by leading you through the creation of a simple application that connects to Cardinal. Within the download package, you will also find a demo app with full source code to help get you started.
| Note |
|---|
Links to our demo application can be obtained by reaching out to your Client Manager or Implementation Manager. |
Issues
Please report bugs, comments, or concerns to your Cardinal Implementation Manager
Frequently Asked Questions
| Insert excerpt | ||||
|---|---|---|---|---|
|
| Table of Contents |
|---|