The result goes to your system
The webmaster presses “Withdraw funds” and goes through the session in the account area. The result arrives as JSON by session identifier and by webhook: document fields, antifraud, Liveness, tax ID (INN) and status.
Registration stays quick, while checking is built into tiers: a document before the first withdrawal, Liveness and a face match against the document photo before a large sum, a new session when payout details change. Disputed sessions are gathered into a manual review queue. You set the thresholds; traffic quality and advertising records remain with your network.
Data stored in Russia · Russian software registry no. 19972 · 152‑FZ
The law does not require every webmaster to be checked with a document, so you set the tiers and thresholds.
A network writes three things into the programme rules before registration: what is checked, when, and what happens to the payout. The points are in the cards. The law on advertising records is covered on the labelling page.
Civil Code of the Russian Federation, Arts 428, 437, 438
Tax Code of the Russian Federation, clause 1 of Art. 226; Federal Law No. 422‑FZ, Part 8 of Art. 2, Part 1 of Art. 15
Federal Law No. 152‑FZ, Art. 9, Parts 5 and 7 of Art. 5
Checking a webmaster touches five roles. If you do not divide what each one does, it belongs to nobody and payouts wait.
Six tiers from registration to a company partner. This is an example configuration: you set the events and sums for each tier.
Email, nickname and site — without a document, so as not to lose honest webmasters.
Withdrawal is closed until the person passes the second tier.
The passport with no manual entry: full name, date of birth and document number arrive in the profile form, a photo of a screen and alterations are visible at once.
Tax ID (INN) from the passport and self-employed status — in the same session.
Liveness: a person in front of the camera, not a photo, screen, mask or deepfake.
Matching with the photo in the document — once, in the same session; there is no search of a face database.
Card or account changed — a short new session: document and Liveness.
Payout details are changed by the passport holder, not by someone who gained access to the account.
Self-employed status and passport validity — as of the payout date, without a new session.
Watchlists and sanctions — on each watchlist update; matches go to manual review.
Company by tax number: its status, director and founders; representative goes through their own session from tier 2.
Checking CPA‑network partners as one set: the person and the company.
The check answers the question “who is this person”. What to do with the answer is decided by your system’s rule.
You catch fraudsters with the check, and you lose honest webmasters through how it is designed. These four failures are in the process, not in the partners.
A person who has not yet earned their first rouble is asked for a passport. Some leave before the network has had time to check them. The document is needed before the first withdrawal, not before the first click.
The payout was sent and the check was promised later. If the webmaster turns out to be a returnee after a ban, the money is already with them. The check comes before the transfer.
All disputed sessions pile up by the payout date, the operator cannot cope, and honest webmasters wait. The queue is built by status, and the review deadline is set in advance.
The webmaster was checked at registration and then deregistered as self-employed. The status is checked as of the date of each payout, not once.
Four groups, sixteen lines. A tag shows who closes the line: our check, your network or accounting.
Ask for the document where money appears: at the “Withdraw funds” button, not at registration. Before a large sum — Liveness.
The waiting screen explains why the document is needed and how long it takes. A refusal names the reason: “photo of a screen”, “data does not match the profile”, “document has expired”.
A blurry frame or a covered flash is not a reason to refuse. Give a second attempt via a link whose validity period you set: from 15 minutes to 30 days.
A disputed case goes to an operator for review, not to an automatic refusal. The affiliate manager explains the situation to the partner, and the session is not lost.
The check exists so that a real person receives the money, not to weed out partners. How it is designed determines how many honest webmasters reach payout. You write the texts of screens and refusals. NeuroVision returns the reason for refusal as a code and the session status.
Clicks, conversions and suspicious sources are checked by your analytics.
We confirm who withdraws the money.
The legality of an offer, licences and restrictions on advertising certain goods — the network’s lawyer.
Labelling, contracts and data for the register — a separate topic: advertising records and labelling.
You take the check data from the session response.
Calculating personal income tax (NDFL), self-employed receipts and contributions — accounting.
We provide the tax ID (INN) and status as of the check date.
You confirm that a site or channel belongs to the webmaster.
We confirm that the account was created by the person named in the passport.
Your network
Traffic is up to you
The checking process is tuned to your network’s figures. These four metrics are visible from session exports, and each has a decision attached.
How many webmasters got from the “Withdraw funds” button to payout. A drop shows that a tier is too strict or the screen is unclear.
How many disputed sessions arrived and how many were reviewed per shift. A growing queue is a reason to adjust the threshold or add an operator.
Refusals are grouped by code: “document from a screen”, “data does not match”. A frequent reason is a hint for the on-screen text.
How many new accounts matched a document number from the ban list. A match goes to review, and the threshold is tightened where there are many.
Each check is enabled separately — for the tier and the payout amount. Payment is for completed requests. All database checks are in AML checks catalogue.
Document and status
Without manual entry.
A Russian passport and documents from 195+ countries and territories are recognised from a photo: full name, date of birth and document number arrive as response fields. Anti-fraud flags a screen photo, a printout and editing in an editor.
from 16 ₽
Learn moreThe INN is found from the passport data, without namesakes. Needed for the payout register.
5 ₽
Learn moreChecks the professional income tax status as of the check date: it determines who pays tax on the payout.
5 ₽
Learn moreThe passport is not listed as lost, replaced or invalid — per the Ministry of Internal Affairs database.
5 ₽
Learn moreFace, watchlists, company
Before a large sum. Each database check — 5 ₽.
Liveness tells a live person from a photo, a screen and a mask; matching shows that the selfie and the photo in the document are the same person. Once, in the same session; there is no search of a face database.
from 29 ₽ per session
Learn moreScreening against the list of persons involved in extremist activity or terrorism — at the network’s decision, for example before a large sum.
5 ₽
Learn moreA check against the sanctions lists of the USA, the European Union, the United Kingdom and the UN — on each list update.
5 ₽
Learn moreStatus, head and founders of the partner company. The representative goes through their own session from tier 2.
on request
Learn moreYou pay for each document recognised and for each database check. There is no subscription fee: the more checks per year, the lower the price.
A Russian passport or a document from 195+ countries and territories without manual entry, antifraud. For the first withdrawal.
from 29 ₽ per session
Everything from “Document”, plus Liveness and a selfie match against the document photo. For large payouts and changes of payout details.
5 ₽ per check
Tax ID (INN) from the passport, self-employed status, passport validity. International screening — 36 ₽.
A self-employed person’s first withdrawal — document, tax ID (INN) and status: from 26 ₽ (16 + 5 + 5). One session — one person: a company representative goes through their own. At 10 000 checks per year, a “Document” session — 18 ₽ by the calculator. Checking a company by tax ID (INN) — on request.
KYC for an affiliate programme goes in three places: the “Withdraw funds” button, the payout register and the link a manager sends to a webmaster.
Trial period — 1 month; payment for completed checks; the data retention period is set in the scenario; support via a ticket system.
A payout team needs identical data for every partner, a clear queue of disputed cases and a supplier that does not get in the way of honest webmasters.
Recognition, antifraud, tax ID (INN) and status arrive as one result, and disputed cases are gathered into a queue. The manager stops asking for passport photos in messengers, and the operator sees everything in one card.
There is no need to assemble a solution from several vendors and reconcile their responses.
A short guide to the terms used when setting up webmaster checks. CPA and advertising record terms are in the glossary of the section’s main page.
Self-employed persons, counterparty checks, antifraud and deepfakes — in our blog.
A partner check is establishing the identity of the person who withdraws money: document, face in the check, tax ID (INN) and tax status. Verifying site rights in a search engine is confirming ownership of a site, which is a different task. What exactly to check about a webmaster under the advertising records law is covered on the section’s main page.
Do not ask for a document at registration. Registration is an email and a nickname; the passport comes before the first withdrawal; Liveness before a large sum; a new session when payout details change. Disputed cases go to an operator, not to an automatic refusal.
You set the threshold: start with a sum whose loss would be noticeable for the network, and check it against your payout history. Below the threshold, a document, tax ID (INN) and status are enough; above it, Liveness with a face match against the document photo is added. The threshold can be changed by a rule in your system without changing the scenario.
Show the reason: “photo of a screen”, “data does not match the profile”, “document has expired”. A blurry frame is a reason for a second attempt via a new link. If doubt remains, the session goes to manual review, and the payout waits for the decision.
Sessions with the status “Suspicion” are gathered into a queue. The operator opens the card: document, selfie, check results and the reason for refusal, and changes the status in one action. The log records who made the decision, when and why. You build the queue with an owner and a deadline in your own system from the webhook.
No. The network checks the quality of clicks and leads by its own means. An identity check covers the withdrawal of money: accounts after a ban, money mules, other people’s data.
By the document number from the check: NeuroVision returns it as a response field, and your system compares it with the ban list and other accounts. We do not search for a duplicate by face: a face database search is restricted by Federal Law No. 572‑FZ.
Desirable: the status is needed as of the payout date, and the webmaster may have stopped applying the professional income tax. The check costs 5 ₽. An organisation that pays an individual is a tax agent for personal income tax (NDFL) (clause 1 of Art. 226 of the Tax Code), and your accounting calculates the tax.
Yes. Each tax ID (INN) goes as a separate request via REST API, your system sends the whole register, and the results arrive by run identifier. Refusals and disputed cases are visible before the money is transferred.
A document from 195+ countries and territories is recognised without manual entry, and the name in Latin script is taken from the machine-readable zone. Tax ID (INN) and self-employed status are checked only for Russians.
Web SDK is embedded in the account area, SDK for iOS and Android in the app, a one-time link is sent by a manager, and REST API connects to your system. “Document” is from 16 ₽ per session, “Document + Liveness” from 29 ₽, database checks 5 ₽ each. The trial period is 1 month.
In Russia: in the NeuroVision cloud or on your servers when installed inside your perimeter as a set of Docker containers. The retention period is set in the scenario; personal data is stored no longer than the purpose of the check requires (Part 7 of Art. 5 of Federal Law No. 152‑FZ).
Tell us how many webmasters withdraw money per month and in what amounts. We will select the tiers, thresholds and set of checks, 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 callThe 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.