Respond to 3DS Verification

Endpoint

POST/api/v1/merchant/cards/{cardId}/3ds-answer/{initiateActionId}/

An endpoint to respond to a 3DS authentication request using in-app authentication.

Use this endpoint to respond to a webhook notification when you have enabled 3D Secure (3DS) forwarding for your card. This allows you to make 3DS decisions using an alternative method instead of SMS OTP.

You must use the initiateActionId from the 3DS Forwarding Webhook as a path parameter.
The response must be sent within 5 minutes from the transaction timestamp; otherwise, the request will timeout.
If a response attempt occurs after the timeout, an error should be returned to the user.

Path Parameters

Name	Type	Required	Description
`cardId`	`string`	✅	A unique identifier for the card used in this transaction, which is currently undergoing a 3DS challenge flow.
`initiateActionId`	`string`	✅	A unique identifier for the transaction action that initiated the current 3DS challenge checkout process.

Request Body

{
  "approve": true
}

Body Parameters

Name	Type	Required	Description
`approve`	`boolean`	✅	Indicates whether the transaction is approved or declined following identity verification. Possible values: `true` (approve), `false` (decline).

Example Request

POST /api/v1/merchant/cards/{cardId}/3ds-answer/{initiateActionId}/
Content-Type: application/json

{
  "approve": true
}

Response

{
  "message": "3DS authentication response submitted successfully"
}

Response Codes

Status Code	Description
`200 OK`	3DS authentication response submitted successfully.
`400 Bad Request`	Invalid request parameters or response timeout exceeded.
`401 Unauthorized`	Authentication failed.
`404 Not Found`	Card or transaction not found.
`500 Internal Server Error`	Server error.