Skip to main content
POST
Validate an intelligence evaluation request

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

Optional. If both this header and body idempotency_key are supplied, the header wins during validation mapping.

Maximum string length: 255

Body

application/json
use_case
enum<string>
required
Available options:
payee_registration,
instrument_screening,
payout_screening,
merchant_onboarding,
monitoring
entity
object
required
client_reference_id
string

Client-supplied reference for reconciliation. Not used for merchant scoping.

idempotency_key
string

Body fallback for testing. Prefer the Idempotency-Key header.

instrument
object
payout
object
merchant
object

Accepted for future compatibility but ignored on the public test endpoint.

context
object

Response

Request is valid and can be mapped to an internal event.

data
object
required