...

Verifying users of SaaS platforms

A company account in your service holds its customers, contracts and employee access. NeuroVision checks the customer company by INN before the contract, the account owner — by document and Liveness when rights are issued and when the administrator changes, and partners and bug bounty researchers — before payout.

Result of the account owner check before rights are issued: company, passport, Liveness and a match with the director
99,9 % Liveness accuracy
5 ₽ check of a company or a person against one register
195+ countries and territories — documents without manual entry
from 29 ₽ per "Document + liveness" session
Company by tax number Document Liveness Administrator change Self-employed Sanctions lists

Owner rights go to the person the company appointed · Federal Law 152‑FZ · cloud or your perimeter

Sign-in without foreign accounts, data processing on behalf of a customer and leaks: which rules apply to a SaaS platform

There is no law that obliges a SaaS to check a customer’s passport. But the law sets how users may be let in and makes the platform responsible for the data customers entrusted to it. The better the account owner is known, the lower the chance that this data leaves through them.

  • User sign-in

    149‑FZ, part 10 of Art. 8; Code of Administrative Offences, Art. 13.55 (from 7 July 2026).

    What the platform risks

    Permitted methods

    • If access is open only after authorisation, users located in Russia are authorised by a mobile operator number, through Gosuslugi, the EBS or another Russian system
    • The obligation lies with the owner of the website, app or information system

    Whose sign-in system

    • Another sign-in system is acceptable if its owner is a Russian citizen with no other citizenship or a Russian company controlled by Russia or its citizens
    • This also applies to corporate sign-in for a customer’s employees

    What the law does not contain

    • The law does not require checking the user’s document
    • The sign-in method confirms a number or an account, but not who is sitting behind a company account
  • Customer data in your service

    152‑FZ, parts 3 and 5 of Art. 6, part 5 of Art. 18, part 3.1 of Art. 21.

    Checklist of checks

    Processing on behalf of a customer

    • If a customer company entrusts the platform with processing the data of its own customers and employees, the operator is the company, and the platform processes the data on its instruction
    • The instruction sets out the list of data, the actions, the purposes, the security requirements and the obligation to report leaks to the operator

    Storage in Russia

    • Personal data of Russian citizens is recorded and stored in databases located in Russia

    A leak

    • The operator notifies Roskomnadzor of a leak: within 24 hours — of the incident and its causes, within 72 hours — of the results of the internal investigation
  • Administrators’ data and liability

    152‑FZ, part 1 of Art. 9 (as amended by 156‑FZ), part 1 of Art. 11; 572‑FZ, Art. 15; Code of Administrative Offences, Art. 13.11.

    How to verify an administrator

    Consent

    • Consent to the processing of personal data is drawn up separately from the offer and other documents
    • Biometric data — information used to establish identity — is processed only with written consent

    No face sign-in

    • Biometric authentication by organisations — only through the EBS
    • Liveness at an administrator change checks live presence and matches the selfie with the photo in the document; it does not replace a password

    Fines for a leak

    • Since 30 May 2025 a leak costs an operator that is an organisation from 3 to 15 million ₽ depending on the number of people affected, and a repeat leak — from 1 to 3 % of revenue
    • Failing to notify Roskomnadzor — a further 1 to 3 million ₽

CRM, data rooms, APIs, partner programmes and bug bounty: where a SaaS needs identity checks

There is no need to check everyone who opened a trial. Verifying users is needed where the platform gives rights over a company’s data, opens deferred payment or transfers money.

  • CRM, accounting and HR services

    • The account holds the customer base, deals, salaries and employee documents
    • Company by tax number — before the contract and deferred payment
    • The account owner — document and Liveness when rights are issued and when the administrator changes
  • Virtual data rooms and corporate storage

    • Deal documents are seen by lawyers, auditors and investors of the parties
    • Every external participant — document and Liveness before the folder opens
    • The participating company — by INN and sanctions lists
  • Developer services and API platforms

    • A corporate plan, higher limits, payment by invoice
    • The company by INN, its director and founders — before onboarding
    • The representative who receives the keys — document and Liveness
  • Scraping APIs and data-collection services

    • Mass requests on a customer’s behalf are a reason for complaints against the platform
    • Corporate plan — company by INN, director and founders before connection
    • API keys go to a representative — document and Liveness; trial farms — anti-fraud
  • App marketplaces and partner programmes

    • 1C integrators, resellers and extension authors receive payouts and access to customers
    • A company — by INN, an individual — passport and Liveness before publication
    • Self-employed status and sanctions lists — before payout
  • Bug bounty and reward programmes

    • A researcher gets access to a test environment and a reward for a report
    • Passport and Liveness — before admission to a private programme
    • INN and self-employed status — before payout

Account owner rights in three steps: the company by INN, the administrator’s document and Liveness

Verifying the account administrator is built into the step where a company receives owner rights, a corporate plan or deferred payment. The person completes it from a phone or computer, without visiting an office.

Step 1

Company by tax number

The platform sends the INN from the application. The response contains the company’s status, its director and founders from the registers, and sanctions lists. Liquidation, signs of a shell company or a list match are visible before the contract and deferred payment.

Checking a SaaS customer company by INN: status, director and sanctions lists
Step 2

The administrator’s document and Liveness

The future account owner photographs their passport; the full name and date of birth arrive as fields without manual entry, and anti-fraud flags a photo of a screen and traces of editing. Liveness confirms a live person with 99.9 % accuracy, and the selfie is compared with the photo in the document.

Liveness and passport check of the account administrator
Step 3

Rights and the log

The platform matches the full name from the document with the director from the INN response or with the power of attorney sent by the company: both values arrive in the result. If they match, the platform issues owner rights and the session number is saved in the account log for disputes and audit.

Issuing account owner rights after the check and writing the session to the log

The administrator left or lost access: how to recover a company account and not hand it to a stranger

Change of account owner

What to check before transferring rights

  • 01

    Why a letter to support is not enough

    “I am the new director, the old administrator left” — an ordinary request, and a fraudster sends the same one. The former administrator’s email and phone may have stayed with them or passed to third parties. Transferring rights by letter means giving the company’s data to whoever writes most convincingly.

  • 02

    Who decides for the company

    Owner rights are transferred not by support but by the company: the director per the register or a person with a power of attorney. The platform checks the company by tax number, and the new administrator completes a session with a document and Liveness. The full name from the passport is matched with the director or the power of attorney.

  • 03

    If the owner themselves lost access

    The owner changes their phone or loses their email — and restores access by document and Liveness. The passport data is compared with what they provided when rights were issued. For details of the scenario, see the access recovery page.

  • 04

    What to do after the transfer

    Reset the former administrator’s sessions and API keys, notify all of the account’s administrators, and hold back the database export and changes of payment details for a few days. That way even a successful takeover does not turn into a leak.

  • 1 session one person: document, Liveness and face
  • 24 hours for the first notification to Roskomnadzor about a leak
  • 5 ₽ the company’s director per the register

A verification checklist for a SaaS platform: from a trial to a researcher’s payout

The level of checking grows with what the user receives. A phone sign-in is enough for a trial, while owner rights, deferred payment and payouts require a document. This is a guide for a conversation with a lawyer, not a legal opinion; the rules are as of October 2026. How to choose the level of checking by risk — in a blog article.

  • Sign-in by a Russian number, through Gosuslugi, the EBS or a Russian system — without Google, Apple ID or foreign email Law
  • One trial per company and per person: INN and document number — before a trial is extended or higher limits are granted RecommendationNeuroVision

  • Company by INN: status, head and founders, sanctions lists NeuroVision
  • A repeat company check — before a contract is renewed and the deferred-payment limit grows Recommendation

  • The administrator’s document and Liveness; the full name is matched with the director or the power of attorney NeuroVision
  • The administrator’s separate consent to processing of the passport and selfie Law

  • A new administrator — the same session as when rights are issued; a letter to support is not grounds RecommendationNeuroVision
  • After the transfer — reset the former administrator’s sessions and keys, notify all administrators Recommendation

  • A company — by INN, an individual — passport and Liveness before admission to the programme NeuroVision
  • INN, self-employed status and sanctions lists — before every payout NeuroVision

  • An instruction from the customer company: list of data, purposes, protection, incident notification Law
  • The session data retention period is set in the scenario, and data is deleted on request NeuroVision
  • Law — required by law
  • Recommendation — practice, not an obligation
  • NeuroVision — the step is covered by a NeuroVision check: result, source and date

Passwords, roles, customer data: what stays with the SaaS platform

  • We do not replace sign-in required by law

    Sign-in by phone, through Gosuslugi, the EBS or a Russian system is set up by the platform. The document check and Liveness sit on top of it — at the steps where what is needed is not a number but a person.

  • We do not manage roles and passwords

    Passwords, SSO, roles and employee permissions live in your system. NeuroVision answers the question “who is this person and is the company real”, and the platform grants rights based on the result.

  • We do not store your customers’ data

    The customer base, deals and documents in the account are not passed to us. We process only the data of the person and company being checked; the storage period is set in the scenario.

  • We do not replace the contract or a lawyer

    The processing instruction, the administrator’s consent, the owner-change procedure and the steps to take in a leak are prepared by your lawyer. The check gives evidence of who received rights and when. A data subject request: how to verify the requester.

How to protect the access-recovery channel from takeover — on the page “Account access recovery by selfie”.

The decision to grant rights, open deferred payment or make a payout is made by the platform: NeuroVision provides the result of each check and the session number.

Re-checks in a SaaS: a new owner, expanded rights, deferred payment and payouts

  • A new owner or administrator

    The company’s director or account administrator changed — a company check by INN and a session with a document and Liveness for the new person before rights are transferred.

  • Access to export and API

    The administrator requests an export of the whole database, new API keys or access to sensitive sections — a document and Liveness again before they are issued.

  • Growth of the deferred-payment limit

    Before the contract is renewed and the deferral is increased — a repeat company check: status, director, sanctions lists.

  • A payout to a partner or researcher

    Before every payout — a document and Liveness again, INN and self-employed status: the money goes to the person who passed the check.

A leak through someone else’s account: what it means for a SaaS platform and what protects it

If a customer’s database was exported by a person to whom rights were transferred by letter, both the customer and the platform it entrusted its data to will have to answer. A confirmed owner identity and a log of the rights transfer are the main arguments in the review.

  • Notify Roskomnadzor

    The operator reports a leak within 24 hours and the results of the internal investigation within 72 hours

    The law requires the processor’s obligation to report such cases to the operator to be written into the instruction

    • 152‑FZ, part 3.1 of Art. 21
  • A fine for a leak

    For an operator that is an organisation — from 3 to 15 million ₽, depending on the number of people whose data leaked

    A repeat leak — from 1 to 3 % of revenue, at least 20 million ₽

    • Administrative Offences Code, Art. 13.11
  • Liability to the customer

    The operator — the customer company — answers to data subjects for the processor’s actions

    The processor answers to the operator — under the processing instruction agreement

    • 152‑FZ, part 5 of Art. 6
  • Sign-in through a foreign service

    Authorising users from Russia by methods other than those the law allows

    For a legal entity — 500,000 to 700,000 ₽ from 7 July 2026

    • Administrative Offences Code, Art. 13.55

Checks for a SaaS platform: catalogue and prices

The set is assembled for each step: a corporate plan needs a company check, the account owner needs a document and Liveness, and a partner needs self-employed status.

The client company

Before the contract, deferred payment and a limit extension.

  • Unified State Register of Legal Entities / Individual Entrepreneurs

    A company by INN: status, director, founders

    The company’s status, director and founders by the INN from the application — as part of the KYB scenario.

    on request

    Learn more
  • Tax Service · courts · lists

    Head and founders by registers

    A check of the head and founders against selected registers and lists.

    5 ₽ per register

    Learn more
  • Sanctions lists

    OFAC, EU, UK and UN sanctions lists

    The company, its director and founders are checked against four sanctions lists.

  • International lists

    International screening: sanctions and PEP

    Sanctions, PEP and adverse media against international lists.

    36 ₽

    Learn more

How much verification costs in a SaaS: administrator, company, researcher

No subscription fee: you pay for the sessions and checks performed. One KYC session is one person with all the steps of the scenario.

  • The client company

    on request

    Enable

    A company by INN as part of the KYB scenario. Director and founders — 5 ₽ per register, sanctions lists — 5 ₽, international screening — 36 ₽.

  • For account owners

    Administrator

    from 29 ₽ per session

    Calculate

    A document with anti-fraud, Liveness, and a face-to-document match. For issuing owner rights, changing the administrator and recovering access.

  • Partner and researcher

    from 29 ₽ per session

    Build a set

    Plus database checks at 5 ₽ or the basic Russian-passport package for 50 ₽. INN, self-employed status and sanctions lists before payout.

Up to 6 free attempts per step. Prices are per the price matrix on the date of publication. Test access — 1 month.

Integration: the check in the registration wizard, rights settings and the partner portal

The check is built into the screen where a company connects a corporate plan, appoints an owner or requests a payout, and the scenario is changed in the personal account without development.

SDK

Ready-made SDKs for iOS, Android and Web: the widget captures the document, selfie and Liveness and shows prompts. The logo, colours and texts are customised for your platform. Without development — a unique link that support sends to the new administrator. Documentation

  • SDK iOS, Android, Web
  • REST API
  • Webhook
  • Unique link
  • On-premises

Test access for 1 month.

A personal manager; you pay only for sessions actually completed; the data storage period is set in the scenario.

Why B2B SaaS platforms choose NeuroVision

A SaaS needs a check that does not slow down an honest customer’s onboarding and does not let a stranger reach owner rights.

Company and person — in one service

A company check by INN, the administrator’s document and Liveness, and a partner’s self-employed status all work through one API. For every account you have a session number and the result of each check.

There is no need to assemble a solution from several vendors and reconcile their responses.

Accuracy

Liveness 99.9 %, face comparison 99.74 %, iBeta PAD Level 1–3 attacks.

Speed

Liveness in under a second, selfie-to-document comparison in 0.1 s.

Document Liveness Company Partner

Documents of the world

16 000+ types from 195+ countries and territories for customers from different countries.

Skolkovo — participant

Your own environment

On-premises, if administrators’ data cannot be taken out.

A SaaS platform glossary: account owner, data processing instruction, trial abuse

Concepts that come up when a SaaS platform decides whom to trust with a company account.

Account owner
The user with the highest rights in a company account: appoints administrators and manages payment and data export.
Account owner
The account administrator
An employee of the customer company who manages users and settings in the SaaS.
Account administrator
Processing on behalf
A contract term under which a SaaS processes the personal data of a company’s customers on its behalf (part 3 of Art. 6 of 152‑FZ).
Data processing agreement
Personal data operator
The party that determines the purposes and scope of processing. For data in the account — the customer company.
Data controller
Account takeover
Gaining control of someone else’s account: through a stolen password, email or deception of support.
Account takeover
Trial abuse
Obtaining a trial repeatedly through new registrations.
Trial abuse
KYB
Company check — registration, director, founders, sanctions lists.
Know Your Business
Liveness
A check that in front of the camera is a live person, not a photo, screen, mask or deepfake.
Liveness detection
Bug bounty
A programme in which a company pays researchers for the vulnerabilities they find.
Bug bounty
Virtual data room
Secure storage for deal documents with access for participants of the parties.
Virtual data room

Frequently asked questions about verifying users of SaaS platforms

So that rights over a company’s data, deferred payment and payouts go to those who were entrusted with them. A phone sign-in is enough for a trial. Before a corporate plan, check the company by INN; before issuing owner rights, the administrator’s document and Liveness; before paying a partner, INN and self-employed status.

No. The law sets the sign-in methods for users from Russia — a phone number, Gosuslugi, the EBS or a Russian system — and responsibility for personal data. The platform switches on the document check according to risk, and 115‑FZ does not apply to a SaaS unless the service itself accepts payments as a money transfer operator.

The law allows users located in Russia to be authorised only by a mobile operator number, through Gosuslugi, the EBS or a system whose owner is a Russian company or a Russian citizen. From 7 July 2026 a legal entity faces a fine of 500 000 to 700 000 ₽ for a breach.

If a customer company entrusts the platform with processing the data of its own customers and employees, the operator is that company. The operator answers to people for the processor, and the processor answers to the operator. The operator notifies Roskomnadzor of a leak within 24 hours, and the instruction states that the processor reports such cases to it.

Check the company by INN and ask the new administrator to complete a session: a document, Liveness and a comparison of the face with the passport photo. Match the full name from the document with the director per the register or with a power of attorney. Only then transfer owner rights.

If the rights are requested not by the director but by an employee under a machine-readable power of attorney, check it separately: term, powers, the principal’s signature and whether the representative matches the signatory. That is done by the power-of-attorney (MCHD) check, and in the same session the employee passes the document and Liveness. What exactly the administrator is allowed to do on your platform — roles and permissions — is up to you.

Ask them to complete a session with a document and Liveness and compare the passport data with what they provided when rights were issued. After recovery, reset the old sessions and API keys and notify the other administrators.

Do not ask for a document at the start — it will put honest customers off. Ask for it when a user extends a trial or requests higher limits: one document number — one trial. Repeats and linked accounts are visible to anti-fraud at registration.

A company — by INN and sanctions lists. An individual — passport and Liveness before admission to the programme, and before every payout a document and Liveness again, INN and self-employed status. Each database check costs 5 ₽.

No. The customer base and documents in the account are not passed to us. We process the data of the person and company being checked, the storage period is set in the scenario, and session data is deleted on request.

Yes. NeuroVision is installed on-premises with the same capabilities as in the cloud — if customers require that administrators’ data does not leave your infrastructure.

Renting out computing capacity is hosting: separate customer identification rules apply to it. For details, see the page for hosting providers and clouds.

A “Document + Liveness” session — from 29 ₽, “Document” — from 16 ₽, database checks — 5 ₽, the basic Russian-passport check package — 50 ₽, there is no subscription fee. Test access — 1 month.

We will choose a verification scenario for your SaaS platform

Tell us whom you want to check — customer companies, administrators, partners or researchers — and how many checks a month you expect. We will build a scenario for each step and give you test access.

Can't put your request into words? Book a call and our team will contact you at a convenient time

Book a call

The company is included in the register of IT companies and the register of personal data operators of the Russian Ministry of Digital Development.

Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.