KYC
In productionIdentity checks run on your rules.
Versioned KYC policies per licence, with levels, triggers, deadlines and a review queue that needs a second person for the sensitive cases, plus an encrypted evidence vault that is in pilot.
What it does
A policy per licence
Up to six levels per policy, each saying what the player may do: play, deposit, withdraw or take bonuses, and up to which amount. Publishing a policy needs a second person.
Triggers that open cases
Twenty-one events can open a case with a deadline: deposits, withdrawals, net loss, a new payment method, a profile change, an expiring document, an AML result and more.
Review with four eyes
No approval without the evidence opened first. PEP matches, the highest levels, register matches and manual approvals at a real-money operator need a second reviewer.
- In pilot
An evidence vault
Envelope encryption per operator and per file, watermarked one-time views, retention per country, legal hold, and keys destroyed when the retention ends.
Thirteen jurisdiction templates
Starting policies for Latin America, Nigeria, Curaçao, Malta, Spain, the UK and the EU rules of 2027. A published policy can never ask for less than its template.
- Coming soon
Automatic document, face and liveness checks
Our own engine for reading documents, matching faces and checking liveness is built and not yet deployed. Until it is, those steps cannot be published in a policy.
By the numbers
Levels per policy
Up to 6
Trigger events
21
Jurisdiction templates
13
starting points, to be validated by counsel
Details
A policy engine, not a form
Each policy holds levels, steps and rules by threshold and by event, the minimum age, the documents accepted and how long evidence is kept, per country. Thresholds written in legal units, such as Mexican UMA, are converted for each year.
A simulator shows what a policy would ask of a given player before it is published.
Decisions a regulator can follow
Every decision carries a coded reason. A reviewer cannot approve without the evidence submitted and opened in the vault, and every view is logged. The same person can never be both reviewers: the database refuses it.
Automatic approval is off by default and refused for operators with real money, both when a policy is published and when a case is decided. Nothing is rejected automatically.
Evidence handled like money
A master key wraps one key per operator, which wraps one key per file, all with AES-256-GCM bound to their place: moving a file to another operator or changing one byte breaks it. Files leave the vault only decrypted in memory, watermarked, through a one-use token.
When the retention set by the policy ends, the file key is destroyed and a tombstone remains.
What is not there yet
Document upload and the evidence vault are deployed and stay closed until the platform's vault key is installed. The engine for document reading, forgery checks, face matching and liveness is not deployed, and its liveness check is not certified.
Checks against official registers are a manual attestation with a capture, and no third-party KYC provider is connected today.
Contact
Tell us what you are building.
Markets, brands, verticals. We show you the platform with your case in mind.