Recent Revisions to This Document

About This Guide

Introducing Payer Authentication
- Overview of Chargeback Protection
- Payer Authentication Process Flow Overview
- Integrating Payer Authentication into Your Business
- Using Secure Acceptance with Payer Authentication
- Required Merchant Information

Implementing Cardinal Cruise Direct Connection API Payer Authentication
- Prerequisites
- After Implementation and Before Go Live
- Step 1: Payer Authentication Setup Service
- Step 2: Device Data Collection Iframe
- Step 3: Payer Authentication Check Enrollment Service
- Step 4: Step-Up IFrame
- Step 5: Payer Authentication Validation Service
- Cardinal Cruise Direct Connection Integration Examples

Implementing SDK Payer Authentication
- Implementation Overview
- Process Flow for SDK Integration
- Prerequisites for SDK Implementation
- Using the Android SDK
- Using the iOS SDK
- Running Payer Authentication in SDK

Hybrid Payer Authentication
- Implementation Overview
- Process Flow for Hybrid Integration

API Fields
- Required Fields for Setting Up Payer Authentication
- Required Fields for Checking Enrollment in Payer Authentication
- Required Fields for Validating Payer Authentication

Testing Payer Authentication
- Testing Process
- Expected Results
- 3-D Secure 1.0 Testing
- Test Cases for 3-D Secure 2.x
- Payer Authentication Exemption Test Cases

Website Modification Reference
- Website Modification Checklist
- 3-D Secure Services Logos
- Informational Message Examples

Alternate Methods for Device Data Collection
- Device Data Collection Overview
- Collecting Device Data

Upgrading Your Payer Authentication Implementation
- Benefits
- PSD2 Impact
- Recommended Integration
- Migration FAQ

Payer Authentication Transaction Details in the Gateway Portal
- Payer Authentication Search
- Storing Payer Authentication Data
- Searching for Payer Authentication Details

Payer Authentication Reports
- Payer Authentication Summary Report
- Payer Authentication Detail Report

Glossary

REST API

Hybrid Payer Authentication

If you are just getting started with Payer Authentication, you should use the Cardinal Direct Connection API implementation method. It is the newest and most advanced method of integrating 3-D Secure into your transaction process and is the method the majority of our customers choose to use. The Hybrid implementation is still available when customer support determines that it best fits your company's business needs.

The same prerequisites involving API keys and JSON Web Tokens necessary for the SDK integration are also required for the Hybrid integration. In addition, you need to add JavaScript to your checkout page and setup BIN detection as explained below. Complete these prerequisites before continuing with your Hybrid implementation. Additional information about configuring the Hybrid version of payer authentication is available at Cardinal Cruise documentation.