Re-screen a Beneficiary
Queue a fresh check of an active beneficiary. Asynchronous: responds
202 immediately. The beneficiary may become unavailable for payouts
(blocked, with the beneficiary.blocked webhook event); otherwise
nothing changes. Both the request and its outcome are audited.
Not the same as POST /v1/beneficiaries/{id}/rescore, which
recomputes the engine risk score.
Requires an Idempotency-Key header.
Authorizations
Per-request DPoP proof JWT (RFC 9449). MUST accompany the Authorization: DPoP <access_token> header on every protected operation. The proof is signed by the merchant's private DPoP key and carries htm, htu, iat, jti, and ath claims.
Headers
Unique key identifying this operation. Sending the same key twice returns the original response instead of creating a duplicate. Keys are retained for 24 hours.
255Path Parameters
^ben_[a-zA-Z0-9]+$Response
Screening queued.