Article 31 (PSD2 RTS) – Outlines the access interface options, thus ASPSPs can provide access:
- via a dedicated interface (generally understood to refer to an API-based solution)
- by allowing the use by [TPPs], the interfaces used for authentication and communication with the [ASPSP’s] payment service users
Article 33 (PSD2 RTS) – Outlines the requirements of contingency interface.
- Customer Interface – the interface used by PSU to access the banking channels electronically - namely, Internet Banking, Mobile banking or others.
- API (Dedicated) Interface – As per PSD2 RTS mandate, provide API access to all banking facility associated with payment accounts to TPPs who consumes on behalf of PSU with valid consent.
- Customer Interface with TPP Identification – TPP using “Customer Interface” but need to be eIDAS-authenticated and NCA-authorised during the access. Also, ASPSP should have safeguards where only financial data is shared and not the personal data so that ASPSP is GDPR compliant. This interface will be commonly referred as Modified Customer Interface (MCI) in this guide. This can also be considered as fallback-interface or contingency mechanism to Dedicated Interface.