Challenge Autofill

The autofill feature on mobile devices allows the device operating system to automatically fill in forms, login credentials, and other information on websites and apps. It is designed to save the user’s time and effort by pre-populating fields with previously entered or saved information.
When autofill is enabled on a mobile device, it can store and retrieve various types of information, such as:

  • Names and addresses
  • Phone numbers and email addresses
  • Login credentials (usernames and passwords)
  • Other personal details

Autofill can be triggered in various ways, for example:

  • When the user starts typing in a form field
  • When the user taps on a form field
  • When the user uses a password manager or a browser’s built-in autofill feature

Autofill is available on most mobile devices, including Android and iOS devices, and can be managed through the device’s settings or through individual apps, such as web browsers or password managers.
In the context of a 3DS challenge on a mobile device, the autofill function could be used to automatically fill a password or SMS OTP on the challenge UI.

Benefits by Actor

Issuer:
  • reduced risk of Cardholder error during the challenge
Cardholder:
  • improved challenge experience by reducing friction

 

Technical Features

Preconditions

The authentication is initiated from a 3DS SDK with a 2.3.1 or higher protocol version.
The ACS has chosen to use the autofill feature during the challenge.

Overview

During a challenge, the ACS has the option to enable the Autofill option for the ACS UI template = Text. The ACS can select between OTP or Password.
When the Autofill option is enabled, the OS will display to the Cardholder a pop-up with the suggested input field. The Cardholder validates the input and submits their response.

Example Cardholder Experience Involving OTP

The ACS shall ensure that a text message is sent to the Cardholder’s phone.
Note: The device operating system may implement its own heuristics to determine whether the input field is for login or a verification code, which may lead to incorrect suggested input. The recommendation for the ACS is to conduct extensive tests before enabling the Autofill option. To learn more, please refer to the mobile operating systems’ detailed autofill information (Android and iOS).

The table below lists the data elements that may be provided in relation to 3DS Autofill.

Table 4.6: 3DS Data Elements Related to 3DS Autofill

Data Element

Description

Version

Challenge Entry Box

Defines the setting of an entry box in the Native UI OTP/Text Template:

  • Challenge Data Entry Keyboard Type
  • Challenge Data Entry Autofill
  • Challenge Data Entry Autofill Type
  • Challenge Data Entry Length Maximum
  •  Challenge Data Entry Label
  • Challenge Data Entry Masking
  • Challenge Data Entry Masking Toggle

2.3.1

 

Challenge Entry Box 2

 

Defines the setting of an entry box in the Native UI OTP/Text Template:

  • Challenge Data Entry Keyboard Type
  • Challenge Data Entry Autofill
  • Challenge Data Entry Autofill Type
  • Challenge Data Entry Length Maximum
  • Challenge Data Entry Label
  • Challenge Data Entry Masking
  • Challenge Data Entry Masking Toggle

2.3.1

2.2

 

Challenge Data Entry Autofill

Indicates if the 3DS SDK enables the autofill option for the Challenge Data Entry.

When enabled, the 3DS SDK/OS automatically copies the received or saved code or password in the Challenge Data Entry.

If Challenge Data Entry Autofill is not present, the option is not enabled.

2.3.1

 

Challenge Data Entry Autofill Type

Indicates the type of data expected when the Challenge Data Entry Autofill is active.

Refer to the following for Android or iOS.

2.3.1