3D Secure Guide (Cardinal)

This guide describes the Thredd 3D Secure Realtime Data eXchange (RDX) service and how to implement a 3D Secure project with OTP, KBA, or biometric/In-app authentication.

Topics covered: Authorisation types, transaction flows, project steps, completing the 3DS product setup form, RDX and OAuth API endpoints, Implementing Oauth, Enroling cards in 3D Secure, auto-enrolment, test and rollout, Cardinal Portal, Cardinal Test Simulator, Biometric/In-App authentication, KBA, 3DS Screens, Language support, NotifyValidate REST API, validation timeout, Support for 3D Secure versions, creating 3DS rules and policies, 3DS Test Merchants

For information on Apata version of 3D Secure, see 3D Secure Guide (Apata).

Current Version

Click the links below to view the current version, available in both Online (HTML) and PDF format.

Online (HTML)	PDF	What's Changed?	Version
3D Secure Guide (Cardinal)		Updates to content and graphics to align with taxonomy updates on our documentation portal. In the section PRD1 and PRD2 - Cloud Production Environments, updated the oAuth endpoint for PRD2 to `p1ists.globalprocessing.net`.	2.1

Online (HTML)

PDF

What's Changed?

Version

3D Secure Guide (Cardinal)

Updates to content and graphics to align with taxonomy updates on our documentation portal.

In the section PRD1 and PRD2 - Cloud Production Environments, updated the oAuth endpoint for PRD2 to p1ists.globalprocessing.net.

2.1

Older Versions

Older versions are available in PDF format only.

File Name	What's Changed?	Version
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 2.0	Added details of when you might receive the FAILWITHFEEDBACK status in the response to a `NotifyValidate` API call. See the FAQs. Restructuring of guide topics. Updates to reflect changes to the Thredd 3DS Product Setup Form (PSF) and steps in a 3D Secure project. Added details of using the Cards API 3D Secure endpoints. Added details of using Compliance Manager. New FAQs added. Added details of relevant Cards API functionality and endpoints. Guide rebrand to new company name and brand identity.	2.0
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.9	Added additional IP addresses that need to be allowed for secure communication between Thredd and your systems when using one of our cloud production environments (PRD1 or PRD2). See Authorising Thredd IP Addresses. Guide updated to reflect that the OUTOFBAND authentication type is now available. Note: Please discuss with your Implementation Manager before implementing this method. Added a note to indicate that your `NotifyInitiateAction` endpoint must resolve to a static IP address. See Steps in a 3D Secure Biometric/In-app Project. Removal of references to OTP Email, which is currently not supported. Updated the Copyright Statement.	1.9
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.8	Correction to the OAuth Introspect Example which shows how to validate a bearer token. New MerchantAppRedirectURL field added to the `NotifyInitiateAction` API. This field provides the callback URL to use to enable the merchant's app to redirect the cardholder back to their checkout page after completing the authentication session. See Appendix 3: Biometric/OOB Fields. Fix to examples in Appendix 4: KBA Questions. Updated Thredd UAT IP addresses.	1.8
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.7	New guide layout and HTML version now available	1.7
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.6	Added details of Dynamic Cardholder Verification (CVV) support to Supported Authentication Types.	1.6
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.5	Added new section with details of auto-enrolment of 3D Secure credentials when an expiring card is renewed resulting in a new card PAN. See Card Renewals and Credential Auto-enrolment.	1.5
3D Secure Guide - RDX with OTP, KBA and Biometric/In-app authentication 1.4	Updates for the Out of Band (OUTOFBAND) authentication method. Added notes to clarify that the OUTOFBAND authentication type is not yet available. Correction: the spelling of the bearer token in the header of the NotifyInitiateAction request should be Authorization: Bearer	1.4
3D Secure Guide - RDX with Biometric/In-app authentication 1.3	Addition of Knowledge Based Authentication (KBA). Removal of references to OTP Email, which is currently not supported.	1.3
3D Secure Guide - RDX with Biometric/In-app authentication 1.2	Removed the port number from UAT URLs.	1.2
3D Secure Guide - RDX with Biometric/In-app authentication 1.1	Address updates and update to Figure 3: 3D Secure Authentication Process Using RDX and Biometrics. New Appendix 3: Biometric/OOB Fields.	1.1
3D Secure Guide - RDX with Biometric/In-app authentication 1.0	New guide. Describes the Thredd 3D Secure Realtime Data eXchange (RDX) service and how to implement a 3D Secure project with biometric/In-app authentication.	1.0