- Question ID
-
2024_7261
- Legal act
- Directive 2015/2366/EU (PSD2)
- Topic
- Other topics
- Article
-
66
- Paragraph
-
4
- Subparagraph
-
b
- COM Delegated or Implementing Acts/RTS/ITS/GLs/Recommendations
- Regulation (EU) 2018/389 - RTS on strong customer authentication and secure communication
- Article/Paragraph
-
35.4.b
- Type of submitter
-
Other
- Subject matter
-
Obstacles Faced by PISPs in Accessing Payment Status Information Under PSD2
- Question
-
Are ASPSPs allowed to require PISPs to provide any additional identifier beyond what is specified in Article 35.4.b of the RTS in order to access information about the execution of a payment order?
- Background on the question
-
In accordance with Articles 66.4.b of the PSD2, Account Servicing Payment Service Providers (ASPSPs) are required to provide or make available all necessary information on the initiation and execution of payment transactions to Payment Initiation Service Providers (PISPs) upon receipt of a payment order. Specifically, Article 66.4.b mandates that this information be shared with the PISP immediately following the payment initiation, while RTS Article 35.4.b stipulates that all parties involved must include unequivocal references to identify each payment order
Additionally, Article 36.1.b of the RTS requires that PISPs have access to all relevant information about the initiation and execution of payment orders.
However, some ASPSPs, unlike the broader industry standard, impose additional requirements, such as mandating the use of a "user token" to access payment execution information.
This practice conflicts with broader industry standards, where ASPSPs provide the necessary information without imposing similar constraints. Requiring "user tokens" undermines the uniformity intended by PSD2, leads to inconsistency among ASPSPs, and hinders PISPs' ability to comply with their obligations under PSD2 and the RTS.
- Submission date
- Status
-
Question under review
- Answer prepared by
-
Answer prepared by the EBA.