Law / France

Code monétaire et financier Article L. 133-44, Strong Customer Authentication of Payment Users

Code monétaire et financier, art. L. 133-44 (authentification forte du client)

In force since .

A sector security regimes rule binding private bodies.

Obligation class
Security

What it requires

  • This binds every payment service provider: payment institutions, electronic money institutions, credit institutions and account information service providers; you reach it by declaring that you are a bank or a payment provider.
  • Apply strong customer authentication when the payer accesses a payment account online, initiates an electronic payment transaction, or carries out a transaction through a remote means of communication that may carry a risk of payment fraud or other fraudulent use (Article L. 133-44 I).
  • For a remote electronic payment transaction, include elements that dynamically link the transaction to the amount and the payee (Article L. 133-44 II).
  • Put adequate security measures in place to protect the confidentiality and integrity of users' personalised security credentials (Article L. 133-44 III).
  • If you manage the payer's account, let payment initiation and account information providers rely on your authentication procedures when they act for one of your users (Article L. 133-44 IV).

These lines are LexLint's reading of the law's text.

What this law does

Drafted with AI

Drafted with AI from the cited sources under the direction of UnGovr staff. UnGovr holds editorial responsibility for this page. How this site is made

Research summary

Legal information, not legal advice. This is LexLint's own research summary of a public legal source, and it creates no attorney-client relationship. For decisions that matter, consult qualified counsel in the relevant jurisdiction. About LexLint

Article L. 133-44 requires a payment service provider to apply strong customer authentication when the payer accesses a payment account online, initiates an electronic payment transaction, or carries out a transaction through a remote means of communication that may carry a risk of payment fraud or other fraudulent use. For remote electronic payment transactions, strong authentication must include elements that dynamically link the transaction to a given amount and payee.

The provider must put adequate security measures in place to protect the confidentiality and integrity of users' personalised security credentials. The account servicing provider must allow payment initiation and account information providers to rely on its authentication procedures when they act for one of their users.

Under Article 34 VIII of the ordinance of that transposed the second Payment Services Directive, paragraphs I, II and III of Article L. 133-44 entered into force eighteen months after the entry into force of the delegated act adopted under Article 98 of that Directive. That delegated act, Delegated Regulation (EU) 2018/389, applies from .

When LexLint raises it

When your app profile says your app is a bank or is a payment provider.

Back to the example  ·  Lint your app

Page updated .