Verification: what the clauses actually say

«No KYC» is one of the most-searched phrases in this subject and not one of the 12 records in this register makes the claim. Every one of them reserves the right to ask for documents, and several say so in two separate chapters. That is worth stating plainly at the top of the page, because a site that measured what it wished were true would have a much shorter table. The newest entries, dated by certificate.

What varies is the shape of the promise, not its presence. Some clauses name a point at which a check starts. Some name a deadline for sending documents once asked. Most name neither, and say only that documents may be requested at any time — which is a sentence that cannot be planned around at all. Roulette, counted pocket by pocket.

A figure inside the clause — an amount, a number of days, a threshold — is the only thing on a whole record that lets a reader decide anything in advance. It carries six of the small-print block's twenty points for that reason, and the records that have one are worth reading side by side because no two of them measure the same thing. Bitcasino.io: what is written down.

The clauses in the table differ in when and how much they bind, but what they ask for is remarkably consistent across all twelve: something that proves who you are, something that proves where you live, and — less often, and usually later — something that shows where the money came from. None of that is specific to crypto. It is the ordinary shape of the obligation the licence itself imposes on the operator.

1. 01
   IdentityA government document with a photograph. This is the one almost every clause names explicitly and the one most likely to be asked for first.
2. 02
   AddressUsually a recent utility bill or bank statement carrying the same name. The requirement that it be recent is the part that catches people out, and the number of months is exactly the kind of figure most of these clauses do not give.
3. 03
   Source of fundsThe least common and the slowest, because it is a question about a history rather than a document. Clauses that mention it at all usually attach it to a threshold rather than to every account.

The practical consequence is worth stating once. A check is not an event that happens to suspicious accounts; it is a condition the operator has agreed to be able to perform. The useful question is therefore never whether it will happen, but whether the terms say in advance what will set it off — which is precisely the field this page scores.

The idea that depositing in crypto avoids verification comes from a real property: a transfer needs no bank and no card, so nobody at the payment end asks for a name. That is true of the transfer and false of the account. The obligation sits on the operator, not on the rails, and the operator applies it at the account — which is why one clause in this register names bitcoin players outright and asks for identification before the first bet rather than after the first withdrawal.

The direction of travel is worth noticing too. A deposit in a coin that arrives without a name still has to leave somewhere, and a withdrawal is the moment almost every clause here attaches itself to. A route that is anonymous on the way in and documented on the way out is not an anonymous route; it is a documented one with a quiet beginning.

A clause with a section number can be reopened by anybody. A clause without one has to be found by reading the whole document, which means in practice that nobody checks it and the summary on some listing becomes the record. That is a filing problem rather than a substantive one, and this register still charges for it: a reader who cannot verify a quotation is being asked to take it on trust. Each clause is repeated on its own record in the register, beside the licence number it belongs to.