The TrustStack ORION user manual.
A practical guide for operators, analysts, merchant admins and integrators — organized around five apps and fourteen registered modules, with observed surfaces separated from target workflows.
Who this manual is for
TrustStack is designed for merchant teams working in their own tenant and provider-side compliance operations working across tenants. Navigation visibility depends on role, entitlement, feature flags and configuration; a screen shown in this manual may therefore be absent or read-only in a particular environment.
How the platform is organized
The reviewed registry contains fourteen modules in three rings. Core — GATE, PULSE, SWITCH, LEDGER, SENTINEL, PRISM — and Add-ons — STUDIO, TRAVEL, AURA, MoR — are sellable entitlements. Platform — DOCKET, VAULT, HELM, FORGE — is registered as always_on fabric, but access remains role- and configuration-dependent. Registry status ui confirms an interface or read surface, not general availability or completeness.
Modules are designed to connect five apps: the Compliance Console, Client & Onboarding Portal, Developer Portal, Evidence Portal and Admin Console. An app is an audience; a module is a capability. A screening result may hand work to a DOCKET case and reference VAULT evidence when the relevant integrations, fields and access controls are configured.
The one idea to keep
A Decision Record is designed to connect an outcome with the context the producing workflow actually recorded: rules, thresholds, inputs, versions, correlation and review events where applicable. Missing fields must read Not recorded by engine or Not applicable. Evidence export is available only on supported, configured surfaces; it is not proof that every event or document was captured.
Conventions used here
- Screen paths are written as App → Section → Screen, e.g. Compliance Console → Cases → Case detail.
- Module names are set in capitals (GATE, PULSE); the same names appear in navigation, entitlements and audit events.
- Numbered procedures describe intended product paths; confirm the deployed version, entitlement and feature flag before treating them as exact instructions.
- Callouts flag audit-relevant behavior — things a reviewer or examiner will later look at.
Getting started
From scoping to a bounded first decision exercise: delivery models, entitlements, setup, validation and operating cadence.
02The five apps
Compliance Console, Client & Onboarding Portal, Developer Portal, Evidence Portal, Admin Console — who uses which app and for what.
03GATE — Verify
Observed hosted KYC and party surfaces, with designed tiering, screening, review and re-verification workflows; current UBO and review limitations apply.
04PULSE — Risk
The observed decision explorer for rules-first risk decisions; rationale is partial and the current ML indicator is a stub.
05SWITCH — Payments
Partial routing-configuration and payment-path read surfaces; live processor connectivity, automated failover and production resilience are not established by the reviewed status.
06LEDGER — Tax & Finance
Observed tax and ledger read surfaces with static rate tables in the reviewed context; tax outcomes, filings and ledger integrity require scoped validation.
07SENTINEL — Policy
Observed screening and policy surfaces with a labelled demonstration list; provider coverage, lifecycle actions and maker-checker are configuration-dependent.
08PRISM — Insights
Observed dashboard and generate-now scorecard surfaces; scheduled reporting, SLA monitoring and report completeness are not established by the current status.
09Add-ons — STUDIO, TRAVEL, AURA, MoR
Conditional add-on read surfaces for content moderation, travel rule, coverage and merchant-of-record; entitlement is only one of several required gates.
10Platform ring — DOCKET, VAULT, HELM, FORGE
The registry's always_on platform fabric: role-gated case, evidence, administration and developer surfaces with workflow-specific coverage.
11Evidence & the audit trail
Decision Record and evidence concepts, observed bounded read/export surfaces, verification limits and conditional external-review access.
12The scenario universe
What the interactive scenarios on e-kmc.io demonstrate, which fixtures they use, and what they deliberately do not prove.
13Glossary
The platform vocabulary: Decision Record, evidence pack, maker-checker, entitlement, tenant, and the rest.
Want the complete manual as a PDF? Leave us your email and we'll send it over.
Request the manual