Law / Germany

Zahlungsdiensteaufsichtsgesetz (ZAG), Section 55 Strong Customer Authentication

ZAG § 55

In force since .

A sector security regimes rule binding public and private bodies.

Obligation class
Security

What it requires

  • If you provide payment services as a payment institution, an e-money institution or a credit institution, including as the account servicing provider, Section 55 binds you beside the technical standards under Article 98 of Directive (EU) 2015/2366.
  • Require strong customer authentication when the payer accesses a payment account online, initiates an electronic payment transaction, or acts through a remote channel in a way that carries a risk of payment fraud or other abuse (Section 55(1)).
  • For an electronic remote payment transaction, require authentication with elements that dynamically link the transaction to a specific amount and a specific payee (Section 55(2)).
  • Have adequate security measures to protect the confidentiality and integrity of your users' personalised security credentials (Section 55(1)).
  • If you are the account servicing provider, let payment initiation and account information service providers rely on the authentication procedures you give your user (Section 55(4)).

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

Who enforces it

Settledness

As of

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

Section 55(1) of the Zahlungsdiensteaufsichtsgesetz (ZAG) obliges a payment service provider to require strong customer authentication when the payer accesses a payment account online, initiates an electronic payment transaction, or carries out through a remote channel an action that involves a risk of payment fraud or other abuse. For a remote electronic payment transaction the authentication must include elements that dynamically link the transaction to a specific amount and a specific payee.

The provider must have adequate security measures to protect the confidentiality and integrity of the personalised security credentials of its users. An account servicing provider must allow payment initiation and account information service providers to rely on the authentication procedures it gives its user. Details of the requirements, including exemptions, are set by the delegated act under Article 98 of Directive (EU) 2015/2366. Section 55 entered into force on .

When LexLint raises it

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

Back to the example  ·  Lint your app

Page updated .