Access to an online banking account relies on strong authentication, as required by PSD2. This technical requirement, often reduced to entering an SMS code, actually underpins the account’s entire security process: first login, periodic renewal (Crédit Agricole requires reauthentication every 90 days), and approval of sensitive transactions. Understanding this foundation helps you prepare for the most disruptive scenario: losing the mobile device used as an authentication factor.
Lost phone and banking authentication: backup solutions
Smartphones have become the gateway to our accounts. If yours goes missing, breaks down, or is stolen, strong authentication prevents you from logging in to your customer account. Most online banks mention this situation only in obscure corners of their FAQs.
Depending on the bank, there are three fallback options:
- A code-generating device (Digipass or equivalent), offered by some traditional banks with online services. It works without a network connection or a phone.
- Calling customer service to request a temporary unlock after an identity check. The wait can range from a few minutes to 48 hours, depending on the bank and the level of verification required.
- Setting up the authentication device on a new phone, which generally requires a visit to a branch or a letter containing an activation code.
One precaution to take before anything goes wrong: check your banking app’s security settings to see whether you can enable a backup authentication factor (recovery email address, security question, or physical device). Some banks let you register two devices at the same time.
To view accounts from multiple institutions in one place, you can access Mon Portail Finance banking and bring your accounts together on a single dashboard, provided the service provider holds the ACPR authorization required under PSD2.

Checking the payee before a transfer: what changed in October 2025
Since October 9, 2025, payment service providers have been required to check that the payee’s name matches the name associated with the IBAN before executing a transfer. This check, known as “Verification of Payee,” adds a visible step to the approval process.
When you add a new payee or enter a transfer, the interface displays a match status. If the names do not match or only partially match, an alert appears. The transfer is not automatically blocked, but users are prompted to verify the details through a trusted channel before confirming.
This measure directly targets scams involving manipulation. The 2025 report by the Observatory for the Security of Payment Means, published by the Banque de France in 2026, notes an increase in fraud based not on stolen credentials but on psychologically manipulating the account holder. A typical scenario: a fake bank adviser calls the customer and persuades them to approve a transaction or transfer funds to a “secure account.”
Payee verification does not protect against every scenario, but it creates a pause. For users accustomed to approving transfers in seconds, this extra time provides a practical safeguard.
Bank account aggregation: regulatory framework and practical limitations
Viewing accounts from several banks in a single app is appealing, but it is worth understanding how the service works before enabling it. PSD2 distinguishes between two types of third-party services: account information services (centralized account viewing) and payment initiation services (initiating transfers through a third party).
Account aggregators must hold authorization issued by the ACPR. Without it, the provider operates outside the legal framework. Before connecting your accounts, check that the app is listed in the Register of Financial Agents (REGAFI).
Some practical limitations to be aware of:
- Synchronization may stop if strong authentication expires with your original bank. You will then need to reconnect each institution manually.
- View-only aggregators do not allow you to make transfers or change limits. These transactions must still be carried out through the bank’s own customer portal.
- Some banks restrict or delay API access for third-party providers, which can result in display delays ranging from a few hours to a full day.

Unauthorized transaction on an online account: what to do before it happens
Waiting until you become a fraud victim to find out what to do is a common mistake. Reporting the incident immediately affects your chances of getting reimbursed. The steps are simple, but the order matters.
As soon as you spot a suspicious transaction, contact your bank without delay to block your card if it has been compromised, then formally dispute the transaction. Keep all relevant evidence: screenshots of the transaction, correspondence with customer service, and any messages from the fraudster.
Reimbursement deadlines and conditions depend on the type of payment (card, transfer, direct debit) and whether the customer may have been negligent. An unauthorized direct debit is easier to dispute than a transfer approved using strong authentication, since in the latter case the bank may cite the account holder’s explicit approval.
We recommend setting up real-time alerts for every account transaction, a feature available in almost all banking apps. An unnoticed charge of just a few euros may be a test before a larger fraud attempt. The first few hours are often critical.




