ORDiN inserts a runtime authority check before sensitive actions commit. It returns PERMITTED, DENIED, or STEP-UP REQUIRED, emits an AuthorityReceipt, and leaves enforcement local to the customer.
Execution only happens after judgment.
Identity proves the actor. Access opens the door. Wallet policy signs the transaction. ORDiN checks whether the action should happen now.
Integrate at your execution points. Get standardized decisions. Enforce locally before commit.
Receive actor, action, context, policy, and evidence at the point where a sensitive action is about to commit.
npm install @ordin/protocol
Your system calls ordin.authorize() with the action, amount, context, policy, and evidence. No unnecessary identity data leaves your environment.
const decision = await ordin.authorize({
action: 'transfer.execute',
amount: 4200
})
ORDiN runs the runtime authority check and returns PERMITTED, DENIED, or STEP-UP REQUIRED.
Decision is external. Enforcement stays in your environment.
ORDiN emits an AuthorityReceipt tied to the action, decision, policy context, and time window.
Your system enforces locally before commit. ORDiN gives judgment; the customer keeps execution control.
ORDiN starts in hybrid financial infrastructure: treasury movements, settlement steps, cross-system transfers, and other irreversible value-moving actions. Old approval should not move new money.
AuthorityReceipt returned. Your system executes the transfer locally. ORDiN gives judgment but never holds funds.
Signed DENIED receipt. Action is rejected before execution. No funds move. Decision is auditable for regulators and the operator.
ORDiN requests fresh evidence before the original action re-evaluates against current conditions.
Not all decisions are equal. A simple credential check is lighter than a multi-factor regulated approval. Pricing reflects the shape of the decision — more clauses, more credentials, more sensitivity = higher tier. Decisions are measured in Standard Decision Units (SDUs) — 1 SDU ≈ $0.01 of usage value, benchmarked to a standard execution-time authorization.
Single-purpose, low-risk, deterministic gates. One or two simple rules evaluated against a single credential. Sub-10ms decisions. High volume, low weight.
Usage pools typically consume 1 SDU per decision at this tier.
Two to five policy rules. Amount bands, jurisdiction checks, time-window gates. The working tier for most production workloads.
~2–5 SDUs per decision.
Five to ten policy clauses. Conditional logic, step-up branching, multiple credentials combined. For institutional and multi-party use cases.
~6–10 SDUs per decision.
Advanced, regulated, high-assurance policy. Dense logic, bespoke tuning, compliance-aligned rule sets for enterprises in regulated markets.
~11–25 SDUs per decision. Custom tuning available.
Core decision fee plus external vendor pass-through plus workflow premium. When a decision needs more than ORDiN alone — a sanctions refresh, KYT pull, or live re-verification.
Tier-3 core fee plus pass-through cost of the external workflow plus orchestration premium.
Toggle the characteristics that apply to your use case. The score determines which pricing tier your decisions fall into.
Your monthly commitment isn't a platform fee — it's a prepaid usage block measured in Standard Decision Units (SDUs). Simpler decisions consume less. Heavier decisions consume more. You're not paying for access. You're paying for decisions.