- Introducing Payer Authentication
- Implementing Cardinal Cruise Direct Connection API Payer Authentication
- Implementing SDK Payer Authentication
- API Fields
- Testing Payer Authentication
- 3-D Secure 1.0 Testing
On This Page
REST API
Implementing SDK Payer Authentication
This chapter summarizes the process of integrating SDK Payer Authentication services into
your mobile application. Payer Authentication services use the Cardinal Mobile SDK for
iOS or Android to facilitate the authentication. New SDK versions are frequently
released and you should ensure that you stay up-to-date with the current release. One
way to stay informed on about new releases is to subscribe to Cardinal's distribution
list to be informed of updates and other product announcements. You can subscribe by
going to this link: CardinalMobileSDKNotifications
Implementing the SDK in your mobile application requires either Android or iOS platform
application programming skills. Android API 21 or iOS 9 and XCode 8 are required.
The SDK is only designed to handle 3-D Secure 2.x transactions. If a 3-D Secure 1.0
transaction occurs, you must include functionality to open up a WebView.