Skip to main content
POST
Record a decision

Authorizations

DPoP
string
header
required

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

Idempotency-Key
string
required

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.

Maximum string length: 255

Path Parameters

id
string
required

Review ID.

Pattern: ^irv_[a-zA-Z0-9]+$

Body

application/json
decision
enum<string>
required

The first five are decisions you can record through this API. release and cancel are votes on a payout your rule held, and approved, rejected and expired are how such a review can close; both are made in the portal.

Available options:
waiting_on_customer,
not_a_match,
confirmed_match,
no_concern,
concern_confirmed,
release,
cancel,
approved,
rejected,
expired
reason_code
enum<string>
required

Accepted per decision: waiting_on_customer — dob_needed, id_document_needed, more_information_needed; not_a_match — dob_differs, nationality_differs, id_document_verified, different_entity_type, location_differs; confirmed_match — identity_confirmed, exact_identifier_match, customer_confirmed; no_concern — activity_explained, documents_verified; concern_confirmed — suspicious_activity, policy_breach; other with any decision.

Available options:
dob_needed,
id_document_needed,
more_information_needed,
dob_differs,
nationality_differs,
id_document_verified,
different_entity_type,
location_differs,
identity_confirmed,
exact_identifier_match,
customer_confirmed,
activity_explained,
documents_verified,
suspicious_activity,
policy_breach,
other
note
string

Stored in a vault; never returned by the API.

Maximum string length: 2000

Response

The decision and the review after it.

data
object
required