SLslashfi

Retrieve a 3D Secure challenge

Changed on

A 3D Secure challenge asks the cardholder to confirm a card purchase. Legal entities that decide their own challenges receive each one as a three_ds_challenge.requested webhook, then approve or decline it within about five minutes; a challenge left unanswered is declined.

get/v2/three-ds-challenges/{challengeId}

Request

  • Base URL
    https://api.slash.com
  • URL
    https://api.slash.com/v2/three-ds-challenges/{challengeId}
  • Auth
    API key in header X-API-Key

Path parameters

challengeIdstring required

3D Secure challenge id with the three_ds_challenge_ prefix.

Response

The 3D Secure challenge.

idstring required

3D Secure challenge id with the three_ds_challenge_ prefix.

cardIdstring required

The card the purchase was made with, with the c_ prefix.

status'pending' | 'approved' | 'declined' | 'expired' | 'failed' required

pending until it is decided. approved and declined record the decision. expired means it was not decided in time and the purchase was declined. failed means the decision could not be reported and the purchase was declined.

expiresAtstring date-time required

The deadline to approve or decline the challenge.

Example response

{
  "id": "three_ds_challenge_2rj4l7hmrrrcv",
  "cardId": "c_2rj4l7hmrrrcv",
  "merchant": {
    "description": "Acme Tickets",
    "location": {
      "country": "USA"
    }
  }
}

Changes