OTP

This endpoint allows system integrators to trigger a new OTP (One-Time Password) request during a payment user flow — when supported by the financial provider. It is particularly useful when the user’s OTP has expired or was not received.

Path Parameters

NameTypeRequiredPurpose
customerIdstringUnique ID of the customer
providerstringName of the financial provider
operationIdstringUnique ID of the operation that triggered the OTP requirement

This endpoint is called only when the initial response to an operation included an OTP_REQUIRED error and explicitly indicated that the resend capability is allowed. To enable this capability, your integration must return the resend flag and a valid operationId in the OTP_REQUIRED response, as shown below.

Example — OTP_REQUIRED response with resend support

{
  "data": {
    "requestId": "req-1234567890abcdef",
    "operationId": "op-1234567890abcdef",
    "resend": true
  },
  "code": "OTP_REQUIRED",
  "errorSeverity": "ERROR",
  "message": "In order to confirm a trusted beneficiary and OTP is required",
  "httpStatus": 422,
  "requestId": "req-abcdef1234567890",
  "date": "2025-04-02T08:03:09.883Z",
  "errorOrigin": "your-integration"
}