Client Identity Verification in IZI
Client Identity Verification in IZI
Section titled “Client Identity Verification in IZI”Client identification in IZI is primarily phone-based with OTP confirmation. This is the base level: the client is verified as the owner of that number. Extended identity verification (document, age, KYC) is an additional layer that each club builds based on jurisdiction requirements and internal policy.
Important: requirements for identifying club clients vary by country. This page describes IZI’s technical capabilities and general practices. For legally binding conclusions, consult a lawyer in your jurisdiction.
Base Identification: Phone + OTP
Section titled “Base Identification: Phone + OTP”Standard flow in IZI: the administrator enters the phone number → the client receives an OTP → enters the code → a profile is created. This confirms that the phone belongs to the client at the time of registration.
What this provides:
- Unique client identification in the database (one number = one profile)
- Session history tied to the account
- Bonus balance is not lost if the device changes
- Account recovery by phone number
What this does not provide: confirmation of identity, age, or nationality. The phone may belong to someone else.
More on the registration procedure: Register a Client by Phone in IZI.
Extended Verification: Documents and Age
Section titled “Extended Verification: Documents and Age”Gaming clubs in some regions are required or choose to verify a document at registration. Typical scenarios:
Age verification. If the club has set an age threshold (14+, 16+, 18+) — the administrator visually assesses or requests ID from clients who appear younger than the threshold. More details: Age Restrictions in IZI.
Visitor registration. Some jurisdictions require recording visitor data (name, document, visit time). This may be a license or regulatory requirement.
Corporate contracts. If the club works with corporate clients, verifying the company representative may be part of the contract process.
What Data IZI Records
Section titled “What Data IZI Records”Standard client profile contains:
| Field | Required | Used for |
|---|---|---|
| Name | Yes | Identification, search, address |
| Phone | Yes (for registered clients) | OTP, unique account key |
| No | Notifications | |
| Date of Birth | No | Age control, birthday bonuses |
| Note | No | Admin service annotations |
Storing document scans is not available in standard IZI functionality. If local requirements mandate keeping copies — set up an external secure storage and enter only the document ID and verification fact in the Note field, without the scan itself.
How to Record Verification in CRM
Section titled “How to Record Verification in CRM”Via Date of Birth
Section titled “Via Date of Birth”If the client presented a document with their date of birth at registration — enter it in the profile. This provides:
- Automatic age display in the profile
- Basis for age control
- Data for birthday promotions if the program is configured
Via Admin Note
Section titled “Via Admin Note”The Note field in the client profile is for internal use, visible only to staff. Used for audit trail without storing the document itself:
Passport verified 2026-05-31, admin Smithor
Document not presented, appears 20+, admittedThe note is not included in client exports and is not visible to the client.
Via Client Groups
Section titled “Via Client Groups”For clubs with multi-level verification, groups can be created: “Document Verified”, “Minor”, “Corporate”. A group affects client tariffs and automation rules — more on client groups.
Which Documents to Accept
Section titled “Which Documents to Accept”Standard minimum for age verification:
- National passport
- Student card with date of birth
- Driver’s license
- Any government-issued document with photo and date of birth
Accepting specific document types is the club’s decision and jurisdiction-dependent. In the UAE: Emirates ID and passport. In Russia: passport; for minors — birth certificate. In the EU: national ID or passport.
Document the accepted document policy in the club’s internal regulations — this simplifies staff operations and reduces dispute risk.
Personal Data Storage
Section titled “Personal Data Storage”Client data in IZI is stored in IZI’s cloud. The retention policy is described in the IZI service agreement.
Additional considerations for the club:
- Collect only data that is actually needed
- If the jurisdiction requires the ability to delete client data — this is handled through an IZI support request
- Do not store document scans in CRM unless there is a secure cloud storage for personal data
- Date of birth is sensitive data; restrict profile access by role
For full compliance with GDPR, Federal Law 152-FZ, or PDPL — consult a lawyer in your jurisdiction. This is an area where requirements differ significantly and change frequently.
Protocol for Document Refusal
Section titled “Protocol for Document Refusal”There is no single correct procedure — it is defined by club policy. Recommended approach:
- Politely explain the club’s requirement
- Offer alternatives if available (e.g., areas without age restriction)
- If refused — do not serve and log in the journal
- Do not create a client profile without fulfilling the club’s mandatory requirements
If the incident involves a minor — see Age Restrictions in IZI.
Verifying Existing Clients
Section titled “Verifying Existing Clients”For already registered clients without a date of birth:
- Open the client profile
- Click Edit
- Add the date of birth and a document check note if needed
- Save
Profile edits are recorded in client history with the administrator’s name.
See Also
Section titled “See Also”Frequently asked questions
Is client identity verification mandatory at a gaming club?
Depends on jurisdiction and club operating model. Most countries do not require gaming clubs to conduct KYC at the level of banks or casinos. However, age control requirements — and in some regions, visitor registration — may be established by law. Consult a lawyer in your jurisdiction.
Does IZI store copies of client documents?
A standard IZI client profile stores name, phone, email, date of birth, and admin notes. Storing document scans or photos is not available in standard functionality. If local law requires it — set up an external secure storage and record only the document ID in the note field.
How do I record an age check in CRM?
Via the Date of Birth field in the client profile or via an admin note. If the club requires mandatory document verification at registration — add a note that the document was checked and when. This creates an audit trail without storing the document itself.
Is ID required for every new client?
Depends on club policy and your jurisdiction's requirements. Minimum practice: age check for clients who appear younger than the club's age threshold. Stricter: document check for all visibly underage clients. Maximum: document at every registration.
A client refuses to show ID — what to do?
This is governed by club policy, not IZI. Standard practice: if the client appears younger than the restriction and refuses to show ID — refuse service. Log the refusal in the journal or in the profile note if an account exists.
How to handle client personal data in compliance with GDPR / data protection laws?
Rules depend on jurisdiction: GDPR (EU), Federal Law 152-FZ (Russia, personal data law), PDPL (UAE), and others. General principle: collect only necessary data, retain no longer than needed, ensure right to deletion. Specific requirements — consult a lawyer in your country.