Update 3DS Forwarding Method
Endpoint
PUT/api/v1/merchant/cards/{cardId}/3ds-forwarding/
Use this endpoint to update the 3DS forwarding method for either SMS OTP (One-Time Password) or in-app authentication.
Upon enrollment in 3DS forwarding, you can update the 3DS authentication method to SMS, in-app authentication, or both for a specific card.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
cardId |
string |
✅ | The unique identifier of the card you want to enroll in 3DS forwarding. |
Request Body
{
"biometricEnroll": true,
"smsEnroll": false
}
Body Parameters
| Name | Type | Required | Description |
|---|---|---|---|
biometricEnroll |
boolean |
❌ | Indicates whether biometric authentication is required for 3DS verification. Possible values: true (enabled), false (disabled). |
smsEnroll |
boolean |
❌ | Indicates whether SMS-based verification is enabled for the card during 3DS transactions. Possible values: true (enabled), false (disabled). |
📌 Important: Enabling biometric authentication requires additional technical implementation, such as configuring in-app workflows for biometric enrollment.
Example Request
PUT /api/v1/merchant/cards/{cardId}/3ds-forwarding/
Content-Type: application/json
{
"biometricEnroll": true,
"smsEnroll": false
}
Response
{
"message": "3DS forwarding method updated successfully"
}
Response Codes
| Status Code | Description |
|---|---|
200 OK |
3DS forwarding method updated successfully. |
400 Bad Request |
Invalid request parameters. |
401 Unauthorized |
Authentication failed. |
404 Not Found |
Card not found. |
500 Internal Server Error |
Server error. |