Version Control

Overview

This specification includes all relevant artefacts for the Open Data Business Current Account (BCA) API Specification.

...

This endpoint can contain multiple brands owned by a particular banking group. Each brand can own multiple BCA products.

BCA

This section covers BCA attributes that will change only under rare circumstances (see CoreProduct section for additional attributes that will be updated regularly). 

The following information can be provided:-

• Product Name i.e. the name marketed to the consumers.
• Identification is the unique id created by the financial institution to internally define the product
• Segment - allows specification of the type of product e.g. basic, regular, premium

MarketingState

Within our design, we have a concept of a "marketing state" for the product. This concept is required because for any "On Sale" BCA product:-

1. The BCA may provide a different offering to the account holder the longer that they hold a particular BCA - covered by StateTenureLength & StateTenurePeriod in the example below.
2. The financial institution can change any of the BCA attributes that are marketed over time - covered by FirstMarketedDate and LastMarketedDate in the example below.

We'll illustrate this with a complex example. 

CMA9Bank has a BCA product that was first advertised on 1/1/2017 and has the following features currently:-

1. If the accountholder takes the product, they are offered a promotional interest rate of 0.5% for 1st 9 months, then 0.2% for next 12 months and then it reverts back to the standard variable rate (e.g. 0%).
   
   

...

1. PredecessorID is used to sequence the creditinterest states offered to the customer when they take out the BCA, it does not record change history.
2. FirstMarketedDate and LastMarkedDate cover the period when the particular marketing state was advertised to the customer.
3. CMA9 Banks only have to provide information for current (and known future, if they wish) marketing states. There is no open data requirement to provide an audit history of all marketing states that ever applied to the BCA. When the future marketing state becomes the current marketing state, the original marketing state information no longer needs to be published.
4. When CP1 Marketing state is replaced by CP3 Marketing state, the PredecessorID in CP2 will also need to be updated to point to CP3, as shown.
5. The Identification column is simply for internal bank use. The ID column is required so that we can sequence states.

Core Product

This sections includes information that can change relatively often. Information to be provided includes:-

• Product URL allows a link to the financial institution's website where more detail about the product can be found
• URL to the product's terms & conditions
• Sales Access Channels cover all of the channels by which a customer can be sold a BCA 
• Servicing Access Channels cover all of the channels by which a customer can receive service for their BCA. Note: This covers servicing of all aspects of the BCA. Some aspects may not be serviceable via certain channels.
• MonthlyCharge covers any monthly servicing charge that a financial institution may make to a BCA accountholder

Credit Interest

In this section, information about the interest rates that are payable to the consumer are listed. Interest rates are typically standard variable rates, with rates potentially changing many times during the course of the products. In addition to the 'Regular' standard variable rates, some BCA products also provide for more attractive 'Promotion' interest rates which are fixed for a relatively short duration. (see MarketingState section above as to how to represent these). 

...

This section has, therefore, been designed to allow the implementer to provide whole and tiered interest rates.

Overdraft/Borrowing

This section allows information to be provided about whole and tiered overdrafts as well as any overdraft/borrowing related fees/charges. Common borrowing charges include:-

1. Arranged and Unarranged overdraft usage fees
2. Fees for exceeding an agreed credit limit
3. Fees where payments are returned due to there being no agreed credit facility available.

Eligibility

In this section, criteria such as residency and trading history restrictions that are necessary for opening an account are provided. Note eligibility criteria for features & benefits are treated in that section. 

Features & Benefits

In this section, information about any inherent product features or value-added benefits (whether they're charged or not) can be captured.

...

For a benefits group or for individual benefits, any eligibility criteria required to obtain that benefit can be specified as notes.

Other Fees & Charges 

Key Fees & Charges that a customer has to pay can be specified in the Core Product,  Overdraft/Borrowing and Features & Benefits sections (see above).

...

Details as to any capping (i.e. maximum amount that can be charged to a customer for a particular period) for any fee/charge can also be specified in this section.

Specification

The following UML Class Diagram provides the hierarchical structure of the message in a graphical form, which is easier to digest.

...

• Data Dictionary - provides detailed descriptions for each field in the message specification along with the associated code lists, constraints and other technical details such as cardinality, any pattern constraints, min, max length etc.
• Swagger - the API specification written using the Swagger API specification format.

Compliance Report

• Compliance Report - highlights changes made to fields & datatypes from v1.x.

Message Implementation Guide

• Message Implementation Guide - provides worked examples of how to implement a particular message specification.

...