New Challenge Indicator Field for 3DS Transactions

Beginning on Tuesday January 21, 2025, a new field, three_ds_requestor_challenge_indicator, will be added to the 3DS authentication object. This field will be included in the 3DS Decisioning Request and will also be available in other places where 3DS data is provided, such as the three_ds_authentication.created webhook or when retrieving a 3DS Authentication by token. This field indicates the acquirer’s challenge preference for a transaction, providing additional visibility into the type of 3DS challenge requested (or not requested) during the authorization process.

Details

The three_ds_requestor_challenge_indicator field will support the following values:

• NO_PREFERENCE : No preference.
• NO_CHALLENGE_REQUESTED: No challenge requested.
• CHALLENGE_PREFERENCE: Challenge requested (3DS Requestor preference).
• CHALLENGE_MANDATE: Challenge requested (Mandate).
• NO_CHALLENGE_RISK_ALREADY_ASSESSED: No challenge requested (transactional risk analysis is already performed).
• DATA_SHARE_ONLY: No challenge requested (Data share only).
• OTHER: Represents any other uncommon values provided by the acquirer.

Disclaimer

The challenge indicator reflects the values passed by the acquirer and may not always correspond to the actual regulatory or market requirements. For example, some acquirers may pass a CHALLENGE_MANDATE value, even in cases where a challenge is not strictly mandated in a given market. The accuracy of this value depends on the acquirer’s implementation and usage.

Note

This change is purely additive and will not affect existing integrations. For more information about this addition, please see the API Reference.

If you have any questions or concerns, please contact us via the HELP link in your Lithic Dashboard.

The Lithic changelog has an RSS feed! To monitor for new update announcements, subscribe with your preferred RSS reader.