Skip to content

Security

What actually stops someone

Most of what a bank calls security is a screen that hides a button. Here is what happens underneath, where hiding a button changes nothing.

The database refuses, not the code

A negative balance, a second main account, an active card that was never approved: the engine turns them down. Not a condition somebody could forget to write.

The rules
Closing gives the money back first
Refused by the database
The main account
One per client
Cards
Approved before being active

Nothing is deleted quietly

An audit line names who acted, when, and from where, and it cannot be erased by the person it names — the database refuses that too.

The receipt of a transfer, exactly as the portal issues it.

Ledger entry Settled
Description
Transfer to Marie Lefevre
Posted at
TRX-2026-08-0009408
Approved by
Camille Roux
Amount
-1,250.00 €

Security

A second factor that really blocks

Five wrong attempts lock the screen, and during the lockout the RIGHT code is refused too. A counter you can outrun is not a counter.

  • Five attempts, then a quarter of an hour locked — and during that lock the right code is refused as well.
  • Every attempt is written to the log, successful or not.
  • Two-factor authentication is available, and turning it off is guarded like turning it on.
  • The full number and the security code are fetched only after your PIN, are never part of the page’s state, and every reveal is written to the audit trail.

PIN code

Asked for on every transfer, every card order, every administrative decision.

Report a weakness

Write to our team with what you found. We answer, we fix, and we say publicly what was wrong once it is closed.

Open an account in a few minutes

No paperwork to print, no branch to visit. You will need an identity document and a proof of address.

Open an account

What this site keeps. A session cookie, an anti-forgery token, and your display preferences. No audience measurement, no third-party script. The cookies page