Skip to navigation

PII inquiry with OTP: submit by transaction

View as Markdown

Runs the PII inquiry against the ID images of an existing transaction, with phone-number ownership proven by a one-time password.

Call POST /api/FRAServices/RequestOtpForPii first to send the code and get an otpRequestId, then send it here together with the otpCode the user received.

Same URL as the no-OTP variant — the only difference is that otpRequestId and otpCode are present. They travel together: send both, or send neither and use the no-OTP variant.

Authentication

ApiKeystring
Static API key issued to your tenant. Required on every request.
OR
AuthorizationBearer

End-user JWT from registration or login. Required for verification, signing, and user-scoped operations.

Request

This endpoint expects an object.
phoneNumberstringRequired
The phone number being validated.
otpRequestIdstringRequiredformat: "uuid"

The otpRequestId returned by POST /api/FRAServices/RequestOtpForPii.

transactionIdstringRequiredformat: "uuid"
The transaction whose ID front and back were already processed.
otpCodeintegerRequired

The OTP the user received, sent as a JSON number (123456), not a string.

Response

PII inquiry result.
dataobjectOptional
error_codeinteger or nullOptional
error_messagestring or nullOptional
error_descriptionslist of strings or nullOptional

Errors

400
Bad Request Error