APIs

PSD2 CIS - Consent Information Service
1.6.3

Consents and consent management are core concepts of the PSD2 solution, and are defined with dedicated API endpoints in the Berlin Group specification. The general mechanism for validating and authorizing consents is through a Redirect SCA Approach - utilising implicit start of the authentication process. This is described in NextGenPSD2 XS2A Framework - Implementation Guide, Section 6.1.1.1, Page 101.

Access to the Consent Information Service API is controlled through the general onboarding/enrollment flow. I.e

REST
Online
PSD2 FCS - Fund Confirmation Service
1.1.8

The Fund Confirmation Service (FCS) API provides a service to query the availability of a specific amount at the point in time of the call.

Access to the FCS API is controlled through the general onboarding/enrollment flow. I.e. the API is only accessible to valid TPPs, who have completed the enrollment in order to upload and verify their qualified certificates. By accessing the API, you confirm that you already have status as an authorized TPP - or (for sandbox access only) that your application has been submitted to a local NCA and is pending approval. Only TPPs who can document their

REST
Online
PSD2 PIS - Payment Initiation Service
2.4.4

The PIS API implements the Payment Initiation Service parts of the PSD2 specification, and provides the following services to authorized TPPs:

  • Initiation and update of a payment request
  • Status information of a payment
  • Singing baskets - authorising several transactions with one SCA operation

Access to the Payment Initiation Service API is controlled through the general onboarding/enrollment flow. I.e. the API is only accessible to valid TPPs, who have completed the enrollment in order to upload and verify their qualified certificates. By accessing the API, you confirm that you already

REST
Online
TPP Enrollment API
0.1.2

API for completing enrollment/onboarding to PSD2 APIs to Member and Service Banks under BEC umbrella. The onboarding step serves to 1) Verify the identity of the TPP 2) Establish and verify the TPP's roles with respect to PSD2 (AISP, PISP, CBPII)

The enrollment API uses the same general format and mechanisms as specified in the Berlin Group XS2A specification. Hence the TPP will need to present a qualified QWAC certificate (which when registered allows the TPP to setup two-way TLS when conecting to the BG XS2A APIs) as well as a QSEAL (which is use by TPP to sign API requests and which gives

REST
Online