Validate a transaction
Use this endpoint to check a transaction against your active rules and the applicable spending limits in real time. Returns a decision (ALLOW, DENY, or REVIEW) along with details about which rules matched and the usage each limit would reach. A DENY or REVIEW by the rules decides. An ALLOW is checked against each applicable limit, and an amount that would take a limit past its maximum answers DENY with the reason limit_exceeded. This call only reads: no limit counter moves and nothing is reserved. Only the ledger’s transaction reserve consumes a limit. A requestId already used with the same body returns the decision stored for it. A different body, or a requestId first used on POST /v1/validations/rules-only, answers 409 (code 0084).
Autorizaciones
JWT bearer token issued by the identity provider.
Cuerpo
"100.00"
"USD"
"00000000-0000-0000-0000-000000000000"
"2021-01-01T00:00:00Z"
Payment scheme, required unless the deprecated transactionType is sent: 1 to 50 characters of A-Z, 0-9, _ or - after trimming and upper-casing.
50"PIX"
Sub type, at most 50 bytes after trimming; stored lower-cased and matched case-insensitively.
50"purchase"
Deprecated: use scheme. Same value under its former name; when both are sent they must match.
50"PIX"
Respuesta
OK
"ALLOW"
"2021-01-01T00:00:00Z"
12.5
"Transaction denied by rule 'Block high-value checking transactions'"
"00000000-0000-0000-0000-000000000000"
42
false
"00000000-0000-0000-0000-000000000000"

