Evaluate transaction
Send a decision for evaluation and receive an ALLOW, REVIEW, or BLOCK response on synchronous rules.
If an asynchronous rule (e.g. based on a backend) is involved, a PROVISIONAL response with later update is possible.
Authorizations
HS256-signed JWT bearer token, obtained via the OAuth2 client-credentials grant (see Authentication).
Body
Decision request
Airline / travel industry data. Present only for airline transactions.
Provider-specific passthrough fields keyed by backend identifier. Not persisted.
{
"sift": { "$site_domain": "shop.example.com" }
}Billing address for the transaction
Ruleset context key. Defaults to "default" if omitted.
"checkout"
Cart / order line items
Flat key-value pairs stored alongside the decision. Available to rules. Not sent to backends.
{
"campaign": "spring_2026",
"channel": "web"
}Shipping address for the transaction
Response
Decision result
Result of evaluating a transaction against the active ruleset.
Unique decision identifier
One entry per backend rule that was executed.
"checkout"
Deterministic HMAC-SHA256 card instrument identifier
"crd_4ba218..."
Type of credential supplied in the request
pan, masked_pan, sepa BLOCK terminates on first match. REVIEW accumulates. ALLOW is the default when no rules match.
ALLOW, BLOCK, REVIEW, PROVISIONAL Always empty on a freshly evaluated decision.
True if any backend_results entry carries a non-nil error (e.g. "backend_capability_disabled").
Integration type that originated this decision (e.g. 'interceptor')
ID of the interceptor that originated this decision
4250
Display-safe masked representation, e.g. '411111 ****** 4242'
"411111 ****** 4242"
Merchant-supplied key-value pairs stored with the decision.
Always null on a freshly evaluated decision.
RULE_ENGINE — condition rules only. BACKEND — backend rule(s) only. COMBINED — both.
RULE_ENGINE, BACKEND, COMBINED