8 Enroling your cards in 3D Secure

You can enrol your cards in 3D Secure using either the Thredd 3D Secure RDX Enrolment Thredd API or the Cards API . Your request must include the Thredd public token and the authentication type to use during authentication for this card (e.g., BIOMETRIC) and the value. For OTP SMS, you need to provide the mobile number as the value. For the Biometric authentication, the value is for your reference only. See Using the Card Enrolment API.

Thredd also provides an auto-enrolment option, which can be triggered either as a bulk update on all your existing cards not yet enrolled or can be triggered at the time when you create a new card. See Card Auto Enrolment.

Thredd saves the card enrolment record in our database.

8.1 Card Auto Enrolment

If you are migrating existing cards to 3D Secure, Thredd can automatically enrol all your cards in the 3D Secure RDX service: you can request auto-enrolment by specifying the authorisation types to auto-enrol on your 3DS Product Setup Form (PSF). See Completing your 3DS Product Setup Form.

Auto-enrol options include:

  • None— there is no auto-enrolment. You will need to do this using either Web Services or Cards API; see Using the Card Enrolment API.

  • Initial load— Thredd creates the authentication type credentials (e.g., OTP SMS or BIOMETRIC) for all existing cards. For OTP SMS, Thredd uses the phone number linked to the card (i.e., the phone number supplied when the card was created or updated). This is done as a single bulk update; adding credentials for any future new cards or applying any changes to credentials for existing cards must be done using using either Web Services or Cards API; see Using the Card Enrolment API

  • Continuous— Same as Initial load, however any future cards created (using the Card Create Thredd API or Card Create Cards API) will also have their credentials automatically registered for 3D Secure in the same way. When set to continuous, these cards are enrolled again automatically when approaching the expiry date. Applying any changes to credentials for existing cards must be done using using either the Thredd API or the Cards API; see Using the Card Enrolment API

Thredd auto-enrols the card in the default main and fallback authentication types set for your card product. For OTP SMS, Thredd auto-enrols using the mobile number linked to the card as the number for sending the SMS message to the cardholder during an SMS OTP authentication session.

To use this option, you must first have set up the default main and fallback authentication types on your 3DS Product Setup Form. See Completing your 3DS Product Setup Form.

Auto-enrolment enrolls all live and active cards. It is not recommended if you wish to exclude some cardholders from enrolment.

8.2 Card Unenrolment

For cards which have been enrolled manually or auto-enrolled, you can un-enroll the card if required by deleting the credentials linked to the card using Thredd's 3DS Webservice or the Card Enrolment API.. If using continuous autoenrolment, note that cards cannot be un-enrolled if the card status is still live and active. The Program Manager needs to disable Autoenrolment and switch to using the Card Enrolment API before unenroling cards. To disable Autoenrolment on your products, speak to your Thredd Implementation Manager or Customer Support Specialist.

Thredd does not automatically unenrol cards on behalf of Program Managers. If the status of the card changes to statuses such as Destroyed, Lost, or Stolen, the Program Manager needs to unenrol the respective cards using the 3DS webservice, Ws_AddUpDelCredentials (SOAP), or the 3DS credentials API (REST).