The Ministry of Digital Development (Mintsifry) notifies a bank that it needs to connect to a GIS Antifrod scenario — and then begins what none of the materials at the top of the search results describe: the specific procedure. Whom to contact, whether SMEV 4 is needed or whether it can be done without it, what the mysterious “PODD” means, how long it will take, and what actually happens after the system sends the first signal. We break this down step by step — based on Federal Law No. 41-FZ, Government Resolution No. 200, and the SMEV 4 technical documentation, rather than on other publications retelling each other.
What Happened: The Launch of GIS Antifrod on 1 March 2026
Since 1 March 2026, Russia has had a state information system that everyone — from journalists to vendors — calls “GIS Antifrod.” Its official name is much longer and drier: “the state information system for countering offenses committed using information and communication technologies.” It is created not by the law usually cited in cybersecurity news (210-FZ), but by Federal Law No. 41-FZ of 1 April 2025 — it was its Article 1 that entered into force on 1 March 2026 and put the system into operation.
Official Name and Operator (Mintsifry, GosTech)
Under Article 1(3) of 41-FZ, the operator of the GIS is Mintsifry, and the technical platform is GosTech (this is expressly established in clause 2 of Government Resolution No. 200 of 27 February 2026, which approved the Regulations on the system). The Regulations were agreed with the Federal Security Service (FSB) and describe 29 clauses on how the system works — from the composition of participants to the procedure for approving scenarios.
According to Kommersant, a month after the launch, only organizations that had participated in the pilot mode were connected to the platform, and only certain elements of the system were working. An estimate of the project’s final scale — about 2,500 organizations at the first stage and at least 20,000 in the long term — was given to the same publication by an anonymous market source; Mintsifry has not publicly confirmed this figure. The officially verifiable scale benchmark is different: according to the office of the Deputy Prime Minister, as of 18 June 2026, 12 organizations were connected to the GIS, including the largest banks and telecom operators. This is worth keeping in mind when planning integration: a bank that has received a notice to connect is one of the participants in a gradually deploying system, and their number will grow.
How the GIS Differs From the GRChTs Telecom “Antifrod” and From FinCERT
It is worth setting boundaries right away, because confusing the systems is the most common mistake in the materials already available online. Even the page ranking first for the query “connecting to GIS Antifrod” in fact describes a different system — the telecom “Antifrod” of the Main Radio Frequency Center (GRChTs), which is regulated by separate communications legislation (in particular, Article 46.1 of Federal Law No. 126-FZ, the communications law) and has nothing to do with 41-FZ.
Exchange of signals about signs of unlawful actions between government bodies, banks, and telecom operators (41-FZ, Resolution No. 200). Operator — Mintsifry.
Filtering fraudulent calls and number spoofing at telecom operators (regulated by communications legislation, including Article 46.1 of 126-FZ). Operator — GRChTs (Roskomnadzor).
The Bank of Russia’s information exchange with credit institutions on information security incidents in the financial sector. Operator — the Bank of Russia.
The difference is fundamental: GIS Antifrod is an interagency loop for exchanging signals, FinCERT is a banking loop for exchanging information on incidents, and the telecom “Antifrod” is about calls and SIM cards. Mixing them up in an integration specification means building in the requirements of the wrong system — and redesigning the connection architecture after it has already been built.
Whom It Affects: Banks and Other Participants
Users and Participants (Resolution No. 200, Clause 9)
Clause 9 of the Regulations lists the participants in a closed list: the Ministry of Internal Affairs (MVD), the Federal Service for Technical and Export Control (FSTEC), Roskomnadzor, the Federal Financial Monitoring Service (Rosfinmonitoring), the FSB, the Prosecutor General’s Office, the Investigative Committee, the Bank of Russia, credit institutions and telecom operators, and, separately, the National Computer Incident Coordination Center (NKTsKI). This clause defines the circle of the system’s participants, not whether their connection to a specific scenario is mandatory — that is regulated separately, by clause 2 of the Regulations. Messengers, hosting providers, social networks, and classified ad services may also connect to the system on a voluntary basis.
Formally, participation in a specific GIS scenario for credit institutions and telecom operators — as for other, non-governmental participants that connect voluntarily (messengers, hosting providers, social networks, classified ad services) — is designated as voluntary in clause 2 of the Regulations. This does not apply to the government bodies listed in clause 9 (MVD, FSTEC, Roskomnadzor, Rosfinmonitoring, FSB, the Prosecutor General’s Office, the Investigative Committee, the Bank of Russia) or to NKTsKI: their participation in the GIS follows from their state functions, not from a voluntary choice of a specific scenario. The voluntary nature of scenario participation does not release a bank from its own obligations that are already in force: the banking law (as amended by 41-FZ), Bank of Russia Order OD-2506, and, from 2027, 210-FZ require the bank to use and transmit certain information regardless of whether it has connected to a specific GIS scenario. Further in the text, these three levels — participant status, the voluntary nature of a scenario, and the bank’s own obligations — are kept separate: confusing them means either overestimating the urgency or underestimating requirements that are already in force.
Banks’ Obligations Under 41-FZ
41-FZ amends the banking law (Article 2), and some of these amendments directly affect the bank’s technical architecture, not only its participation in the GIS:
| Provision | What it requires |
|---|---|
| Article 9(10) | Provide information at the request of operational-search/security bodies via SMEV (implemented by a separate mechanism — Resolution No. 1344) |
| Article 24.3-1 | Check for signs of cash withdrawal without the customer’s voluntary consent; a withdrawal limit of ₽50,000 per 48 hours when triggered |
| Article 30(16) | A withdrawal limit of ₽100,000 per month upon receipt of the relevant data from the Bank of Russia |
| Article 30(17) | A ban on using foreign messengers to inform individual customers |
| Article 30(19)–(29) | The “authorized person” mechanism — confirmation of transactions, a delay of up to 12 hours |
| Article 31(4) | Storage of copies of powers of attorney for at least 5 years |
We’ll tell you which obligations under 41-FZ and 210-FZ apply to you and where to start connecting to GIS Antifrod
The 2026 Regulatory Framework
Before discussing the connection procedure, it is worth establishing which act is responsible for what — otherwise it is easy to confuse the 2026 requirements with obligations that will take effect only in 2027.
| Act | What it means for the bank |
|---|---|
| 41-FZ (1 April 2025) | Creates the GIS; the operator is Mintsifry; amends the banking law (Article 2) |
| Resolution No. 200 (27 February 2026) | Regulations on the GIS: participants, types of information, procedure for approving scenarios, 30-day notice, agreement of banking scenarios with the Bank of Russia |
| Bank of Russia Order OD-2506 (5 November 2025) | 12 indicators of a transfer without the customer’s voluntary consent; indicator 1.2 (information from the GIS) — applies from 1 March 2026 |
| Resolution No. 1344 (30 August 2025) | A separate mechanism — rules for banks’ responses to SMEV requests from operational-search/security bodies. This is not GIS Antifrod, although the channel is technically similar |
| 210-FZ (26 June 2026) | “Antifrod 2.0”: provisions on the GIS — from 1 March 2027 (transmission of information about subscriber numbers, expansion of the mandatory use of data, reimbursement, IMEI) |
| Bank of Russia Letter No. 56-5-1/753 (30 January 2026) | Clarification: connection to the GIS is initiated by Mintsifry; confirms the date of 1 March 2026 for indicator 1.2 |
Liability for non-compliance is separately established in the regulations — Article 74 of the law on the Bank of Russia (86-FZ), which gives the Bank of Russia grounds for supervisory measures. This is confirmed by the same Letter No. 56-5-1/753.
Roadmap for Connecting to GIS Antifrod
The most common confusion in materials on this topic is mixing up the deadlines of the GIS itself (2026) with the deadlines of “Antifrod 2.0” under 210-FZ (2027). Let’s separate them by date:
| Date | What happens |
|---|---|
| 1 March 2026 | The GIS is put into operation; indicator 1.2 of OD-2506 begins to apply (41-FZ, Article 16(5); Letter No. 56-5-1/753) |
| 1 March 2026 | Resolution No. 1344 enters into force — banks respond to operational-search requests via SMEV |
| 30 days after the FSB agrees a scenario | The operator (Mintsifry) notifies participants of the need to connect to a specific scenario; the clause does not set a deadline for the participant’s connection itself (Resolution No. 200, clause 15) |
| 31 August 2026 | The 6-month deadline for banks to connect to SMEV under Resolution No. 1344 expires, counted from the date the act entered into force (1 March 2026) |
| 1 September 2026 | The unified payment card accounting system is launched (operator — the National Payment Card System (NSPK), 210-FZ, Article 11) |
| 1 March 2027 | The obligations of 210-FZ enter into force: transmission of information to the GIS; expansion of the obligation to use data when checking transactions — now also Bank of Russia information and information on malware; reimbursement; IMEI (210-FZ, Articles 9 and 11) |
| 1 September 2027 | A limit of 20 payment cards per customer (210-FZ, Article 11) |
Formally, a bank’s participation in GIS scenarios is voluntary (clause 2 of Resolution No. 200). But the obligation to use GIS information when checking transactions arises already from 1 March 2026 — through indicator 1.2 of Order OD-2506. From 1 March 2027, 210-FZ expands this already existing obligation — adding to indicator 1.2 the mandatory use of Bank of Russia information on transfers without consent and information on the impact of malware — and introduces a separate, broader obligation to transmit information to the GIS. These are three different levels of obligation, and in negotiations with an integrator they are worth distinguishing explicitly — otherwise it is easy either to delay the connection or to overpay for urgency where the law does not yet require haste.
Antifrod 2.0 Under 210-FZ: Deadlines and Business Obligations
Antifrod 2.0 is the second stage of the state’s fight against fraud, enshrined in Federal Law No. 210-FZ: it requires banks, telecom operators, and digital platforms to jointly detect and stop transactions made without the customer’s consent. If 41-FZ created GIS Antifrod itself and defined the procedure for exchanging signals, 210-FZ expands the circle of obligated participants and adds new obligations for business — from payment card accounting to countering social engineering.
The law was signed on 26 June 2026, and its provisions take effect in stages: some requirements apply from 1 September 2026, the main block of obligations from 1 March 2027, and the remaining provisions from 1 September 2027. This schedule gives banks and platforms time to prepare their infrastructure, but connecting to GIS Antifrod cannot be delayed: obligations arrive according to the calendar, not according to the participant’s readiness, and by each deadline the integration via SMEV 4 should already be working.
For banks, 210-FZ means specific actions: transmitting information about suspicious transactions to the system, suspending certain transfers for up to six hours for additional checking, and rejecting them if signs of malware are detected on the customer’s device. A separate block of requirements is devoted to accounting for issued payment cards and identifying cards used to withdraw stolen funds.
Digital platforms, marketplaces, and telecom operators connect to the same loop and are required to check participants and transactions on their side. In effect, 210-FZ turns a one-time connection to GIS Antifrod into an ongoing process: the bank does not simply integrate via SMEV 4 once but builds the exchange of signals into its daily compliance and anti-fraud monitoring. That is why the earlier a bank goes through connection and the test environment, the more calmly it meets each subsequent stage of Antifrod 2.0.
How the GIS Is Structured
Structure (Clause 5 of the Regulations)
Technically, the GIS consists of nine elements, expressly listed in clause 5 of the Regulations (Resolution No. 200):
- a centralized database of notifications about signs of unlawful actions;
- a database of persons who have committed unlawful actions using the public communications network, including the subscriber numbers used in such actions;
- a subsystem for detecting information intended to mislead and for restricting access to it;
- a subsystem for administering the participants in information interaction;
- a statistics and analytics subsystem;
- a reporting subsystem;
- a subsystem for interaction between the GIS and the MVD;
- a subsystem for interaction between the GIS and the FSB, including the technical infrastructure of NKTsKI;
- other technical and technological means (subsystems) ensuring the functioning of the system.
The law defines the interaction channel for banks and telecom operators as the “unified SMEV data access service” (the same wording as in clause 2 of Resolution No. 200), without naming a specific technology. The publicly documented variant of implementing this channel, confirmed by ESKS, is SMEV 4 with the PODD subsystem, including via REST access, which SMEV 4 also supports, and not only via regulated requests and data marts. Whether SMEV 4 is the only legally permissible way to connect is not confirmed by open sources — it is established practice, not a norm without alternatives.
Types of Information (Clause 12 of Resolution No. 200)
The Regulations describe what data participants exchange: masks of documents and TINs, IP addresses, URLs, subscriber numbers, and other identifiers tied to specific counteraction scenarios.
Counteraction Scenarios
The telecom operator transmits a signal about the termination of a contract — the bank receives grounds for additional checking of transactions linked to the number.
The indicator enters the system, and participants receive a signal for enhanced checking of the counterparty.
The bank receives a signal about an increased risk for the customer and can apply additional protective measures.
A scenario approved by the operational headquarters on 28 July 2026 for subsequent application: upon a signal from a telecom operator about a probable takeover of a customer’s SIM card, remote banking services must be suspended for a day. There is no public confirmation of its launch in production as of the publication date.
What a Bank Needs: Obligations and Architecture
From the bank’s point of view, the task breaks down into three layers: using GIS information when checking transactions (already mandatory from 1 March 2026 through indicator 1.2), receiving incoming signals and generating responses to them, and logging the processing — recording that a signal was received, processed, and that a decision was made on it. The last is not a declarative formality: clause 11 of the Regulations requires the operator to be informed immediately of failures and violations of information interaction, of information security violations, of technical problems in providing information together with the timeframes for eliminating them, and of changes in the formats of transmitted data. Without logging of processing, these obligations cannot be fulfilled correctly.
If a mature internal anti-fraud loop is in place, integration with the GIS can usually be implemented as an additional entry point for external indicators and an outgoing channel for responses, without rewriting the loop from scratch. The actual scope of modifications is determined by the architecture of the specific bank and the requirements of the chosen scenario.
Connecting to GIS Antifrod: The Sequence of Steps
Mintsifry, together with the FSB, approves the scenario; scenarios involving credit institutions require separate agreement with the Bank of Russia (clause 15 of Resolution No. 200).
The operator (Mintsifry) notifies participants of the need to connect no later than 30 calendar days from the date the scenario was agreed.
The technical documentation for connection — the SMEV 4 Connection Regulations, the PODD Agent Administrator’s Guide, and the Methodological Recommendations on PODD — is published on ESKS (info.gosuslugi.ru); the personal account of the electronic approval system is sc.digital.gov.ru, and the personal account of an interaction participant is lkuv.gosuslugi.ru.
According to ESKS documentation and the practice of connecting via SMEV 4/PODD, a bank usually needs a server to install the SMEV 4 Agent (PODD Agent), access to the SMEV environment, and certificates — this is the technical practice of a specific connection scheme, not a procedure separately prescribed by law. The specific package of documents for submitting a request is not described in the regulations, and here it is worth requesting the current list directly from ESKS or Mintsifry at the time of connection.
Within the scheme of connecting via SMEV 4/PODD, a type of information is, as a rule, tested in the test environment before the bank moves to production — the exact list of cases in which testing is mandatory is determined by the requirements of the operator of the specific scenario.
After successful testing, the bank connects to the production environment and begins receiving/transmitting signals under the agreed scenario.
It is worth planning not only for formal but also for organizational timelines: even for banks from the 2025 pilot group, only certain elements were working a month after the system’s launch, and some exchange scenarios were clarified after the fact. The fact of a staged launch in itself does not make it possible to determine the cause of a delay at a specific bank — timelines are worth planning based on the requirements of the specific scenario and the readiness of all parties.
NeuroVision covers the bank’s internal anti-fraud loop: fraud detection, liveness, and risk scoring, ready for signal exchange. We’ll show it on your scenario.
SMEV 4 and PODD
What SMEV and SMEV 4 Are
SMEV (Government Resolution No. 697 of 8 September 2010) is the basic infrastructure of interagency interaction. SMEV 4 runs on the unified information platform of the National Data Management System (EIP NSUD) (Resolution No. 733 of 14 May 2021) and supports several exchange mechanisms — regulated requests and data marts, as well as REST access (it is REST services related to the GIS that are registered in the SMEV 4 registry — see below). The exchange of information with GIS Antifrod is not limited to only one of these mechanisms.
PODD and the SMEV 4 Agent
PODD stands for the SMEV “data access support subsystem” — this is the official wording of the ESKS methodological recommendations. Some vendor documentation (in particular, Kvorum’s) expands PODD as “document access” — this is a discrepancy with the official source, and the ESKS wording should be used as the norm.
When choosing the scheme of connecting via SMEV 4/PODD, the SMEV 4 Agent (also known as the PODD Agent) is installed on the bank’s side. The exact version of the agent and its set of components are technical details of a specific build that change faster than the regulatory framework; the current state is worth checking directly against the ESKS documentation at the time of connection, rather than treating it as fixed once and for all. The ESKS technical documentation and software suppliers’ materials indicate the RSocket transport (moved to the production environment on 9 December 2025) and API GW port 8172 — this is the technical practice of a specific implementation, not a detail established by a separate regulatory act.
GIS REST Services in the SMEV 4 Registry
According to ESKS, specific REST services related to the GIS are already registered in the SMEV 4 registry: “GISAntifraud_Test” (at T2 Mobile, prefix /reactions), “NRBank. API for receiving signals from interaction participants” (prefix /signal-api/api/v1_0), and “RSHB. API for receiving signals from GIS Antifrod” (mnemonic 771602) — in ESKS terminology, “RZ release” means the publication of a regulated request into commercial operation, recorded as of 15 December 2025 for the T2 Mobile test service and as of 7 August 2026 for the NRBank service. Registration of a regulated request confirms that the interface has been put into commercial operation, but does not in itself prove the scope or fact of a specific bank’s actual production exchange of signals — this is worth checking separately, for example against data on actually connected organizations.
Test Environment → Production
Within a connection via SMEV 4/PODD, a type of information is, as a rule, first tested in the test environment — TSMEV 4, address podd.test.gosuslugi.ru — and only then released into production. Whether this step is mandatory is determined by the operator’s requirements and the chosen connection scheme, not by a separate provision of law; in practice, it is at this stage that mismatches in formats and routing logic are identified, which are more expensive to fix after going into production.
According to vendors (in particular, Kvorum), setting up a new type of information in the test environment takes about one day. This is an integrator’s estimate based on practice, not a regulatory deadline — there is no official data on testing timelines, and for project planning it is more reasonable to request a current estimate from the specific contractor.
What Happens After a Signal Is Received
Below is a typical integrator’s sequence for processing a signal for the option of connecting via SMEV 4/PODD, not a universal workflow mandatory under the regulations: the bank adapts the specific steps to its own architecture and the requirements of the chosen scenario.
Typical Mistakes and Difficulties
Warning: the most common mistake in open sources is confusing GIS Antifrod (41-FZ) with the GRChTs telecom “Antifrod” and with the Resolution No. 1344 mechanism (SMEV responses to operational-search requests). Formally, these are three different systems with different regulatory grounds and different connection deadlines — confusing them when planning integration means building the wrong requirements into the technical specification.
Besides confusion between systems, other difficulties are encountered in practice:
| Difficulty | How it shows up |
|---|---|
| Formal integration without response logic | The technical integration is done, but the response to signals is not set up in substance — signals arrive but do not change the bank’s decisions |
| Quality of return signals | The bank transmits responses that fail validation on the GIS side because of format mismatches discovered only in production, not in the test environment |
| Costs of certification and information security tools | Cost estimates diverge: for example, there is an estimate of “up to ₽180 billion” (for the industry as a whole), while Mintsifry representatives called these estimates inflated without giving an exact figure. There is no official agreed estimate as of the time the article was prepared — both figures should be presented as estimates, not as fact |
| Load on the core | Processing a stream of signals in real time requires resources that are not always built into the bank’s existing anti-fraud infrastructure; industry experts separately note that unifying APIs and protocols for thousands of heterogeneous systems of banks and operators is technically more complicated than connecting a single organization |
Liability and Reimbursement
A bank’s liability for failure to comply with requirements related to the use of the OD-2506 indicators (including indicator 1.2 from the GIS) is established through Article 74 of the law on the Bank of Russia (86-FZ) — this is the basis for the Bank of Russia’s supervisory measures.
The existing reimbursement mechanism for transfers made without the customer’s voluntary consent is already provided for by Article 9 of Federal Law No. 161-FZ (the national payment system law) and applies regardless of GIS Antifrod. From 1 March 2027, 210-FZ expands the grounds of this mechanism with respect to the bank’s new obligations — using GIS information and Bank of Russia data when checking transactions: if the conditions established by law are met, including a decision to open a criminal case, the customer may claim reimbursement — within 30 days for domestic transactions and up to 60 days for cross-border ones. Reimbursement does not occur automatically for any failure to fulfill the new obligations — the specific grounds and procedure established by law apply. Until 1 March 2027, the expanded mechanism does not apply; it should not be confused with the current obligations of 2026.
Bank Connection Checklist
- Wait for the notice from Mintsifry — about the agreed scenario (Resolution No. 200, clause 15); the notice arrives no later than 30 days after agreement with the FSB.
- Request the technical documentation — via ESKS (info.gosuslugi.ru), and open access to the interaction participant’s personal account (lkuv.gosuslugi.ru).
- Prepare the infrastructure — a server for installing the current version of the SMEV 4 Agent (PODD Agent), if the scheme of connecting via SMEV 4/PODD has been chosen.
- Obtain certificates — and set up access to the SMEV environment, as required by the chosen connection scheme.
- Carry out testing — in the TSMEV 4 test environment (podd.test.gosuslugi.ru), if this is provided for by the requirements of the operator of the specific scenario.
- Set up routing — of incoming signals into the internal anti-fraud loop, and the logic for generating return responses.
- Set up logging — of signal processing, to confirm fulfillment of obligations and to inform the operator quickly of failures (clause 11).
- Move to the production environment — and put the scenario into permanent operation.
- Check indicator 1.2 — whether it is taken into account in the transaction checking logic under OD-2506; this obligation applies from 1 March 2026 regardless of the date of actual connection to a specific scenario.
- Build the requirements of 210-FZ into the roadmap — from 1 March 2027: mandatory transmission of information to the GIS and use of Bank of Russia information and malware data when checking transactions.
In regulatory terms, the connection procedure is described rather as a framework: Mintsifry and the FSB agree a scenario, the operator notifies participants within 30 days after the agreement, and then the bank, as a rule, implements the connection via SMEV 4 and the PODD Agent — this is an implementation option confirmed by practice and ESKS documentation, not the only possible method under the regulations. The law does not fix the specific package of documents or exact project timelines, and here the bank’s technical readiness and the quality of its work with the integrator are decisive. At the same time, the project’s scale is no longer limited to the pilot: according to the office of the Deputy Prime Minister, as of 18 June 2026, 12 organizations were connected to the GIS, including the largest banks and telecom operators, while Kommersant gives the estimate of “2,500 organizations at the first stage and about 20,000 in the future” citing an anonymous market source, not Mintsifry.
The key fork for planning is not the integration itself but separating the levels of obligation. Participation in a scenario is formally voluntary, but using GIS information when checking transactions is already mandatory from 1 March 2026 through indicator 1.2 of Order OD-2506, while the transmission of information to the GIS and the expanded reimbursement mechanism under 210-FZ will appear only from 1 March 2027. A bank that builds its connection architecture with these three horizons in mind from the start spends fewer resources on rework over the next two years than one that responds to each requirement separately.
FAQ
We’ll explain how to embed the NeuroVision solution into the bank’s compliance and prepare for each stage of Antifrod 2.0.
