3DS Lithic Decisioning

For customers who prefer simpler implementations, Lithic can decision on 3DS authentications on your behalf. Lithic’s goal is to decline the riskiest 3DS authentications based on network-provided signals. No real-time response is required from you in order to handle responding to these authentication requests, and no customization of the rules is supported at this time.

Summary of the flow of information:

• 3DS Flow:
  • Cardholder initiates e-commerce transaction at a 3DS-enabled merchant
  • Merchant/acquirer initiates a 3DS authentication request, which routes to Lithic
  • If the card is enabled for 3DS decisioning by Lithic, Lithic runs a set of risk-based rules, and generates a response
  • The 3DS authentication response is routed back from Lithic to the merchant/acquirer; at the same time, Lithic sends a three_ds_authentication.created event webhook via our Events API to the card program
• Authorization Flow (assuming the merchant decides to proceed with the authorization):
  • Merchant/acquirer initiates authorization request, which routes to Lithic
  • Lithic sends an ASA request to the card program, which indicates whether liability has shifted from the merchant to the issuer in the cardholder_authentication object
  • Card program incorporates the liability shift signal into its decisioning logic, and responds to the ASA request
  • The authorization response is routed back from Lithic to the merchant/acquirer

What do I need to do to get started? (more implementation details here)

• Let your Implementation Manager or our Support Team know you want to use 3DS Decisioning by Lithic on your card program
• Subscribe to 3DS authentication events via the Events API
• Start incorporating data included in the ASA request’s cardholder_authentication object into your decisioning