Endpoints for the resource - and available methods.

An AISP may retrieve the account product information for a specific AccountId (which is retrieved in the call to GET /accounts).

While this endpoint is marked as Conditional, it will be Mandatory for ASPSPs and account types covered in the CMA Order.

If an ASPSP has implemented the bulk retrieval endpoints for products - an AISP may optionally retrieve the products information in bulk.

This endpoint will retrieve the products resources for all authorised accounts linked to a specific account-request.

The OBReadProduct2 object will be used for the call to: 

• GET /accounts/{AccountId}/product

• GET /products

A resource that contains a set of elements that describes the product details specific to the account (AccountId) - which will include any pricing, fees, interest rates and product features for the account.

An account (AccountId) must only have a single product.

Notes:

• The product resource must be available for all PSD2 in scope accounts (if the product information is also available to the logged in PSU)

• Detailed product information is only available for BCA and PCA products

• High level product information for other products (other than BCA and PCA products) may be available via a reference to the Open Data APIs

Open

Notes:

• All PSD2 in-scope accounts are expected to return a response to the product resource. However, the BCA and PCA objects only apply to current account products (which are a CMA Order requirement).

• Product/ProductIdentifier and Product/SecondaryProductIdentifier are renamed to Product/ProductId and Product/SecondaryProductId respectively

• The APIs are split in to 2 broad groups based on respective security requirements:-

  • Open Data includes an API which provides Marketed PCA/BCA/Other Information

  • Read-Write (aka “Closed Data”) includes an API which provides Operated PCA/BCA/Other Information.

• Open Data Product information covers:- Core Product, Eligibility, Credit Interest, Overdraft, Features & Benefits, Other Fees & Charges

• In July 2017, as part of Open Data-Account Information design workshop, it was agreed that the Products endpoint should contain a reference to Open Data AND subset of Open Data model (Decision 039 – option 4)

• Approach to supplying product information via the Account and Transaction Information API for v2.x:

  • An optional “Open Data Product ID” link to the Open Data APIs should be retained, so that marketed product information is made available where this is available (this could be more than “Front book” if a bank has decided to retain marketed product information for “Back book” products on the Open Data API.

  • In addition to the “Open Data Product ID” link, we should focus on fields that are provided by price comparison websites today. Although overdraft rates are typically marked as “Negotiable” on PCWs, we feel that it would be useful to provide information about the actual overdraft rate(s) that the account holder is on, even if this cannot easily be used for comparison with other products.

  • If there is a reference to “Open Data Product ID”, then TPP may lookup product features from Open Data. If any element/field of products endpoint are populated, then this should override the default in Open Data (Decision 039 & 100). 

  • The “Open Data Product ID” should be populated by the ASPSP in the products resource if there is a corresponding entry in the Open Data APIs

  • Information supplied in the Account and Transaction Information API v2.x product section must come from account operating platforms.

  • ProductType enumeration matches to types available in Open Data APIs, and ASPSPs may chose to provide any additional product type by closing value=Other in ProductType, and providing a brief type details in OtherProductType data fields, and reference to their Open Data product. At this moment, we don't have detailed Product Info structure for product types other than PCA/BCA.

The resource requires the ReadProducts permission. The resource response payload does not differ depending on the permissions granted.

Data Dictionary for Common Payload between PCA, BCA and other product types.

Detailed usage examples for PCA, and BCA can be found in the Message Implementation Guide section of PCA and BCA sub pages.

Request

Response

Request

Response