Use this endpoint to validate a transaction against configured rules and limits in real-time. Returns a decision (ALLOW, DENY, or REVIEW) along with details about which rules matched and limit usage. Performance target is under 80ms (p99).
The type of media of the resource. Must be application/json.
The API Key for authentication. This header is required for all endpoints except health checks.
A unique identifier used to trace and track each request.
Transaction validation request. All context required for validation must be included (Payload-Complete Pattern).
Client-generated unique ID for idempotency and audit trail correlation.
Type of transaction (payment method).
CARD, WIRE, PIX, CRYPTO Transaction amount in cents (smallest currency unit). Must be positive integer.
x >= 1ISO 4217 currency code (uppercase). Lowercase codes are rejected.
3Transaction timestamp in RFC3339 format with timezone.
Account context for validation.
Transaction subtype for additional context (e.g., debit, credit, prepaid).
50Segment context (optional). If provided, segmentId is required.
Portfolio context (optional). If provided, portfolioId is required.
Merchant context (optional, recommended for card transactions). If provided, merchantId is required.
Custom key-value pairs for rule expressions.
Indicates that the validation was processed successfully and returns the decision.
Transaction validation result.
Echo of the client-provided request identifier.
Server-generated unique identifier for this validation record.
Validation decision (ALLOW, DENY, or REVIEW).
ALLOW, DENY, REVIEW Human-readable reason for the decision.
IDs of rules that matched and triggered the decision.
IDs of all rules that were evaluated.
Details about each limit checked during validation.
Processing time in milliseconds (target < 80ms p99).
Total number of rules loaded for evaluation.
Whether the response was truncated due to size limits.