Description: Learn how to view and use 3D Secure (3DS) data in Lighthouse Business Manager (LBM) to understand transaction authentication, identify liability shift protections, and support fraud-related chargeback investigations.
Overview
Lighthouse Business Manager (LBM) provides detailed 3D Secure (3DS) data to improve visibility into transaction authentication and fraud protection. These data points help merchants understand how transactions were verified, determine when liability shift applies, and confidently manage disputes.
3DS-Related Data Fields
The following 3DS data fields are available in the Transaction Manager and Transaction Summary views:
- 3DS Flag: Indicates whether a transaction was processed using the 3D Secure authentication protocol.
- 3DS Liability Shift: Shows whether liability for potential fraud-related chargebacks has shifted from the merchant to the card issuer.
- ECI (Electronic Commerce Indicator): A technical indicator that helps identify where an authentication failure may have occurred.
- 3DS Challenge Flow: Identifies whether the cardholder completed a manual authentication challenge (such as a one-time passcode) or if the transaction was approved without a challenge.
- 3D Secure Version: Displays the specific 3D Secure protocol version used for the transaction (for example, 2.0 or 2.1).
How to Use These Data Points
These fields are designed to help you manage transaction security and fraud risk more effectively.
Customize Your View
By default, 3DS-related columns are hidden in the Default Transaction Manager. You can enable them at any time using the column selector to tailor your view.
Filter by Security Status
Use the 3DS Liability Shift filter to locate transactions with a status of:
- Successful
- Failed
- Unspecified
This is especially helpful when assessing exposure to fraud-related chargebacks.
Support Chargeback Disputes
For fraud-related disputes, the 3DS verification details in the Transaction Detail view can be used as evidence that the transaction was authenticated according to 3D Secure requirements.
Important: 3D Secure authentication attempts appear as standalone records in LBM. A successfully authenticated 3DS transaction generates two records:
- One record for the 3DS authentication attempt
- A separate record for the resulting financial transaction (such as a Sale or Authorization)
If the 3DS authentication fails, only one record appears, representing the standalone authentication attempt.
This record structure ensures clear separation between authentication activity and financial transactions.
Comments
0 comments
Please sign in to leave a comment.