Trust Center
What actually backs a match on Izenzo.
Not marketing claims — the specific mechanisms every match runs through, and what they do and don't guarantee.
Hash-sealed, tamper-evident
Critical transitions — the bid terms, the Proof of Intent, WaD clearance, the Finality record — are sealed with a SHA-256 hash of their state. Anyone holding the original hash can detect if the underlying record changed after the fact.
A compliance gate that can't be waived
Every match runs a WaD case — identity, ownership (UBO), sanctions and PEP screening — before it can leave the Compliance Gate. There is no admin override that skips this; it costs 3 tokens and clears, or the match doesn't proceed to Execution.
Background screening before sealing
A Proof of Intent can't be sealed until the transaction has run its Social & News Media scan — LinkedIn, Facebook, TikTok, marketplaces and news, screened for signals on the deal and its parties.
Counterparty ratings, not blind trust
Counterparties are rated trusted, neutral, or flagged, with a computed score and a written rationale — visible across the matches they're surfaced in, not locked to one transaction.
The audit trail
Every step recorded, in order, with no way around it.
Every stage transition is an event
Bid/Offer, Proof of Intent, WaD clearance, Execution milestones, Finality, and Memory are each recorded as a transaction_event — actor, timestamp, and stage/step — building an append-only audit trail per transaction.
Nothing skips the sequence
A transaction cannot jump from Trading into Execution, Finality, or Memory without a sealed Proof of Intent and a completed WaD case first — enforced by the state machine itself, not by process convention.
Questions about a specific match, screening result, or record? Contact support.