Compliance infrastructure
for regulated venues.
MiCA authorisation, the Travel Rule, and sanctions obligations all assume one thing: controls that run on every deposit, withdrawal, and counterparty — and records that prove they ran.
The obligations of an authorised venue
Screening at transaction scale
Every deposit, withdrawal, and counterparty address must be screened against sanctions lists. Manual checks do not scale past a few hundred customers.
Monitoring after onboarding
A one-time check at onboarding is not sufficient — addresses acquire sanctions flags and risk after the fact, and supervisors expect ongoing surveillance.
Records for the supervisor
Authorisation brings inspection. Timestamped, verifiable logs of every check are the difference between demonstrating compliance and asserting it.
Travel Rule data exchange
Regulation 2023/1113 requires originator and beneficiary information to travel with transfers. That is an operational data-exchange obligation, not a policy document.
What the platform provides
Screening API
Screen addresses at deposit and withdrawal with explicit ACCEPT / REVIEW / REJECT verdicts, scores, and request IDs your systems can act on.
Attribution, not just a flag
Deposit-address clustering names the venue to approach, and exposure to mixers, sanctioned addresses, and known fraud is surfaced as typologies an analyst can act on.
Continuous KYT monitoring
Customer addresses under continuous monitoring, with webhook alerts when risk scores change, new intelligence appears, or sanctions flags are added.
Dashboards and reporting
A central view of screening activity, flagged addresses, and risk distribution, with periodic PDF reports for your compliance officer.
Roles and audit trail
Admin, Member, and Viewer roles with a complete record of who checked what, when, and what action was taken.
Travel Rule (IVMS101)
Originator and beneficiary exchange for Regulation 2023/1113, built into the platform. Send and receive over the open Travel Rule Protocol; commercial networks connect as they open.
From evaluation to production
Evaluate in the sandbox
Engineers validate coverage, latency, and verdict semantics against the live API the same day — no procurement required to begin.
Pilot on monthly terms
Run production traffic under month-to-month terms while internal review and procurement complete.
Move to an enterprise agreement
Negotiated volume, a contractual SLA, self-hosted or EU-resident deployment, and a data processing agreement for vendor due diligence.
Screening at venue scale, on the record.
Plans from €99 per month with enterprise agreements for SLA and negotiated volume. Brief us on your flows and counterparties and we will scope the integration.