The PSR, team by team
The PSR (PSD3) for operations teams
Several PSR obligations rest on processes that people run, on the bank's side and on the TPP's side. On the bank's side, every planned unavailability is announced to TPPs a month ahead, and during an outage the bank tells them what it is doing to restore the interface. A change to the interface is published at least two months before it goes live, against three months in the 2018 RTS. The technical documentation goes free of charge to the TPPs who ask for it, and the bank cannot require extra registrations from them.
On fraud, the bank may deny a TPP access over unauthorised or fraudulent access, on objectively justified and duly evidenced grounds. It then tells the user and reports it to the authority immediately. If it refuses a payment a PISP initiated over suspected fraud, it gives the PISP the reasons, within 10 seconds for an instant credit transfer. On the TPP's side, the PISP compensates the payer's bank when the payee verification failure comes from the PISP.
By Tancrède Simonin, October 22, 2026
17 obligations for your team
6 with no equivalent in PSD2 or the 2018 RTS
T + 21 months for 16 of them, T + 27 for the last one
17 of 17 also involve tech
Where to start
The five obligations that change the most for this team, in reading order.
- 1
- 2
- 3
- 4
- 5
Your 17 obligations, by family
Obligations checked on October 4, 2026.
Dedicated interface9 obligations
- OB-IF-002Interface live within three months of authorisation newPSR 35(2)
- OB-IF-004Free technical documentation and public summaryPSR 35(3)
- OB-IF-005Two months' notice before any changePSR 35(4)
- OB-IF-006Quarterly statistics publishedPSR 35(5)
- OB-IF-007Testing facility with supportPSR 35(6)
- OB-IF-010Parity with the customer interfacePSR 37(1)
- OB-IF-012Maintenance announced a month ahead, from 00:00 to 06:00 newPSR 38(2)
- OB-IF-013TPPs kept informed during an outagePSR 38(2a)
- OB-IF-018TPP requests treated like the customer's ownPSR 40(c)
Payment initiation3 obligations
Prohibited obstacles2 obligations
Authorities and sanctions2 obligations
Consent dashboard1 obligation
New compared with PSD2
- OB-IF-002Interface live within three months of authorisation
- OB-IF-012Maintenance announced a month ahead, from 00:00 to 06:00
- OB-PIS-013Payee verification, PISP liability
- OB-PIS-014The PISP may refuse to initiate
- OB-DB-006After withdrawal, the TPP stops and deletes
- OB-ENF-003TPP access data reported to the authority
Shared with the other teams
These obligations are handled by several teams. The entry and its reference are the same for everyone.
Glossary cards
STET 1.6.3 handbook pages cited5 pages
The pages these obligations cite, most cited first.