Skip to main content

Send an Embedded or Hybrid SCA Challenge

POST 
https://api.paysafe.com/digitalwallets/v1/auth/sca/events/:eventId/challenges

Sends a challenge via a secure communication mechanism as part of the ongoing Embedded or Hybrid SCA process.

Once an SCA process is initiated, a challenge must be sent through one of the available verification mechanisms (e.g., send an OTP code via SMS). Тhe challenges have their own expiration (e.g., the OTP sent via SMS is valid for only a short time). If a challenge expires, a new one must be sent. A challenge sent for the same process can increment the currentChallenges field. This process can only be performed a limited number of times, as defined by allowableChallenges (its value is determined by the best security practices). If this limit is exceeded, an error will be returned, and no additional challenges can be sent for the same process until a cooldown period has elapsed. After this period, the currentChallenges are reset, and new challenges can be sent for the same process as previously described.

More details can be found in Strong Customer Authentication.

Request​

Responses​

Created

Authorization: http

name: Bearertype: httpscheme: bearerdescription: Bearer authentication (also called token authentication) is an HTTP authentication scheme that involves `security tokens` called bearer tokens. In the present context, `configuration & user security tokens` are accepted to access the authentication features.

Request Collapse all
Base URL
https://api.paysafe.com/digitalwallets/v1
Auth
Parameters
— pathrequired
Body
{
  "walletOperationId": "a5865fd6-18c2-45a8-9953-1c00eac36c36",
  "verification": {
    "method": "OTP",
    "channel": "SMS",
    "action": {
      "language": "en",
      "returnUrl": "https://some-process.paysafe.com/"
    }
  },
  "deviceInfo": {
    "appType": "WEB_APP",
    "threatMetrixSessionId": "string",
    "deviceId": "string"
  }
}
ResponseClear

Click the Send API Request button above and see the response here!