Single Layer

Single Layer means that there is only onw layer between the TPP and the Internal services of the bank:

The bank has one layer of Gateways in the DMZ which directly communicate with the Internal Bank services.

The diagram below shows the high level integration that happens between the different components.

The packaged required are all of them:

0-Fragments

1-DMZ

2-Internal services

3-XS2A

4-Mock

Here is a diagram:

 

For a High Level architecture view, here is what it would look like, the above component is the PSD2 Solution Pack component herebelow. and the three EBAregistry, “Consents Auth, PI DB” and “Mock Bank DB” are together as the PSD2 Database.

 

 

component

Meaning

Area

component

Meaning

Area

PSU

Payment Service User, customer

External (Bank user)

TPP

Trusted Payment Party.
This can be for account management (AISP) or for initiating payments (PISP)

External (Client)

ASPSP

Account Servicing Payment Service Provider. This is the Bank

Bank

Backends

Protected area where all the data of the customers of the Bank resides

Bank

Bank PSU Directory

The identity provider that the bank uses for authenticating their bank customers

Bank

Layer7 Gateway

The API proxy solution owned by CA/Broadcom

Bank

Bank Authentication System

An abstract layer that deals with the authentication of the Bank user, this might have components used by the Gateway, that is why the overlapping. This includes 2FA, SCA, OTP, etc…

Bank

Online Banking

The Online Banking Portal of the bank itself, used by the customers of the bank to view their information from which they can also revoke authorisations and consents.

Bank

PSD2 Solution Pack

Addon to the Gateway that allows for the seamless integration and standard enforcement.

Bank

PSD2 Database

Database that contains the collection of consents, authorisation and payment initiation IDs

Bank

Related pages

apiida.com