Step 1
Pass KYC
The person photographs the document, takes a selfie and passes Liveness. The platform recognises the fields, checks the document for forgery and compares the selfie with the photo in that document once.
Digital ID digital identity platform
A person passes KYC once and gets a digital passport. After that, your services and partners receive a confirmed fact from it: “over 18”, “document verified”, “not on any lists” — with no passport copy and no repeat check.
Zero-knowledge proofs Post-quantum algorithms Cloud in Russia or your perimeter
Digital ID for business: verify a person once and stop collecting their passport again
A digital passport — a layer on top of KYC
The check is performed by the NeuroVision KYC platform, and the result becomes a signed digital passport. It can be presented again — disclosing exactly what the service needs.
- 01
Every service asks for the passport again
A customer in an ecosystem goes through the same check at a bank, a broker and a marketplace. Every time — a photo of the document, a selfie, waiting. Some people abandon registration at the second service.
- 02
Document copies pile up everywhere
To check age, a service stores a passport scan with the address and number. The more copies, the more places they can leak from, and the more work for the person responsible for personal data.
- 03
A service needs a fact, not a document
An 18+ store cares about “over 18”, a broker about “not on sanctions lists”, a rental service about “the document is genuine”. None of them needs the date of birth, address or passport series.
- 04
A verification result cannot be passed on
Even if the person has already been checked by a neighbouring service in the group, an ordinary KYC report is a file. Proving that it has not been swapped and that it is about the same person is hard.
- 1 check passport, selfie, Liveness and databases once
- 1 attribute the service receives only the requested fact
- 16 in 1 database checks at RUB 50 before issuance
Issuing a digital passport after KYC and presenting it: six steps
The first three steps are done once, at issuance. The next ones repeat every time a partner service asks to confirm data.
Step 2
Check against databases
At the issuer’s choice — checks against Russian registries and international lists: sanctions, PEP, invalid passports, Rosfinmonitoring lists. The result goes into the passport with the date of the check.
Step 3
Issue the passport
Confirmed attributes are encrypted and signed. Only cryptographic commitments and an issuance receipt are written to the distributed registry — without the name, date of birth or document number.
Step 4
Receive a service request
A partner service asks to confirm a specific fact: for example, “over 18” and “document verified”. The owner sees who is asking and what exactly.
Step 5
Give consent
The owner confirms the request with a key on their own device. Without their consent the service receives nothing — neither the fact nor any data.
Step 6
The service verifies the proof
The service receives a zero-knowledge proof and matches it against the registry record: the passport was issued, has not been revoked, the fact is true. The document and date of birth never reach it.
What a service learns from a digital passport without seeing the document
Selective disclosure: the service requests attributes, the owner agrees — and the service gets a “yes” or “no” with a proof, not a scan. The set of attributes is configured for your ecosystem.
-
Over 18 — without the date of birth
A store, bookmaker or rental service gets the fact of majority. The date of birth stays with the owner. How to check age without a digital passport — on the page age verification.
-
Document verified
The document passed checks for forgery, screen capture and signs of editing, and the face in the selfie matched the photo in it at issuance. The service sees the date and level of the check.
-
A live person at issuance
At issuance, the customer passed Liveness: in front of the camera was a person, not a photo, video, mask or deepfake.
-
Not on lists as of the check date
The result of screening against sanctions, PEP and Rosfinmonitoring lists, with a date. For a fresh decision the service can request a repeat database check.
-
Citizenship and country of the document
The issuing country and citizenship — without the number and series. Needed by services that work only with residents or check foreigners differently.
-
Full name matches the one provided
The service sends the full name from its form and receives an answer on whether it matches the passport. If the name itself must be disclosed — it is a separate attribute and a separate consent.
Identity data protection: ZKP, encryption and post-quantum cryptography
-
Zero-knowledge proof
ZKP verification lets you prove a statement — “over 18”, “document verified” — without passing the data itself. The service is convinced that the answer is true and refers to an issued passport, but learns nothing beyond it.
-
The registry holds commitments, not data
The distributed registry records cryptographic commitments and an issuance receipt. They can be used to verify the authenticity of an answer, but not to recover the name, date of birth or document number.
-
Attributes are encrypted
Confirmed data is stored in an encrypted package. The access key is held by the owner; without their consent the package is not disclosed to either the service or the registry operator.
-
Post-quantum algorithms
Quantum-resistant algorithms ML-DSA and ML-KEM from the NIST FIPS 204 and 203 standards (2024) are used for signing and key exchange. Records made today will not become readable when quantum computers arrive.
-
Erasure on request
Consent withdrawn — the encrypted package is destroyed, new presentations are rejected. Only commitments remain in the registry, from which the person cannot be found.
-
Presentation log
Every presentation is recorded: which service, which attribute, when, with what result. The owner and the issuer can see to whom and what was disclosed.
Digital ID cryptography protects data inside the platform and does not replace certified information security tools. If your system is legally required to use FSB-certified cryptographic tools — for example, when working with the Unified Biometric System (EBS) — they stay in your environment.
What sits in the registry, with the owner and with the service
The protected action registry stores not personal data but what an answer can be verified against. Data stays with whoever it belongs to.
- Register
Register
- Commitments to attributes
- Issuance receipt
- Status: active or revoked
- Issuance and revocation timestamps
- Owner
Owner
- Key on the device
- Encrypted attribute package
- History: to whom and what was disclosed
- “Withdraw consent” button
- Service
Partner service
- The requested fact: “yes” or “no”
- The proof and a link to the registry record
- Date and level of the original check
- No scan and no document number
You set the retention period for the KYC session the passport was issued from in the scenario; session data is deleted on request via the API — documentation.
How the owner proves the digital passport is theirs
The service chooses the confirmation level. The higher the operation risk, the stricter the method, but none of them is recognition by a stored face.
-
Key on the device
Standard level: the owner confirms the request with a key stored on their phone or computer and protected by the device code. Suitable for age, registration, signing back in to a service.
-
The document and Liveness again
High level: for a large operation or a change of details the owner shows the document again and passes Liveness. The face is compared with the photo in that document, once, within the session — as in passport and selfie check.
-
Through the Unified Biometric System
If a service needs to confirm identity by biometrics automatically, the lawful route is the Unified Biometric System (EBS). How to combine it with NeuroVision checks — on the page identification through the UBS.
-
An employee in the office
At a branch or pickup point, an employee sees the person, their document and the passport data on screen and decides whether they match. The digital passport speeds up processing; the decision stays with a human.
The digital passport and the law: consent, data minimisation and the limits of Federal Law 572‑FZ
The NeuroVision digital passport is a business tool for reusing a check. It does not replace a citizen’s passport and is not connected to the state “Digital ID” — that is a separate service.
- Consent to processing must be specific, informed, conscious and unambiguous (Art. 9, part 1). The owner sees which service requests which attribute and agrees to each presentation
- A selfie used to establish identity at issuance is biometric data: written consent is required (Art. 11, part 1). It is obtained at the first step of the KYC session
- The volume of data must match the purposes and must not be excessive (Art. 5, part 5). Selective disclosure gives a service a fact instead of a document copy
- When consent is withdrawn, processing stops and data is destroyed (Art. 21, part 5). In Digital ID, withdrawal is one button for the owner
- Automatic identification and authentication by biometrics goes through the Unified Biometric System (Art. 15, part 1, item 2). That is why the digital passport is confirmed by a device key, and the face is compared only with the document within the current session
- There are no biometric templates in the digital passport: it holds check results, not a face
- Banks, microfinance organisations, brokers and other entities under 115‑FZ identify a customer under the law and their own internal control rules (Art. 7). The digital passport speeds up collecting and matching data but does not cancel your procedure
- Remote identification under the law goes through the EBS; how to combine it with NeuroVision checks — on the page remote identification
- This is a guideline, not a legal opinion; the exact text of the rules is in ConsultantPlus. The state digital ID in the Gosuslugi apps is a separate service; NeuroVision neither issues nor verifies it.
Digital passport lifetime: renewal, revocation and a lost device
-
Every attribute has its own date
“Over 18” does not expire, while a list-screening result does. The service sees the date of the original check and decides whether to accept it or request a fresh database check.
-
A new document — a new issuance
The person changed their passport or surname — they pass KYC with the new document, the old digital passport is revoked and a new one is issued. On the next request services receive the current one.
-
Revocation by the owner or the issuer
The owner withdraws consent; the issuer revokes the passport if the document is found invalid or the check is reviewed. The “revoked” status is visible in the registry immediately.
-
A phone with the key is lost
The key on the old device is blocked, and access to the passport is restored after a new document check and Liveness — as in account access recovery.
The validity period of the passport and of each attribute is set by the issuing organisation in the rules of its ecosystem.
Who needs reusable KYC: banks, Web3, ecosystems
Digital ID pays off where the same person comes to several services or where a service needs a fact, not a document.
-
Ecosystems and groups of companies
- One check — for the bank, insurance, marketplace and delivery service of the group.
- Interagency and interbank exchange of confirmed attributes is built on the same rules. Discuss
-
Banks
- Digital ID for a bank: a partner’s customer arrives with an already verified document and a screening result, and the form fills itself in.
- Identification under 115‑FZ — by your rules. Learn more
-
Crypto services and Web3
- A digital passport for DeFi and Web3 services: confirm “verified and not on lists” without handing the document to every platform. Learn more
-
18+ services and sharing
- Stores, bookmakers, rental and car sharing get “over 18” and “document verified” in one touch, without storing scans. Learn more
-
Fintech and payments
- Repeat customer registration at a partner’s service without a second KYC, data confirmation when details change. Learn more
-
Education, HR and the public sector
- Confirming identity and citizenship for exams, hiring and applications without passport copies in every system. Learn more
How much it costs to issue and verify a digital passport
Issuance starts with an ordinary KYC session at the price-matrix rate. Registry connection and presentations are calculated for your ecosystem.
- Connect KYC
KYC session for issuance
from 29 ₽ per session
The “Document + Liveness” package: document recognition and verification, selfie and Liveness, matching the face with the photo in the document. An additional document — RUB 10.
-
The registry, passport issuance, selective disclosure and proof verification by partner services. The price depends on the number of owners and presentations.
- Choose checks
Database checks
5 ₽ per check
Any check against Russian registries — RUB 5, all 16 — RUB 50, international sanctions and PEP screening — RUB 36. The result goes into the passport with a date.
The KYC session price falls with volume — the calculator in the price matrix.
How to connect Digital ID: a partner ecosystem, your environment or the API
Terms
- A pilot with your partners
- Documentation and test environment
- Integration support under the contract
Digital ID glossary
Terms you will meet in conversations with a CISO, a lawyer and ecosystem partners.
- Digital passport
- A confirmed profile of a person issued after successful KYC. It is presented to partner services instead of a repeat check.
- digital ID
- Attribute
- A separate confirmed fact about a person: “over 18”, “document verified”, “not on lists as of the date”.
- attribute
- Selective disclosure
- Presenting only the attributes a service has requested, without the rest of the data or the document.
- selective disclosure
- Zero-knowledge proof
- A way to prove a statement is true without revealing the data it is based on.
- ZKP
- Commitment
- A cryptographic “fingerprint” of data in the registry. It is used to verify an answer but not to recover the data itself.
- commitment
- Distributed registry
- A database of records whose copies are held by several participants; a record cannot be quietly changed retroactively.
- distributed ledger
- Post-quantum cryptography
- Signature and encryption algorithms resistant to attacks using quantum computers.
- post-quantum cryptography
- Owner key
- A secret on the owner’s device with which they confirm consent to a presentation. Not biometrics.
- holder key
- Revocation
- Ending the validity of a passport or consent; the status is immediately visible to services in the registry.
- revocation
- Reusable KYC
- An approach in which the result of one check is used by several services.
- reusable KYC
Read also
404 16
KYC, AML and Digital Identification
How to ensure the protection of personal and biometric data in KYC processes
359 23
KYC, AML and Digital Identification
Repeat KYC: how to conduct re-identification without losing customers
397 23
KYC, AML and Digital Identification
Local or cloud KYC: how to choose a biometric data storage model
393 13
KYC, AML and Digital Identification
Digital KYC and e-KYC: how real-time remote identity verification works
Frequently asked questions about the Digital ID digital passport
A digital identity platform for business. After successful KYC a person gets a digital passport — a confirmed profile that can be presented to partner services without passing the check again. The service receives only the requested facts.
Pass KYC in a service that issues passports: photograph the document, take a selfie and pass Liveness. After a successful check the passport is issued automatically, and the key is stored on the owner’s device.
A record of the passport sits in a distributed registry, but it contains no personal data — only cryptographic commitments and an issuance receipt. The attributes themselves are encrypted, and the key is held by the owner. Digital ID uses no tokens or cryptocurrency.
A service requests a specific fact, for example “over 18”. The owner agrees, and the service receives a zero-knowledge proof: the fact is true and refers to a valid passport. The service does not receive the date of birth or the document.
No. A selfie is needed only at issuance — for Liveness and a one-time comparison with the photo in the document. The passport holds the check result, not the face or a biometric template. Confirmation by biometrics without a document goes through the EBS.
Registry records are kept for a long time, and quantum computers may one day break classical cryptography. That is why quantum-resistant algorithms ML-DSA and ML-KEM from the 2024 NIST standards are used for signing and key exchange.
No. It is a business tool for reusing a check within your ecosystem. Where the law requires showing a passport or going through identification under specific rules, that requirement remains.
No, the bank carries out identification under 115‑FZ by the rules of the law and its own internal control rules. The digital passport speeds it up: document data and screening results arrive ready and verified. Remote identification under the law goes through the EBS.
The digital passport confirms facts about a person; it does not sign documents. For signing a contract right after verification there is a separate scenario — a simple electronic signature with an audit trail in the NeuroSign service.
The encrypted attribute package is destroyed, the passport gets the “revoked” status and new presentations are rejected. Services that have already received a fact keep it under their own rules and retention periods.
Let’s discuss a digital passport for your services
Tell us how many services and partners you have, what data they ask customers for and where KYC happens today — we will propose a set of attributes, a registry scheme and a pilot plan.
Can't put your request into words? Book a call and our team will contact you at a convenient time
Book a call
The NeuroVision platform is listed in the Russian software registry, entry no. 19972. Rospatent certificate no. 2023661508.
Address: Moscow, Presnenskaya Embankment 12 — Moscow City business centre, Federation Tower. Nearest metro stations: Delovoy Tsentr and Mezhdunarodnaya.
