...

Checking CPA‑network webmasters: trust tiers, payout thresholds and manual review

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.

Three webmaster check tiers: document, face, status — payout ready
from 16 ₽ webmaster’s document and antifraud per session
5 ₽ INN by passport or self-employed status — per check
from 29 ₽ document, Liveness and matching the face with the photo in the document
195+ countries and territories — webmasters’ documents
Passport without entry Document anti-fraud Liveness INN and self-employed Manual review

Data stored in Russia · Russian software registry no. 19972 · 152‑FZ

Contract, tax and webmaster data: what the “payout after verification” rule rests on

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.

  • Contract

    Civil Code of the Russian Federation, Arts 428, 437, 438

    Connection

    Rules as an offer

    • The webmaster accepts the programme rules in full
    • The verification condition must be written down before registration

    Consent by conduct

    • Registering in the account is an act under the terms of the offer
    • Acceptance is confirmed by a log

    Not forever

    • A party that has joined is entitled to contest clearly burdensome terms
    • The wording is agreed by the network’s lawyer
  • Payout and tax

    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

    Self-employed status

    An individual

    • The paying organisation is a tax agent
    • Personal income tax is withheld at the time of payout

    A self-employed person

    • The webmaster pays the tax themselves and issues a receipt
    • The status is needed on the payout date

    Name from the passport

    • Full name and tax ID (INN) from the check go into the payout register
    • Payout details are matched against the name
  • Webmaster data

    Federal Law No. 152‑FZ, Art. 9, Parts 5 and 7 of Art. 5

    Webmaster’s document

    Consent

    • The passport is processed with the webmaster’s consent
    • Before the session starts

    No more than needed

    • The data set matches the purpose of the check
    • Extra fields are not collected

    Deadline

    • Storage no longer than needed for the purpose
    • The period is set in the flow

Payouts, antifraud, affiliate management, account area, accounting: who in the network is responsible for checking a webmaster

Checking a webmaster touches five roles. If you do not divide what each one does, it belongs to nobody and payouts wait.

  • Head of payouts or a partner payout service

    • Sets the withdrawal thresholds and the schedule
    • Decides which sums pass without manual review
    • Looks at the “received — reviewed” report at the end of the shift
  • Antifraud analyst

    • Maintains the  ban list by document number
    • Matches a new account against blocked ones
    • Reviews sessions with the status “Suspicion»
  • Affiliate manager

    • Sends the webmaster a link to the session
    • Explains the reason for a refusal in their own words
    • Brings valuable partners to a second attempt
  • Account area product owner

  • Accounting and lawyer

    • Receive the tax ID (INN) and status as of the payout date
    • Fix the terms in the programme rules
    • Are responsible for the self-employed receipt and personal income tax (NDFL)
  • A payout manager’s workplace: a laptop with an empty table, a smartphone and a notepad

CPA‑network partner check tiers: what to request at registration, first withdrawal, a large sum and a change of payout details

Six tiers from registration to a company partner. This is an example configuration: you set the events and sums for each tier.

  • Registration

    Email, nickname and site — without a document, so as not to lose honest webmasters.

    Withdrawal is closed until the person passes the second tier.

    • without a document
  • First withdrawal

    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.

    • from 16 ₽
  • Withdrawal above the threshold

    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.

    • from 29 ₽
  • New details

    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.

    • from 29 ₽
  • Every payout

    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.

    • 5 ₽ per check
  • Company partner

    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.

    • on request

Check result and account action: the webmaster passed, failed or ended up in disputed

The check answers the question “who is this person”. What to do with the answer is decided by your system’s rule.

Step 1

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.

A webmaster photographs their passport with a phone, and the result goes to the network’s account area
Step 2

Your system’s rule

The system matches the result to the tier: the document number is matched against the ban list and other accounts, the name against the payout details owner, the sum against the threshold. Three outcomes: pass, refuse, send for review.

The check result is matched to a tier: three outcomes — payout, refusal, review
Step 3

Action and message

Passed — the payout goes to the queue. Failed — the webmaster gets a clear reason and a second attempt. Disputed — the session goes to the manual review queue with a deadline and an owner.

Webmaster card: checks passed, payout queued

Too early, too late, a queue on payout day, an outdated status: where the checking process breaks

The check comes before the transfer

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.

  • 01

    Document at registration

    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.

  • 02

    Check after payout

    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.

  • 03

    Queue on payout day

    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.

  • 04

    Status as of yesterday’s date

    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.

  • 7 session statuses — any of them can be set manually
  • 5 ₽ self-employed status or tax ID (INN) from the passport as of the payout date
  • 1 session one person: a company representative goes through their own

Setup checklist: programme rules, scenario, manual review and payout register

Four groups, sixteen lines. A tag shows who closes the line: our check, your network or accounting.

  • The “payout after verification” condition is written in the rules before registration Your network
  • The list of documents and the reasons for refusal are described for the webmaster Your network
  • Consent to processing of passport data is obtained before the session starts Your network
  • The data retention period is set in the scenario NeuroVision

  • Sessions with the status “Suspicion” go into the queue NeuroVision
  • The operator sees the frames, results and the reason for refusal in one card NeuroVision
  • An owner and a review deadline are assigned Your network
  • The decision and reason are recorded in the log NeuroVision

  • INN and self-employed status checked as of the payout date NeuroVision
  • The payout details are registered to the name from the passport Your network
  • The self-employed receipt is received or personal income tax (NDFL) is withheld Accounting
  • The document number is matched against the ban list and other accounts Your network
  • NeuroVision  — the line is closed by NeuroVision: recognition, antifraud, Liveness, face match against the document photo, manual review and database checks
  • Your network  — a line for your network: programme rules, thresholds, the person responsible for review, payout details, ban list
  • Accounting  — an accounting line: self-employed receipt and personal income tax (NDFL)

An honest webmaster under check: when to ask for a document, what to tell them and how to give a second attempt

  • When

    Ask for the document where money appears: at the “Withdraw funds” button, not at registration. Before a large sum — Liveness.

  • What to say

    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”.

  • Second attempt

    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 person is available

    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.

Pass rate, manual queue, refusal reasons, repeats: which metrics the head of payouts should watch

The checking process is tuned to your network’s figures. These four metrics are visible from session exports, and each has a decision attached.

  • Pass rate

    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.

  • Manual queue

    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.

  • Reasons for rejection

    Refusals are grouped by code: “document from a screen”, “data does not match”. A frequent reason is a hint for the on-screen text.

  • Repeats

    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.

What to enable at each tier: checks and prices

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.

  • Recognition · anti-fraud

    A Russian passport and documents from 195+ countries and territories

    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 more
  • Federal Tax Service

    INN by passport

    The INN is found from the passport data, without namesakes. Needed for the payout register.

  • Federal Tax Service

    Self-employed status

    Checks the professional income tax status as of the check date: it determines who pays tax on the payout.

  • Police

    Validity of a Russian passport

    The passport is not listed as lost, replaced or invalid — per the Ministry of Internal Affairs database.

How much a check tier costs

You pay for each document recognised and for each database check. There is no subscription fee: the more checks per year, the lower the price.

  • Most popular choice

    Document

    from 16 ₽ per session

    Calculate

    A Russian passport or a document from 195+ countries and territories without manual entry, antifraud. For the first withdrawal.

  • Document + Liveness

    from 29 ₽ per session

    Enable

    Everything from “Document”, plus Liveness and a selfie match against the document photo. For large payouts and changes of payout details.

  • Database checks

    5 ₽ per check

    Build a set

    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.

Withdrawal request, register before payout day, manager’s account area: where the check is launched

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.

Withdrawal request

Web SDK is embedded in the account area, SDK for iOS and Android — in the network’s mobile app. The account area creates a session when the webmaster presses “Withdraw funds” and receives the result by webhook. The logo, colours and texts are configured for the network. Documentation

  • Web SDK
  • iOS and Android
  • REST API
  • Link
  • Docker

Test period — 1 month

Trial period — 1 month; payment for completed checks; the data retention period is set in the scenario; support via a ticket system.

What changes in the payout team’s work with NeuroVision

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.

One session instead of correspondence with the webmaster

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.

Document Liveness Tax number API

Documents of 195+ countries and territories

Webmasters from other countries.

Decision log and report exports

A basis for the per-shift reconciliation.

Data in Russia

Cloud or installation in your environment, 152‑FZ.

Payment for the checks performed

From 16 ₽, no subscription fee. A Russian developer, Russian software registry entry No. 19972.

Tier, threshold, register, manual review: the payout team’s glossary

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.

Check tier
A stage in a webmaster’s life at which the network asks for a certain set of confirmations: registration, first withdrawal, a large sum.
Verification tier
Withdrawal threshold
The payout amount from which the next check tier is required. Set by the network.
Payout threshold
Payout register
A list of webmasters and sums that the network transfers on payout day.
Payout register
Manual review queue
Sessions that the automation cannot decide itself and passes to a staff member.
Manual review queue
Ban list
A list of document numbers and accounts for which the network has closed withdrawal for breaking the rules.
Ban list
Drop
A front person in whose name an account or payout details are set up, while someone else receives the money.
Money mule
Account farm
Many accounts of one person used to get around limits and thresholds.
Account farm
Session status
The outcome of a check in the account area: passed, refused, suspicion and others. Any of them can be set manually.
Session status
Repeating the check
A new “document and Liveness again” session when payout details change or on a large payout.
Re-verification
Single-use link
The address of a checking scenario for one webmaster with a validity period; the manager sends it in an email.
One-time link

Questions about checking webmasters and CPA‑network partners

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).

We will set up check tiers for your CPA‑network

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 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.