Card3DSChallengeForwarded

Partner Responsibility

There are two possible 3DS modes, depending on the integration setup:

1. CMC (Cardholder Managed Challenge)

When a card issued with "authenticationMethod" : "Otp"

The customer interacts directly with the processor via a hosted 3DS challenge window.
The confirmation code (e.g., SMS OTP) is delivered by the processor.
The customer enters the code directly in the processor’s UI.

Partner responsibility:

• No code handling is required on your side

SMS delivery availability depends on the country — please refer to the 3DS SMS Availability by Country table for details.

2. Push with Confirmation

When a card issued with "authenticationMethod" : "Api"

Similar to Push mode, but instead of forwarding the code itself, you confirm the result.

Partner responsibility:

• Handle user interaction in your UI
• Call the Confirm 3DS API with one of the following statuses:
  • Verified — Partner has approved the 3DS authentication attempt
  • Canceled — Partner has canceled or rejected the 3DS authentication attempt
  • NotVerified — Partner has not approved the 3DS authentication attempt

Sample Request Payload:

{
  "userId" : "46a4e5c0-98a9-444e-a609-841547d35309",
  "event" : "Card3DSChallengeForwarded",
  "transaction" : {
      "threeDsSessionId" : "82520701-00c0-7a15-e389-08deb74cbc45",
      "cardId" : "d2b973fd-1e90-4e67-a376-b9d943bcace9",
      "merchant" : "starbucks",
      "amount" : 21.71,
      "transactionCurrencyCode" : "USD",
      "createdAt" : "2026-05-21T15:22:13Z"
  },
  "card3ds" : {
    "authenticationMethod" : "Api"
  }
}