Introduction to PSD2 Account Information

PSD2 Account Information module (PZ) provides functionality that assists the Account Information Service flows under the Berlin Group.

It consists of the following:

Parameter table
Account Consent Framework using AA
Account Information Service Provider (AISP) APIs and workflows

A high-level summary of the facilitated Berlin Group flow is shown below.

A customer signs up to a Third Party Provider (TPP), which is an AISP that offers Account Aggregation services.
The TPP outlines the terms and conditions of their service, including the details they will be requesting from the customer’s bank. The customer then accepts the T&Cs.
In the TPP, the customer chooses the bank they want to aggregate their accounts from.
The TPP sends a consent request to the customer’s chosen bank, which contains the details of the customer’s accounts and services that TPP requires access to.
The bank receives the request and the following are validated:
- eIDAS check by the API gateway
- TPP Validation by the Payment Hub or Temenos Transact (depending on the architecture)
The request is accepted only if all validations are successful.
Based on a successful request, the bank creates a consent resource. The consent ID is used throughout the consent lifecycle.
The bank provides a response to the TPP, including the consent ID and a redirect link. This is used to redirect the customers to authenticate themselves.
The TPP redirects the customer to a given landing page.
The customer performs Strong Customer Authentication (SCA) to prove the request is genuine (by authenticating the requesting customer). The SCA process is handled by the bank’s identity provider (IDP).
After authentication, a check is done to identify whether the customer has access to the requested accounts through an online channel and whether they are PSD2 eligible.
After the list of accounts is generated, the customer reviews the request at the bank, including the details of what the TPP is requesting access to. The customer can then authorise or cancel the request.
Depending on the customer’s decision, a response is provided to the TPP.
- If the customer authorises the request, the TPP can make subsequent requests for certain account information.
- If the customer cancels the request, the TPP cannot access any customer data.
The TPP uses the consent ID to request account information from the customer’s accounts.
The customer can withdraw consent at any time at the TPP or their bank directly.

Configuring PSD2 Account Information

This section helps the user configure the PZ module.

PZ.PARAMETER

The PZ.PARAMETER application is used to configure the PZ module and can be used to:

Identify the types of accounts that are considered ‘payment’ accounts (and are eligible for PSD2 processing). This can be based on specific category codes or AA Products.
Identify where Consent Management is handled (internally or externally to Temenos Transact).
Identify where TPP Validation is handled (internally or externally to Temenos Transact).

The record ID is the COMPANY of the bank the parameterisation is applicable for.

NOTE: A record is needed for each company in which the configuration is required. If both PZ and PX modules are installed, it is recommended that the parameter table configurations for the Payment Account Definition are in sync.

A screenshot of the PZ.PARAMETER application with a description of each field’s intended use is shown below:

NOTE: For all descriptions listed below, ‘Available’ accounts are payment accounts that are considered eligible for PSD2.

Only one of the following combinations is allowed for defining the Payment Account Definition:

Default Available field
Avail Categ field
Avail AA Prod field

NOTE: Multiple combinations for defining the Payment Account Definition are not allowed.

Field	Description
Default Available	Used to flag all types of accounts offered by the bank that are ‘Available’. If selected, all categories of accounts offered by the bank are considered as eligible for PSD2. If not selected, accounts offered by the bank are not considered as eligible for PSD2 unless they are configured in the Avail Categ fields.
Avail Categ Start	Holds the start number of the `CATEGORY` range for accounts that are considered ‘Available’ under PSD2. It should be used in conjunction with Avail Categ End to allow the client to define a range of `CATEGORY`s that are eligible for PSD2 processing. Example The bank has the below `CATEGORY`s available: 1000 – Demand Account 1001 – Current Account Standard 1002 – Current Account with Overdraft 1003 – Current Account Premium 1004 – Current Account Student 1005 - Junior Savings Account 1006 – Teen Saver 1007 – Instant Access Payment Account 1008 – Long Term Savings Account 1009 – Instant Access Savings Account 1010 – Credit Card 1011 – Fixed Term Deposit 2Y 1012 – Fixed Term Deposit 3Y The bank considers the accounts highlighted in blue as eligible accounts under PSD2. The value of the Avail Categ Start field is 1001. The value of the Avail Categ End field is 1004. All CATEGORY codes between 1001 and 1004 are considered ‘Available’. A customer need not enter every `CATEGORY` code manually and can instead enter a range. Individual `CATEGORY` codes (not within a range) can be defined in the Avail Categ field.
Avail Categ End	Holds the end number of the `CATEGORY` range for accounts that are considered ‘Available’ under PSD2. It should be used in conjunction with Avail Categ Start to allow the client to define a range of `CATEGORY`s that are eligible for PSD2. Example The bank has the below `CATEGORY`s available: 1000 – Demand Account 1001 – Current Account Standard 1002 – Current Account with Overdraft 1003 – Current Account Premium 1004 – Current Account Student 1005 – Junior Savings Account 1006 – Teen Saver 1007 – Instant Access Payment Account 1008 – Long Term Savings Account 1009 – Instant Access Savings Account 1010 – Credit Card 1011 – Fixed Term Deposit 2Y 1012 – Fixed Term Deposit 3Y The bank considers the accounts highlighted in blue as eligible accounts under PSD2. The value of the Avail Categ Start field is 1001. The value of the Avail Categ End field is 1004. This means all `CATEGORY` codes between 1001 and 1004 are considered ‘Available’. A customer need not enter every `CATEGORY` code manually and can instead enter a range. Individual `CATEGORY` codes (not within a range) can be defined in the Avail Categ field.
Avail Categ	Used in addition to or separately from the Avail Categ Start or Avail Categ End field. It allows the user to enter each `CATEGORY` code one by one, which is considered available for PSD2. The user can use the Avail Categ field to manually enter each `CATEGORY` code that is considered available. The user can use the Avail Categ Start or Avail Categ End field to define a range and then use the Avail Categ field to define any additional singular `CATEGORY` codes not included within the range. Example The bank has the below `CATEGORY`s available: 1000 – Demand Account 1001 – Current Account Standard 1002 – Current Account with Overdraft 1003 – Current Account Premium 1004 – Current Account Student 1005 – Junior Savings Account 1006 – Teen Saver 1007 – Instant Access Payment Account 1008 – Long Term Savings Account 1009 – Instant Access Savings Account 1010 – Credit Card 1011 – Fixed Term Deposit 2Y 1012 – Fixed Term Deposit 3Y The bank considers the accounts highlighted in blue as eligible accounts under PSD2. The bank can manually enter ‘1007’ and ‘1009’ to mark these as PSD2 eligible accounts.
Consent Mgmt	Allowed values are Internal or External. If the value is Internal, the Consent Management is handled in Temenos Transact and the Consent Validation is performed internally. If the value is External, the Consent Management is handled in an external system. NOTE: A null value denotes as Internal.
Obd Provider	Allowed values are: EXTERNAL – The Open Banking Directory is maintained outside of Temenos Transact. For example, when maintained by LUXHUB, validation in Temenos Transact is not required. Any valid record ID from `ST.OPEN.BANKING.DIR.PARAMETER` application. This would be in the instance where the bank has an interface with a directory such as PRETA. When this field is not set to External, the Open Banking Directory is populated with the data from an external source.
Block Tpp	Intended to be used only when the Obd Provider field is External. If the Obd Provider field is set to External, the TPP Validation is handled externally. However, to block a certain TPP from making requests, the bank may enter the TPP’s Global URN number in this field. During the TPP Validation, if the TPP’s Global URN is present in this field, the validation fails as the TPP is considered ‘blocked’. If the Obd Provider field is set to Internal (or another valid value), the user must enter a value in this field. Any blocking of the TPP must be handled in the relevant `PZ.OPEN.BANKING.DIR` record itself for the TPP.
Consent Level	Defines the level at which consent is managed within Temenos Transact. Allowed values are: Company – Set if the customer is not shared across the Temenos Transact instance. A parameter should be set for each `COMPANY`. Global – Set if the CUSTOMER is shared across the Temenos Transact instance.
Avail AA Prod Mode	Allows the bank to define the payment account definition through AA Products. Allowed values are: Null – Payment Account Definition not defined by AA Product. Default – Payment Account Definition defined by AA Product Groups (excluding those marked as exceptions). Specific – Payment Account Definition defined by AA Product (as defined as exceptions). Example In the following screenshot, all AA Products in CURRENT.ACCOUNTS of the AA Product Group, except STUDENT.ACCOUNTs and STAFF.ACCOUNTs, are considered ‘available’ under PSD2. In the following screenshot, only the AA Products that are STUDENT.ACCOUNTs or STAFF.ACCOUNTs are considered ‘available’ under PSD2.
Avail AA Prod Group	Defines the AA Product Group, which is considered to be a payment account. This field only allows a valid AA Product Group ID from the ACCOUNT product line. Mandatory if the AA Avail Prod Mode is Default. Must be blank if AA Avail Prod Mode is Specific. NOTE: This field allows multiple values.
Avail AA Prod Excpt	Defines the AA Products that are to be: Excluded (where AA Avail Prod Mode is Default) Included (where AA Avail Prod Mode is Specific) NOTE: This field allows multiple values.
Permissions Check	Defines if the user’s channels permission during PSD2 workflows will be checked within Temenos Transact or within an external system. Allowed values are: Null – Defaults channels permissions to be managed within Temenos Transact using EB External User and Online Channels Arrangement permissions. External – Defines that channels permissions will be managed externally. The expectation is that an external system will check if a user has permission to perform a certain action. NOTE: Once this field is set as External, it cannot be changed to Null. The system displays an override message to warn the user, when this flag is set to External.

Illustrating Model Parameters

Covers the high-level specifications required for the PZ module.

Parameter Description

Parameter	Description
`PZ.PARAMETER`	This application captures the categories of the accounts that are considered as available for Payment Services Directive (PSD2). Category range, that is, accounts that falls under a specific category range are considered as the available account for a specific customer. The category details are captured in the AVAIL.CATEG.START and AVAIL.CATEG.END fields. All the accounts can be considered as available accounts irrespective of the category and it can be defined in the DEFAULT.AVAILABLE field by marking as YES. The Permissions.Check field manages the ‘channels permissions’ validations. The AVAIL.AA.PROD.MODE field defines the rules for fields DEFAULT and SPECIFIC. These in-turn defines the list of products that are considered to be available for PSD2. The AVAIL.AA.PROD.GRP field defines the Product Group to be considered as available under PSD2. Allows valid AA.PRODUCT.GROUP from the ACCOUNT Product Line. The AVAIL.AA.PROD.ECXPT field allows valid AA.PRODUCT from the ACCOUNT Product Line (and applicable to the AA.PRODUCT.GROUP). This field can be left null to identify that no exceptions are defined.

PZ.PARAMETER

This application captures the categories of the accounts that are considered as available for Payment Services Directive (PSD2).
Category range, that is, accounts that falls under a specific category range are considered as the available account for a specific customer. The category details are captured in the AVAIL.CATEG.START and AVAIL.CATEG.END fields.
All the accounts can be considered as available accounts irrespective of the category and it can be defined in the DEFAULT.AVAILABLE field by marking as YES.
The Permissions.Check field manages the ‘channels permissions’ validations.
The AVAIL.AA.PROD.MODE field defines the rules for fields DEFAULT and SPECIFIC. These in-turn defines the list of products that are considered to be available for PSD2.
The AVAIL.AA.PROD.GRP field defines the Product Group to be considered as available under PSD2. Allows valid AA.PRODUCT.GROUP from the ACCOUNT Product Line.
The AVAIL.AA.PROD.ECXPT field allows valid AA.PRODUCT from the ACCOUNT Product Line (and applicable to the AA.PRODUCT.GROUP). This field can be left null to identify that no exceptions are defined.

Illustrating Model Products

PSD2 of the European Union and the Open Banking Implementation Entity (OBIE) have introduced the Third Party Provider services and as a result the customers can able to sign-up for account aggregation services from regulated TPPs. TPP can act as Account Information Service Provider (AISP), Payment Initiation Service Provider (PISP) and Payment Instrument Issuing Service Providers (PIISP).

Dark Mode

Expand/Collapse

In this topic