Product engine
Compliance
Compliance is an engine in the stack, not a bolt-on, and it runs inline before money moves. It verifies parties, screens transactions and counterparties against the lists and providers you connect, applies the travel-rule and risk rules you set, and gives your team the cases and reports they need, all on the same ledger as the rest of the stack.
What it includes
- KYC and KYB verification across the tiers you define.
- Transaction screening on the flows you select.
- Travel-rule compliance for the scope you set.
- Sanctions screening against your chosen lists.
- Case management for review and disposition.
- Regulatory reporting across the report types you need.
- A risk-scoring engine with configurable thresholds.
On one ledger with the rest of the stack
Because the gate sits before the rail, a sanctioned or blocked party is stopped at the decision point: no partner connector is ever called, so nothing leaves the operator. A block here is not a flag written to a report after the fact. It becomes ledger state, a freeze recorded against the party and its funds, that every other engine sees and honours on the next attempt to move that money.
The cases your team opens and the regulatory filings they produce read from those same postings, so a disposition, the screening hit that triggered it, and the held balance it concerns are one record on one ledger, not three figures stitched together from separate systems at filing time.