Overview
The Cardinal Mobile SDK for iOS 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.
Minimum Requirements
Prerequisites
Within 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:
Generating a Server JWT
API Documentation
We have two implementation options :
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
This is a 7-Step process to get your application up and running our Quick Auth frictionless flow based on 3DS 1.0 transactions.
Link to documentation: Cardinal Mobile SDK iOS Documentation for Quick Auth
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.
Issues
Please report bugs, comments, or concerns to your Cardinal Implementation Manager
Frequently Asked Questions
Error rendering macro 'excerpt-include' : User 'null' does not have permission to view the page 'STAG:iOS Frequently Asked Questions'.