The PSR, team by team
The PSR (PSD3) for tech teams
The PSR sets a functional baseline for the dedicated interface, and STET 1.6.3 does not cover all of it. The largest gap is consents. The TPP must send the bank the purpose and validity period of every consent, the bank must tell the TPP about every withdrawal, and STET has neither the fields nor a notification. That data feeds the consent dashboard, a new screen on the bank's side where the user can withdraw access and restore it within 48 hours. A PISP must be able to read the account, its holders and its currencies before initiation, which STET does not allow.
Start by filtering the list on the STET statuses Missing, then Partial. Then look at refresh token lifetimes, because the bank may now require SCA only on an AISP's first access, unless it suspects fraud. On the infrastructure side, the dedicated interface is presumed unavailable once five consecutive requests get a server error or no answer within 30 seconds.
By Tancrède Simonin, October 22, 2026
68 obligations for your team
27 with no equivalent in PSD2 or the 2018 RTS
T + 21 months for 65 of them, from entry into force for 2 others and T + 27 for the last one
28 of 68 also involve compliance
Where to start
The five obligations that change the most for this team, in reading order.
- 1
- 2
- 3
OB-PIS-009 · PSR 36(4)(hc)
Account, holders and currencies visible before initiation new
Payment initiation
- 4
- 5
Your 68 obligations, by family
Obligations checked on October 4, 2026.
Dedicated interface17 obligations
- OB-IF-001At least one dedicated interface per ASPSPPSR 35(1)
- OB-IF-002Interface live within three months of authorisation newPSR 35(2)
- OB-IF-003Recognised communication standardsPSR 35(3)
- 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-008Error messages that explain the causePSR 35(7)
- OB-IF-009Authentication started by the TPP, protected sessionPSR 36(2)(b)
- OB-IF-010Parity with the customer interfacePSR 37(1)
- OB-IF-011Unavailability presumed after five failed requestsPSR 38(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-015TPP access through the dedicated interface onlyPSR 45(1)
- OB-IF-016TPP duties on the customer interfacePSR 45(2)
- OB-IF-017TPP identification towards the ASPSPPSR 36(2)(a)
- OB-IF-018TPP requests treated like the customer's ownPSR 40(c)
Payment initiation14 obligations
- OB-PIS-001Standing order, set-up and revocation newPSR 36(4)(a)
- OB-PIS-002Single paymentPSR 36(4)(b)
- OB-PIS-003Future-dated payment, initiation and revocation newPSR 36(4)(c)
- OB-PIS-004Payments to multiple beneficiaries newPSR 36(4)(d)
- OB-PIS-005Payee outside the payer's beneficiary list newPSR 36(4)(e)
- OB-PIS-006Execution information and status until the endPSR 37(3)
- OB-PIS-007Account holder name check before initiation newPSR 36(4)(g)
- OB-PIS-008The PISP chooses the authentication procedure newPSR 36(4)(ha)
- OB-PIS-009Account, holders and currencies visible before initiation newPSR 36(4)(hc)
- OB-PIS-010Yes or no answer on fundsPSR 36(5)(a)
- OB-PIS-011Confirmation that the payment will be executed newPSR 36(5)(b)
- OB-PIS-012Refusal over suspected fraud, reasons to the PISPPSR 65(1)
- OB-PIS-013Payee verification, PISP liability newPSR 57
- OB-PIS-014The PISP may refuse to initiate newPSR 46(1)(fa)
Prohibited obstacles13 obligations
- OB-OBS-001Blocking the use of the bank's credentialsPSR 44(1)(a)
- OB-OBS-002Making the user type the account identifier at the bankPSR 44(1)(b)
- OB-OBS-003Checking the consent given to the TPPPSR 44(1)(c)
- OB-OBS-004Requiring additional registrationsPSR 44(1)(d)
- OB-OBS-005Requiring contact details to be pre-registeredPSR 44(1)(e)
- OB-OBS-006Limiting payments to the payer's beneficiary listPSR 44(1)(f)
- OB-OBS-007Limiting to domestic account identifiersPSR 44(1)(g)
- OB-OBS-008More SCA than in the direct channelPSR 44(1)(h)
- OB-OBS-009Not supporting every authentication procedurePSR 44(1)(i)
- OB-OBS-010Adding steps to the journeyPSR 44(1)(j)
- OB-OBS-011Forcing a redirect to the bank's websitePSR 44(1)(k)
- OB-OBS-012Two SCAs in a payment-initiation-only journeyPSR 44(1)(l)
- OB-OBS-013No contract required for the baselinePSR 34
Consent dashboard9 obligations
- OB-DB-001Consent dashboard at the ASPSP newPSR 43(1)
- OB-DB-002What the dashboard shows newPSR 43(2)(a)
- OB-DB-003Withdrawal at any time, free of charge newPSR 43(2)(b)
- OB-DB-004Re-establishment possible for 48 hours newPSR 43(2)(c)
- OB-DB-005Two-year history newPSR 43(2)(d)
- OB-DB-006After withdrawal, the TPP stops and deletes newPSR 43(2b)
- OB-DB-007The TPP sends each consent to the ASPSP newPSR 43(3b)
- OB-DB-008The ASPSP tells the TPP about every change newPSR 43(4)
- OB-DB-009Neutral dashboard, no deceptive design newPSR 43(3)
Account information7 obligations
- OB-AIS-001All payment accounts accessible onlinePSR 33(2)
- OB-AIS-002Minimum data for the AISP newPSR 36(3)
- OB-AIS-003Data parity with the customer interfacePSR 37(2)
- OB-AIS-004AIS access with or without the userPSR 41(2)
- OB-AIS-005User told about background access newPSR 41(2a)
- OB-AIS-006Holder name and identifier are not sensitive newPSR 36(5a)
- OB-AIS-007The AISP accesses designated accounts onlyPSR 47(1)(d)
Strong customer authentication5 obligations
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-AIS-002Minimum data for the AISP
- OB-AIS-005User told about background access
- OB-AIS-006Holder name and identifier are not sensitive
- OB-PIS-001Standing order, set-up and revocation
- OB-PIS-003Future-dated payment, initiation and revocation
- OB-PIS-004Payments to multiple beneficiaries
- OB-PIS-005Payee outside the payer's beneficiary list
- OB-PIS-007Account holder name check before initiation
- OB-PIS-008The PISP chooses the authentication procedure
- OB-PIS-009Account, holders and currencies visible before initiation
- OB-PIS-011Confirmation that the payment will be executed
- OB-PIS-013Payee verification, PISP liability
- OB-PIS-014The PISP may refuse to initiate
- OB-DB-001Consent dashboard at the ASPSP
- OB-DB-002What the dashboard shows
- OB-DB-003Withdrawal at any time, free of charge
- OB-DB-004Re-establishment possible for 48 hours
- OB-DB-005Two-year history
- OB-DB-006After withdrawal, the TPP stops and deletes
- OB-DB-007The TPP sends each consent to the ASPSP
- OB-DB-008The ASPSP tells the TPP about every change
- OB-DB-009Neutral dashboard, no deceptive design
- OB-SCA-004Recurring credit transfers without SCA each time
- OB-ENF-003TPP access data reported to the authority
- OB-ENF-007Machine-readable central list of AISPs and PISPs
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 cited33 pages
The pages these obligations cite, most cited first.
- 3. Prerequisites and technical detailsCited by OB-IF-003, OB-IF-008, OB-IF-009, OB-IF-017, OB-AIS-004, OB-DB-003, OB-DB-004, OB-DB-008, OB-OBS-001, OB-OBS-004, OB-OBS-005, OB-OBS-008, OB-OBS-009, OB-OBS-011, OB-SCA-001, OB-SCA-002, OB-SCA-003, OB-ENF-007
- POST /payment-requestsCited by OB-IF-009, OB-PIS-002, OB-PIS-004, OB-PIS-005, OB-PIS-008, OB-PIS-009, OB-PIS-013, OB-OBS-002, OB-OBS-006, OB-OBS-007
- PUT /consentsCited by OB-AIS-006, OB-AIS-007, OB-DB-002, OB-DB-004, OB-DB-007, OB-DB-008, OB-OBS-003
- GET /payment-requests/{paymentRequestResourceId}Cited by OB-PIS-006, OB-PIS-010, OB-PIS-011, OB-PIS-012
- 6.1. PSU Context RetrievalCited by OB-IF-009, OB-SCA-002, OB-SCA-003
- AISP endpointsCited by OB-IF-001, OB-AIS-003
- PISP endpointsCited by OB-IF-001, OB-PIS-007
- GET /accountsCited by OB-AIS-001, OB-AIS-002
- GET /accounts/{accountResourceId}/ownersCited by OB-AIS-002, OB-AIS-006
- 6.2. Consent ForwardingCited by OB-AIS-007, OB-DB-007
- PUT /payment-requests/{paymentRequestResourceId}Cited by OB-PIS-001, OB-PIS-003
- 8.2. Payment Request with multiple instructions having different beneficiariesCited by OB-PIS-004, OB-OBS-012
- BeneficiaryCited by OB-PIS-005, OB-OBS-006
- AuthenticationApproachCited by OB-OBS-001, OB-OBS-009
- CBPII endpointsCited by OB-IF-001
- ErrorModelCited by OB-IF-008
- AccountResourceCited by OB-AIS-001
- GET /accounts/{accountResourceId}/balancesCited by OB-AIS-002
- GET /accounts/{accountResourceId}/transactionsCited by OB-AIS-002
- 8.3. Standing Orders RequestCited by OB-PIS-001
- StandingOrderCharacteristicsCited by OB-PIS-001
- 8.1. Payment Request with multiple instructions having different execution datesCited by OB-PIS-003
- GET /payment-requests/{paymentRequestResourceId}/transactionsCited by OB-PIS-006
- SupplementaryDataCited by OB-PIS-008
- FundsAvailabilityInformationCited by OB-PIS-010
- POST /funds-confirmationsCited by OB-PIS-010
- PaymentInformationStatusCodeCited by OB-PIS-011
- StatusReasonInformationCited by OB-PIS-012
- AccessCited by OB-DB-002
- PaymentRequestResourceCited by OB-OBS-002
- POST /registerCited by OB-OBS-004
- AccountIdentificationCited by OB-OBS-007
- POST /payment-requests/{paymentRequestResourceId}/confirmationCited by OB-OBS-012