How to Register for the FNC-RF Scheme in France?

On May 6, 2026, the FNC-RF scheme (National File of Accounts Reported for Fraud Risk) will officially go live in production. All PSP (Payment Service Providers) operating in France are required to participate.

Following the so-called “Labaronne” law, which established a legal framework for sharing fraudulent IBANs, the Banque de France is deploying a national infrastructure enabling institutions to report accounts involved in fraud and consult existing alerts. The objective is clear: prevent the reuse of IBANs already identified as fraudulent and strengthen collective prevention.

For the PSPs concerned, the challenge is now operational. How should they register? Which documents must be submitted? What does the connection process look like?

A multi-step process

The first step consists of registering with the Banque de France in order to adhere to the scheme. This registration conditions access to the central file. Once registered, the PSP receives a UUID (unique identifier) allowing it to connect to the Banque de France’s MISP platform.

The next phase is implementation, either through internal development or by relying on an external service provider authorized by the Banque de France. The PSP must also obtain a certificate to authenticate exchanges, issued by a certification authority approved by the Banque de France (e.g., CertEurope, DigiCert, GlobalSign).

Finally, the integration must be validated in pre-production by the Banque de France, in accordance with a strict test plan. Successful validation of this testing phase allows the PSP to move into production.

Registering with the Banque de France: practical guidance

A PSP wishing to connect to the scheme must first obtain the registration documents from its professional association (ASF, OCBF, FBF or AFEPAME). Three documents must be completed:

1. The subscription form

This document formalizes acceptance of the General Terms and Conditions of Use of the FNC-RF service and includes the participant’s legal information: corporate name, legal form, share capital, identity of the legal representative, and so on. Where an institution acts as the head of a group, it must append the list of affiliated entities on whose behalf it adheres and commit to paying the corresponding invoices.

2. The technical connection form

This form specifies the requested implementation date, the chosen interfacing method — via the PSP’s own MISP instance or via the Banque de France API — as well as the selected functional scope (read-only access or both read and write access).

The certification authority (CA) must be indicated. It is also possible to use a certificate issued directly by the Banque de France. If a technical service provider is involved (for example, Qombo), the name of the provider and its contact details must be provided.

In addition, the PSP must designate its operational contacts: fraud business lead, IT contact and, where applicable, the technical provider’s points of contact.

3. The list of BIC codes attached to the organization

This document applies only to account-servicing PSPs and constitutes the official reference list of BICs covered within their scope. This is a critical element: the submitted reference list will enable the identification of the account-servicing PSP responsible for qualifying any alert related to a given BIC code.

Once completed, the documents may be sent to the Banque de France either by post or via a secure Sharebox. The latter option is generally recommended for reasons of speed and traceability.