---
title: "Respond to a Challenge Request"
method: POST
path: "/v1/three_ds_decisioning/challenge_response"
tags: ["3DS"]
---

# Respond to a Challenge Request

`POST /v1/three_ds_decisioning/challenge_response`

Card program's response to a 3DS Challenge Request.
Challenge Request is emitted as a webhook [three_ds_authentication.challenge](https://docs.lithic.com/reference/threedsauthenticationchallengewebhook) and your Card Program needs to be configured with Out of Band (OOB) Challenges in order to receive it (see https://docs.lithic.com/docs/3ds-challenge-flow for more information).

## Request body

- ChallengeResponse — Response from Card Program to a 3DS Authentication challenge
  - `token` string, uuid, required — Globally unique identifier for 3DS Authentication that resulted in PENDING_CHALLENGE authentication result.
  - `challenge_response` 'APPROVE' | 'DECLINE_BY_CUSTOMER', required — Whether the Cardholder has approved or declined the issued Challenge

## Response `200`

Challenge Response was received and forwarded to the ACS

## Other responses

- `400` — Invalid request body
- `404` — The provided token was not found
- `422` — Challenge Response could not be actioned because a response was already set, or the status was updated by the upstream 3DS Service
- `500` — Lithic Error

---

[API](https://skmtc.net/lithic-com/apis/lithic-developer-api.md) · [All operations](https://skmtc.net/lithic-com/apis/lithic-developer-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lithic-com/lithic-developer-api/revisions/53ab5d4e2adb/schema)