3DS

Simulate 3DS authentication

Simulates a 3DS authentication request from the payment network as if it came from an ACS. If you're configured for 3DS Customer Decisioning, simulating authentications requires your customer decisioning endpoint to be set up properly (respond with a valid JSON). If the authentication decision is to challenge, ensure that the account holder associated with the card transaction has a valid phone number configured to receive the OTP code via SMS.

post/v1/three_ds_authentication/simulate

Request

  • Base URL
    https://sandbox.lithic.com
  • URL
    https://sandbox.lithic.com/v1/three_ds_authentication/simulate
  • Auth
    API key in header Authorization

Request body

panstring required

Sixteen digit card number.

card_expiry_check'MATCH' | 'MISMATCH' | 'NOT_PRESENT'

When set will use the following values as part of the Simulated Authentication. When not set defaults to MATCH

Example request

{
  "merchant": {
    "country": "USA",
    "id": "OODKZAPJVN4YS7O",
    "mcc": "5812",
    "name": "COFFEE SHOP"
  },
  "pan": "4111111289144142",
  "transaction": {
    "currency": "GBP"
  }
}

Response

OK

tokenstring uuid

Globally unique identifier for the 3DS authentication.

Changes

No recorded changes to this operation across all 103 revisions of this API.