Screening decisions
Every payment carries exactly one screening decision — retrievable, displayable, auditable.
A screening decision (oz_scr_) is attached to every payment when Sirius Core completes its evaluation. It is a permanent object: retrieve it at any time, including years later for an audit.
curl https://api.onzo.la/v1/payments/oz_pay_8f2c41/screening \
-H "Authorization: Bearer oz_sk_..."
json Response
{
"id": "oz_scr_c91b02",
"payment": "oz_pay_8f2c41",
"outcome": "cleared",
"checks": [
{ "type": "sanctions", "result": "clear", "lists_version": "2026-07-03T12:00Z" },
{ "type": "pep", "result": "clear" },
{ "type": "risk_score", "result": "pass", "threshold": "corridor:CL-US" }
],
"decided_at": "2026-07-03T14:02:13Z",
"latency_ms": 41
}
Outcomes
| Outcome | Meaning |
|---|---|
cleared |
All checks passed — payment proceeds to settlement |
held |
One or more checks require human review — funds do not move |
declined |
A check failed definitively — funds never move |
Why this exists as an API
Most platforms treat compliance as internal machinery. Onzo exposes it because our customers need it: your operations team can see why a payment was held, your compliance officer can pull the decision trail for any transaction, and your auditors get evidence instead of assurances.