Government
1. «Antifrod» state system
The operator is the Ministry of Digital Development, the platform is GosTech. It generates a signal under the agreed scenario.
The PODD agent for SMEV 4: how a bank exchanges signals with the «Antifrod» state system
The PODD agent, also called the SMEV 4 agent, is a standard program that a participant installs inside its own perimeter. Through it the bank receives signals from the «Antifrod» state system and sends back its responses. We explain how the channel works, what to prepare and where a connection most often breaks.
Data stays in Russia Cloud or your own perimeter Russian Software Registry No. 19972
SMEV 4 PODD: what it is and why a bank needs an agent
-
What SMEV 4 is
The System of Interdepartmental Electronic Interaction, fourth generation (Government Decree No. 697 of 08.09.2010). Besides requests and responses it works with data showcases and REST services. Participants exchange data with the «Antifrod» state system through SMEV 4.
-
PODD — the data access subsystem
The transport part of SMEV 4: it verifies the participant, routes messages and grants access to data under registered rules. The PODD core runs on the government side — a participant does not need to install it.
-
The PODD agent, or SMEV 4 agent, — what the bank installs
Standard software inside the participant's perimeter, called the «SMEV4 Agent» in the documentation. It confirms that the bank's information system is a participant, signs messages with a certificate using GOST cryptography, receives signals from the state system, sends responses and passes data to the bank's internal system.
The agent only delivers the signal.
The decision — hold the transfer or pass it to an analyst — is made by the bank's anti-fraud system.
The signal path: from the «Antifrod» state system to the bank's anti-fraud system
A signal passes through three zones: the government zone, the SMEV 4 channel and the bank's perimeter. The state system operator and the SMEV operator are responsible for the first two; the third is the bank's responsibility. The bank's response returns along the same path: anti-fraud system → adapter → PODD agent → PODD core → «Antifrod» state system. How NeuroVision handles signals from the state system
SMEV 4 channel
2. PODD core
Verifies the participant and routes the message.
SMEV 4 channel
3. Secure channel
The test environment works over the internet, production over a secure data network.
Bank perimeter
4. PODD agent
Authenticates over GOST TLS, receives the signal and signs the response.
Bank perimeter
5. Bank adapter or REST service
Converts the signal to the internal format and distributes it to systems.
Bank perimeter
6. Anti-fraud system
Factors the signal into risk together with customer checks and transaction history.
Bank perimeter
7. Core banking, remote banking, log
They carry out the decision and record that the signal was received and handled. The bank must report failures to the state system operator without delay (clause 11 of Government Decree No. 200).
What to prepare before connecting to SMEV 4
Six conditions without which the agent will not work. Most of them are prepared in advance by the bank's IT and information security teams, before the Ministry of Digital Development notifies the bank about connecting to a scenario.
-
Organisation in ESIA
- A legal entity account and an authorised employee
- This is how you sign in to the participant account (LK UV)
-
Information system in SMEV 4
- The bank's IS is registered in the participant account and has received a role in SMEV 4
- The IS mnemonic is its «login» in the agent configuration
-
Certificate and cryptographic tools
- An electronic signature certificate for the IS with a full chain up to the certification authority
- A CryptoPro CSP licence on the agent server
-
Server or virtual machine
- The agent is installed from a ready-made package with a Docker image
- The portal recommends allocating up to 8 GB of memory to the container if the agent does not start
-
Network and access
- Ports 6650–6680 open to SMEV 4 addresses and 443 for authentication
- A secure data network for the production environment
-
Accurate time and a log
- Synchronise via NTP: if the time drifts, the agent gets a token error
- A log of the agent and signal handling — to answer the state system operator about failures
SMEV 4 test and production environments
- Purpose
- Channel
- Message exchange
- Agent authentication
- Time synchronisation
- IS certificate
- How to get access
- Purpose
- Channel
- Message exchange
- Agent authentication
- Time synchronisation
- IS certificate
- How to get access
- The agent is first connected to the test environment: «SMEV4 Quick Start» in the participant account issues a ready-made agent package with the configuration, and the configuration, certificate and exchange are checked there. The information system is copied to the production environment separately: access to the closed segment of the secure data network (ZSPD) follows the connection procedure, and the agent must hold the same certificate that is registered for the production IS in SMEV 4.
- We do not publish production IP addresses on this page: they change and are issued under the connection procedure. The current list is in an article on the SMEV portal «Current addresses for calling SMEV4».
- No trial period is set by regulation: it depends on the scenario and the bank's readiness.
SMEV 4 connection: a 10-step technical checklist
The order for a bank connecting to SMEV 4 from scratch. If the bank already works with SMEV 3, steps 1–3 are usually done — start from step 4. The organisational steps — notifying the Ministry of Digital Development and agreeing the scenario — are covered on the page about connecting to the state system.
Step 1
Registering the organisation in ESIA
A legal entity account and an authorised employee who will act on behalf of the bank.
Step 2
Applications for joining
Applications for joining and registering a participant are submitted through the personal account on the Situation Centre website.
Step 3
Secure channel
A channel to the e-government infrastructure and cryptographic equipment that meets the requirements for the participant network.
Step 4
Participant account (LK UV)
Access for the authorised employee; choosing the organisation in the account.
Step 5
Information system and role
Registering the bank's IS, a role in SMEV 4 and an electronic signature certificate for the IS.
Step 6
Access to the state system's data type
Access to the «Antifrod» service or registration of the bank's own REST service — as the scenario requires.
Step 7
Installing the agent in the test environment
«SMEV4 Quick Start» in the participant account issues an agent package with a ready configuration and a Docker image.
Step 8
Checking the connection
A test request to the agent core. A response without an error means the agent is online.
Step 9
Integration and trials
The bank's adapter or REST service, signal routing to anti-fraud, sending the response, the log.
Step 10
Moving to the production environment
Copying the IS to the production perimeter, the production certificate, access to the closed segment, enabling the scenario.
Steps 1–5 and 7–8 are the same for any SMEV 4 participant. What is specific to the «Antifrod» state system starts at steps 6 and 9: which signals arrive, which responses the bank is expected to send and how fast. These two steps decide whether the connection turns into working anti-fraud or stays a formality.
Typical PODD agent errors and how to fix them
-
Invalid Client Credentials— wrong IS mnemonic, or the IS has no role in SMEV 4 -
Certificate provided in request not matched— the agent holds a different certificate from the one registered in SMEV 4 -
unable to find valid certification path— the key container lacks the full chain up to the certification authority -
0x8010002C— when reading the key: the private key has expired -
connection refused, «No active connections» — SMEV 4 ports or addresses are unreachable -
JWT is not active— the agent server clock differs from SMEV -
License has expired— the CryptoPro CSP trial licence has expired - the agent shuts itself down — an agent with the same IS mnemonic is running on another machine
- the container crashes at start — the agent does not have enough memory
- Systems get confused — the «Antifrod» state system under 41‑FZ, Roskomnadzor's «Antifrod» and the Government Decree No. 1344 mechanism are three different circuits. The requirements of one system end up in the project of another
- A formal integration — the signal is accepted and stored, the response is sent, but the bank's decisions do not change
- No handling log — the bank cannot show that a signal was received and taken into account, and will not notice a failure
- Format errors are found in production — responses fail validation on the state system side
- One agent for everything, with no standby — a server stop is an exchange stop
- Start-up errors are described on the SMEV portal: almost all of them come from configuration, the certificate or the network. The full list with codes is in the article «Typical SMEV4 Agent errors». If the error does not go away, file a request with the Situation Centre.
- Project errors — when the agent works, but the signals bring no value: «signal → risk → action» rules, a handling log, checking every type of signal and response in the test environment, agent monitoring.
41‑FZ and 210‑FZ deadlines: by what date the agent must work
There is no single «connect the agent by…» deadline for all banks. The channel is needed by the date the bank connects to a state system scenario, and from 2027 — for mandatory data submission. A detailed analysis of the rules is in the blog article.
-
01.03.2026 — the state system is live
The «Antifrod» state system was put into operation (41‑FZ); its data is used when checking transfers — indicator 1.2 of Bank of Russia Order OD-2506. Banks join scenarios on notification.
-
30 days after the scenario is agreed
The Ministry of Digital Development notifies participants about connecting to a scenario (clause 15 of Government Decree No. 200). From that date a working channel and signal handling are needed; the clause sets no deadline for the connection itself.
-
01.03.2027 — data submission
Banks must submit data to the state system (210‑FZ): the channel is needed not only for receiving but also for sending.
-
31.08.2026 — not about the state system
The deadline for banks to connect to SMEV under Government Decree No. 1344 has expired — this is a different mechanism: replies to requests from authorities. If the agent is installed for both exchanges, check at once which IS and roles each one needs.
Who is responsible for what during the connection
Connecting to the state system is the work of three parties. The earlier the roles are assigned, the fewer pauses there are between test and production.
-
Bank IT and information security
ESIA, the participant account, IS registration and certificates; the server, network, secure channel and cryptographic tools; installing and maintaining the PODD agent.
-
SMEV integrator
A turnkey agent installation if the bank has no team of its own; an adapter between the agent and the bank's systems; trials in the test environment.
-
NeuroVision
«Signal → risk → action» rules for each scenario; state system signals in risk scoring alongside customer document checks and repeat registrations; a handling log and failure alerts.
Glossary: SMEV 4, PODD, LK UV and other terms
Terms that appear in SMEV 4 documentation and in correspondence with the state system operator.
- The «Antifrod» state system
- The state information system for countering offences committed using information and communication technologies. Established by 41‑FZ; the operator is the Ministry of Digital Development.
- Scenario
- The exchange rule in the state system: who sends a signal, who receives it and what they do. Approved by the Ministry of Digital Development in agreement with the FSB, and for banks also with the Bank of Russia.
- Signal and response
- A signal is information about signs of fraud that the state system passes to a participant; a response is the participant's reply about what was done.
- SMEV
- The System of Interdepartmental Electronic Interaction (Government Decree No. 697 of 08.09.2010).
- SMEV 4
- The fourth generation of SMEV: requests, data showcases and REST services.
- PODD
- The SMEV 4 data access subsystem — the transport part that verifies the participant and routes messages. Other expansions («document access», «platform for exchanging data on droppers») — are errors.
- PODD agent (SMEV 4 agent)
- Standard participant software installed in its perimeter that connects its information system to PODD. The distribution package and the administrator's manual are on the SMEV portal, in the «Software for SMEV participants» section.
- PODD core
- The central part of PODD on the SMEV operator's side.
- ESIA
- The Unified Identification and Authentication System. An organisation registers in it to sign in to the participant account.
- LK UV
- The interaction participant's account: registering the IS, certificates, access rights and «Quick Start».
- IS UV
- The interaction participant's information system. All exchanges are made on its behalf.
- Mnemonic
- A unique IS identifier in SMEV 4; set in the agent configuration and case-sensitive.
- Data type
- A set of data registered in SMEV that participants exchange.
- Regulated request
- A request registered in PODD that a consumer calls by its mnemonic.
- Data showcase
- A provider's storage from which SMEV 4 serves data to consumers. A bank usually does not need it for the state system.
- Test and production environment
- A debugging environment (access over the internet) and a permanent-operation environment (access over ZSPD).
- ZSPD
- The secure data network over which the production environment runs.
- GOST TLS
- A secure connection built on Russian cryptographic algorithms; the agent authenticates over it.
- SKZI
- A cryptographic information protection tool; for the agent it is CryptoPro CSP.
- Situation Centre
- The SMEV participant support service: joining applications and error requests.
Read also
State system regulation and anti-fraud practice — in our blog.
362 16
Anti-Fraud, Liveness and Deepfake Protection
Implementing an anti-fraud system: a step-by-step plan from pilot to production
351 15
Anti-Fraud, Liveness and Deepfake Protection
Anti-fraud system: architecture and real-time fraud monitoring
386 19
Anti-Fraud, Liveness and Deepfake Protection
Fraud Metrics: How to Measure the Effectiveness of an Anti-Fraud Architecture
119 28
Anti-Fraud, Liveness and Deepfake Protection
What Is a Deepfake: How It Works, Why It’s Dangerous for Business, and How to Protect Yourself (2026)
Frequently asked questions about the PODD agent
In brief about the agent, SMEV 4 and connecting to the state system.
The PODD agent is a standard SMEV 4 program that a participant installs inside its own perimeter. PODD stands for «data access subsystem». Through the agent a bank receives signals from the «Antifrod» state system and sends responses.
Yes. The SMEV portal documentation uses both names, as well as «SMEV4 Agent» without a space. They all refer to one program.
On the SMEV technology portal, in the «Software for SMEV participants» section: the administrator's manual and configuration samples are there too. For the test environment, a ready package is issued by «SMEV4 Quick Start» in the participant account.
An organisation in ESIA, a participant account, a registered information system with a role and a certificate, a CryptoPro CSP licence, a server for the agent and network access. The production environment also needs a secure channel.
Yes. A SMEV 3 connection shortens preparation — ESIA, the channel and cryptographic tools are already in place — but for SMEV 4 the information system is registered separately and the agent is installed.
In the test environment the agent connects over the internet and the certificate can be generated in the participant account. Production runs over a secure data network, with a production certificate and closed-segment addresses.
Most often the information system mnemonic is wrong or the system has no role in SMEV 4. Check the mnemonic against the participant account, remembering that it is case-sensitive.
There is no regulatory deadline: it depends on whether the bank already has ESIA, a channel and certificates, and on the scenario requirements. The 31.08.2026 deadline from Government Decree No. 1344 relates to a different mechanism, not to the «Antifrod» state system.
No. The agent is installed by the bank or its SMEV integrator. NeuroVision is responsible for what happens after the agent: signal handling rules, factoring signals into risk, and the log.
Pass it to the anti-fraud system, factor it into risk together with customer checks and transaction history, make a decision and send a response. The bank must immediately report any failure in receiving or handling data to the state system operator.
Let's discuss what to do with signals after the agent
Tell us which step you are at: the agent is not installed yet, runs in test or is already in production. We'll suggest how to build state system signals into your bank's anti-fraud.
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.
