Step 1
Launch from the card
The manager clicks “Check customer” in the deal card. Or a rule starts the check: the deal has moved to the “Contract preparation” stage — and your system creates the session itself.
KYC module for CRM, ERP and 1C
KYC for CRM without a second window: your system starts a check from the deal, customer or counterparty card, the customer completes it via a link, and the passport fields, the results of watchlist and sanctions checks and the session link return to the same card. You connect through the Web SDK, KYC links, a webhook and the REST API; we do not claim ready-made connectors for specific CRMs and 1C.
REST API and Web SDK Session result — by webhook Session log per customer
Checking a customer outside the CRM: where data and time are lost
A check is a funnel stage
Not a separate service you have to leave the CRM for, but a funnel step: your system starts the check and gets the result back. The result stays where the decision is made.
- 01
The passport is retyped twice
The customer sends a photo in a messenger, the manager copies the series, number and address into the CRM, and the accountant copies them into 1C for the contract. Every retyping is a chance of a typo that is only noticed at signing.
- 02
The check lives in someone else’s window
Watchlists, sanctions and passport validity are checked on third-party sites, and the result is a screenshot in a comment or “checked” in a field. A year later nobody can say what exactly was looked at and when.
- 03
The deal moves faster than the check
The manager needs to close the deal, and the check is an extra step. If it is not built into the funnel stage, it gets skipped on the busiest day, and the contract goes to a customer who is on a watchlist.
- 04
Every department has its own service
Sales check customers, procurement checks suppliers, HR checks candidates. Three subscriptions, three formats, and no shared log from which the security team could build a picture.
- 1 link to the customer — and the check runs without a second window for the manager
- 0 retypings passport fields arrive in the response and the webhook, not from a messenger
- 24 checks in the AML catalogue: watchlists, sanctions, passport, courts
CRM, ERP, 1C and core banking systems: what the check connects to
We do not claim ready-made connectors for specific CRMs and 1C: you connect through the REST API, Web SDK and a webhook, and the result is the same in every system — fields, statuses and the session link. Can’t find your system? Any system that can call an HTTP service and receive a webhook will do — how the API works.
-
1C:Enterprise
A counterparty, individual or employee card: the passport details are taken from the service response, and the check results are written to the card. The request and the write-back are implemented by your developer or 1C integrator.
-
CRM with a deal funnel
A funnel stage or a manager’s action triggers your integration: it creates a KYC session and sends the customer a link. The result arrives by webhook at your address and is written to the deal fields — the deal moves to the right stage.
-
CRM without developers
If you have no developer: one-time KYC links are created in the NeuroVision personal account — up to 1,000 at a time — and sent to customers by a CRM mailing. The result is exported to CSV or XLSX for import into the cards.
-
Online shops and order management
Checking a buyer before an expensive order, an instalment plan or a pick-up point handover: the check status is written to the order card, and a refusal comes before dispatch, not after a return.
-
ERP and accounting systems
The ERP sends a person’s data to the REST API and gets the check results by run ID, while the KYC session result arrives by webhook. It suits any ERP that can call an HTTP service.
-
Core banking, online banking and bank front-office systems
For banks and microfinance organisations — integration with core banking, online banking and an anti-fraud system via the API: the check result arrives at your backend address, and your system makes the decision.
A check from the deal card: from the button to the status
An example — a deal in a leasing company’s CRM. In 1C, ERP and other systems the steps are the same, only the field names change. One customer — one KYC session.
Step 2
A link to the customer
Your CRM sends the customer a link to the check — by email, SMS or chat. The link is single-use; your system records which link went to which customer by session ID, so results do not get mixed up.
Step 3
Passport and selfie in the widget
The customer photographs the passport and face in the phone browser. The widget prompts if the frame is blurred and rejects photos of a screen, printouts and traces of an editor. More — on the page on verification on a website and in an app.
Step 4
Database checks
The checks from the scenario run on the recognised passport data: passport validity, the Rosfinmonitoring list, sanctions lists, bankruptcy and wanted lists.
Step 5
Fields and statuses — to the card
The session result arrives by webhook at your system’s address: full name, date of birth, passport series and number, the status of each check and the session link. Your handler writes them to the card — the manager retypes nothing.
Step 6
A decision by a funnel rule
All clear — the deal moves on. A watchlist match or signs of forgery — your system moves the deal to “Manual review” for the security team, and no contract is generated.
What is written to the customer card
The card gets only what the decision is based on and what the contract needs. The document and selfie images stay in the KYC session: the CRM holds a link to it.
- Full name, date and place of birth, passport series and number, issue date, issuing authority, department code, registration address — into the card fields or the individual’s details in 1C
- Document type and country — for 16,000+ document types from 195+ countries and territories; the name in Latin script for a foreign passport
- The document anti-fraud result: a photo of a screen, a printout, traces of an editor, machine-readable zone checksums
- Matching the selfie with the passport photo and the liveness check — “passed” or “failed”
- Session status: success, failed, suspicious, expired — in the “Customer check” field
- A link to the session in the NeuroVision account: the frames and details are visible to an employee with access, not to every CRM user
- Each check gets its own line: passport validity, tax number by passport, the list of terrorists and extremists, the OFAC, EU, UK and UN sanctions lists, PEP, bankruptcy, wanted lists
- The date and time of each check — for the log and audit
- “Not checked” is kept separate from “clear”: if there was not enough data, the field will not turn green
- For a counterparty card in 1C or a company in the CRM — the company check scenario; confirm the set of checks and API access during test access. More — on the page counterparty checks.
- The director and founders are checked against watchlists and sanctions in the same way as an individual customer
- You decide which fields to fill and which to leave in the session: the mapping of card fields to the response is set when you connect. The full list of response fields is in the documentation.
Sales, back office, HR, procurement: check scenarios in accounting systems
-
Lead and deal qualification
Where it runs. In the CRM at the “Agreeing terms” stage — before the manager spends time on the contract.
What the system receives. Confirmed full name and passport, watchlists and sanctions; a lead on a watchlist does not reach the commercial offer. -
Contract and disbursement
Where it runs. In the back office of a leasing company, microfinance organisation or developer — before the contract is generated in 1C.
What the system receives. Passport details for the printed form without retyping, and a check mark in the contract card. More — for leasing and factoring. -
Procurement and accounting
Where it runs. In the counterparty card in 1C or ERP — when a supplier is set up and before a large payment.
What the system receives. Counterparty checks in 1C without exports: the scenario result counterparty checks is written to the card. -
HR
Where it runs. In the HR system or 1C:ZUP — when a candidate or contractor is hired.
What the system receives. A Russian passport or a foreign document without manual entry, passport validity and wanted lists — with the candidate’s consent. -
Security and compliance
Where it runs. The “Manual review” queue in the CRM: deals with matches and signs of forgery land here.
What the system receives. A log of who checked whom, when and against which databases — without screenshots. -
Re-checking the customer base
Where it runs. On a schedule from your CRM or 1C: the system resubmits customer data for checking — once a year or once every three years, depending on the customer’s risk.
What the system receives. New watchlist and sanctions matches among existing customers — as a task for the person responsible.
The same service — different departments. The check scenario (which document, which databases, what counts as a refusal) is configured separately for each funnel.
The scenarios are not mutually exclusive: one CRM can have a quick check for a lead and a full one — before the contract. The price depends on the content of the scenario, not on the number of funnels.
How to build verification into a CRM: Web SDK, KYC link, webhook or REST API
Terms
- Try the demo
- One customer — one KYC session
- Support under the contract, via a ticket system
Customer personal data in the CRM: processing on behalf, localisation and retention periods
When the check is built into the CRM, data lives in two places — in the card and in the KYC session. Below is what follows from this under the law and how it is handled when you connect.
- Discuss the contract
Who is responsible for the data
152‑FZ, art. 6
The operator is your company
- You determine the purposes and the scope of data. NeuroVision processes the data on your behalf.
Processing on behalf under a contract
- Processing can be entrusted to another party with the customer’s consent; the instruction specifies the list of data, the actions, the purposes and the protection requirements (part 3 of art. 6 of 152‑FZ). The instruction is part of the contract with NeuroVision.
Liability
- The operator is answerable to the customer for the processor, and the processor is answerable to the operator (part 5 of art. 6).
- A question about retention
Where and for how long to store it
152‑FZ, arts. 5 and 18
The CRM database — in Russia
- Recording, storing and updating the personal data of Russian citizens in databases outside the country is not permitted, except in the cases in items 2, 3, 4 and 8 of part 1 of art. 6 (part 5 of art. 18 of 152‑FZ). If the CRM keeps its database abroad, passport fields are not written there. Ask where NeuroVision’s servers are located when you conclude the contract.
The card — the minimum
- Data may be stored no longer than the purposes require (part 7 of art. 5 of 152‑FZ). The CRM holds the fields for the contract and statuses; passport frames and the selfie stay in the KYC session, so not every CRM user sees the customer’s face.
Erasure on request
- If the customer withdraws consent or the period expires — the session data is destroyed by a single request per customer across all their sessions, and the deletion is logged. Your system deletes the CRM fields on the same event.
- Discuss your scenario
If you carry out identification under 115‑FZ
115‑FZ, art. 7
Five years after the relationship ends
- Documents and information about the customer are kept for at least five years from the end of the relationship (item 4 of art. 7 of 115‑FZ).
Updating the records
- At least once a year, for low-risk customers — at least once every three years, and within seven working days if there are doubts (item 3 of art. 7).
What the service provides
- The retention period for results is set in the scenario, the session log is available in the account, and your CRM or 1C runs the scheduled re-check of the database.
The summary of the provisions is simplified and is not legal advice.
Without a developer, with an integrator or via the API: who connects the check
The timeframe depends not on the check itself but on how many funnels and fields need configuring. A typical path — test access, one scenario on one funnel, then the other departments.
-
A CRM or 1C administrator
If no development is needed: the administrator creates a scenario in the NeuroVision account, generates KYC links — up to 1,000 at a time — and sends them to customers from the CRM. The result is exported to CSV or XLSX.
- For integrators
Your 1C or CRM integrator
If the system has been customised for you — cards, stages, printed forms — the integrator who maintains it makes the connection. Any developer can get test access and the documentation; the terms for integrators are on a separate page.
- API and SDK
Your developers
For ERP, core banking and an in-house CRM — the REST API and a webhook. Connecting the KYC API takes a developer an evening for the first request and a few days for the webhook, refusal handling and tests on your data.
- Discuss the project
The NeuroVision team
Tell us about your system and funnel — we will choose a connection method and set up the check scenario on test access. The terms of an implementation project for banks and large companies are available on request.
How much a check from the CRM and 1C costs
You pay for checks, not for the way they are started: the cost is calculated by sessions and database checks, regardless of where the check was started — from the card, by a link or from the ERP.
- Calculate
Document
from 16 ₽
Passport recognition, anti-fraud, machine-readable zone checks, fields — into your system.
- Calculate
Document + liveness
from 29 ₽
Everything in the “Document” package plus a selfie, matching with the passport photo and a liveness check.
- Discuss
A project for your system
on request
Connection to ERP and core banking, scenarios for several departments, repeat database checks from your CRM or 1C.
Database checks — 5 ₽ per register, international compliance screening — 36 ₽. A check that lacked data is not charged; repeat capture attempts are not paid for. Calculator in the price matrix.
Glossary: card, webhook, field mapping and scenario
- KYC module
- A link between your CRM, ERP or 1C and NeuroVision: a step or a button in the card starts a customer check, and the result is written to the card fields. It is built on the REST API, Web SDK and a webhook; we do not claim a ready-made connector for a specific system.
- KYC module
- Card
- A record of a customer, deal, counterparty or employee in an accounting system; your system writes the check fields and statuses into it.
- Record
- KYC session
- One visit by one person through the check scenario: document, selfie, database checks and the result.
- KYC session
- Scenario
- A set of check steps in the NeuroVision account: which documents, countries and checks, and where to send the result.
- Verification flow
- KYC link
- A single-use link to the check widget that the customer opens in a phone or computer browser.
- Verification link
- Webhook
- A notification that the platform sends to your system’s address when the check is complete.
- Webhook
- Field mapping
- The correspondence between check response fields and card fields: for example, “passport series” → a contract field in 1C.
- Field mapping
- Processing on behalf of the operator
- A contractual term under which NeuroVision processes customers’ personal data on behalf of your company (part 3 of art. 6 of 152‑FZ).
- Data processing instruction
- Manual review
- The funnel stage where deals with watchlist matches or signs of document forgery end up.
- Manual review
Read also
383 13
KYC, AML and Digital Identification
How to build a KYC policy compliant with Federal Law 115-FZ, Federal Law 152-FZ, FATF and GDPR
384 16
KYC, AML and Digital Identification
How to ensure the protection of personal and biometric data in KYC processes
398 27
KYC, AML and Digital Identification
The KYC Funnel: How to Increase Verification Completion and the Approval Rate Without Slowing Down the Decision
114 29
KYC, AML and Digital Identification
115-FZ: What Businesses Are Required to Do and How to Meet the Law’s Requirements
346 14
Anti-Fraud, Liveness and Deepfake Protection
An antifraud solution for a company: requirements for data, integration and security
166 30
KYC, AML and Digital Identification
Politically Exposed Person (PEP): Who It Is and What 115-FZ Requires
Frequently asked questions about KYC in CRM, ERP and 1C
Recognition only copies the passport fields into the card. KYC checks the customer as a whole: the authenticity of the document, liveness and face match, watchlists, sanctions and passport validity — and your system writes to the card not only the fields but also the status of each check with a link to the session. Integrating verification with the CRM removes both retyping and checks in other people’s windows.
We do not claim ready-made connectors for specific CRMs, ERPs and 1C. You connect through the REST API, Web SDK, KYC links and a webhook: the result is the same in every system — fields, statuses and the session link; the request and the write-back to the card are configured on your side.
Partly. One-time KYC links are created in the NeuroVision account — up to 1,000 at a time — and sent to customers by a CRM mailing, and the result is exported to CSV or XLSX. Automatic launch from the card and writing back the result require the REST API and a webhook.
Through the REST API: the ERP calls an HTTP service with the person’s data, starts the checks and fetches the result by run ID, while the KYC session result arrives by webhook. The approach does not depend on which ERP it is — all that is needed is the ability to call an HTTP service and receive a webhook.
A request from the counterparty card is implemented through the REST API; the set of company checks and API access — on test access. What the scenario includes — on the page counterparty checks.
The card gets the passport fields, the session status, the status of each check and the session link. Passport frames and the selfie stay in the KYC session: they are visible to an employee with access to the NeuroVision account, not to every CRM user. The set of fields is defined when you connect.
Yes, if the CRM database is in Russia: recording and storing the personal data of Russian citizens in databases abroad is not permitted, except in the cases set out in the law (part 5 of art. 18 of 152‑FZ). By handing the check to NeuroVision, the company entrusts processing under a contract (part 3 of art. 6 of 152‑FZ). Ask where NeuroVision’s servers are located when you conclude the contract.
Yes. Any developer can get test access and the documentation; the terms for integrators are described on the page for integrators. In Russia NeuroVision products are also distributed by the IT distributor TERA.
KYC session data is stored for the period set in the scenario or by the contract; personal data is deleted by an API request. Where the servers are located and which hosting options are available — on the page on platform hosting and when the contract is concluded.
You pay for checks: a KYC session — from 16 ₽, with liveness — from 29 ₽, database checks — 5 ₽ per register. A check that lacked data is not charged. We calculate the cost of a project to connect ERP and core banking systems on request.
We will show the check in your CRM
Tell us which system you use — 1C, CRM, ERP or an in-house build — whom you check and at what stage. We will show a check from the card in a demo 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 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.
