three_ds_authentication.created
Occurs when a 3DS authentication is created.
Payload
The type of event that occurred.
Type of account/card that is being used for the transaction. Maps to EMV 3DS field acctType.
Type of authentication request - i.e., the type of transaction or interaction is causing the merchant to request an authentication. Maps to EMV 3DS field threeDSRequestorAuthenticationInd.
Indicates the outcome of the 3DS authentication process.
Indicates whether the expiration date provided by the cardholder during checkout matches Lithic's record of the card's expiration date.
Globally unique identifier for the card on which the 3DS authentication has occurred. Permitted values: 36-digit version 4 UUID (including hyphens).
Entity that orchestrates the challenge. This won't be set for authentications for which a decision has not yet been made (e.g. in-flight customer decisioning request).
Channel in which the authentication occurs. Maps to EMV 3DS field deviceChannel.
Date and time when the authentication was created in Lithic's system. Permitted values: Date string in the ISO 8601 format yyyy-MM-dd'T'hh:mm:ssZ.
Entity that made the authentication decision. This won't be set for authentications for which a decision has not yet been made (e.g. in-flight customer decisioning request).
Either PAYMENT_AUTHENTICATION or NON_PAYMENT_AUTHENTICATION. For NON_PAYMENT_AUTHENTICATION, additional_data and transaction fields are not populated.
Indicates whether a challenge is requested for this transaction
- 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 - Other indicators not captured by above. These are rarely used
Type of 3DS Requestor Initiated (3RI) request — i.e., a 3DS authentication that takes place at the initiation of the merchant rather than the cardholder. The most common example of this is where a merchant is authenticating before billing for a recurring transaction such as a pay TV subscription or a utility bill. Maps to EMV 3DS field threeRIInd.
Globally unique identifier for the 3DS authentication. Permitted values: 36-digit version 4 UUID (including hyphens).
Example payload
{
"event_type": "three_ds_authentication.created"
}Response
Return a 200 status to indicate that the data was received successfully