July 27, 2023

Upcoming Modifications to the Cardholder Authentication Object (ASA and Transaction object)

In conjunction with our upcoming release of a new 3DS product offering (see API documentation for more information), we are announcing a few modifications to the cardholder_authentication object to provide additional clarity into what (if any) type of cardholder authentication has taken place before the transaction took place.

• New fields to be introduced to ASA on July 31 (Transaction object to follow in mid-August):
  • authentication_result will indicate, where relevant, the outcome of the 3DS authentication process
  • decision_made_by will indicate which party (network, Lithic, customer, or unknown), where relevant, made the 3DS authentication decision
  • three_ds_authentication_token will identify the 3DS authentication API object associated with the transaction
• Two existing fields are deprecated and will be removed on November 7:
  • verification_attempted currently indicates whether a 3DS challenge flow was used; this will be replaced with a new field (to be announced in the future) when Lithic begins supporting challenge flows
  • verification_result currently indicates whether a transaction is considered 3DS authenticated; this is replaced with the new authentication_result field that presents a clearer picture of whether a 3DS authentication took place, and if so, what the result was