400

API problem detail

Review Confirmation Required

Description

This problem happens when $Verify or $VerifyAndSend is called with an explicit reviewConfirmed: false. The field records that the approver reviewed the amount, funding source, recipient, account, and delivery method; a request that explicitly denies that review is refused and no money moves. Omitting the field is treated as confirmation, so existing integrations that never send it are unaffected. On the wire the refusal carries the generic BadRequest problem type with the title Review Confirmation Required and errorCode REVIEW_CONFIRMATION_REQUIRED. Match on the errorCode.

Response errorCode: REVIEW_CONFIRMATION_REQUIRED.

Experience API error bodies also carry errorCode, resolution, and traceId. Branch on errorCode, not on title or detail; see fields on every error.

How to resolve

Have the approver complete their review, then repeat the action with reviewConfirmed: true (or omit the field). Do not automate the approval decision itself; when the company's approval strategy requires a separate approver, the approver must be a different user from the requester.
Back to all problem details