Appendices

Common Terminology – Preferred Terms and Language

This version is:

This is the latest version Published 1 year ago 28 Jun 2024

This document is based on existing research undertaken by Open Banking ltd (OBL) over the last 4 years, a detailed audit of existing language used in the market, work undertaken on the naming of dashboards undertaken in early 2021 and an interactive workshop held in June 2021 with a range of participants including ASPSPs, TPPs and consumer experts.

Other pages in this section

Introduction

The purpose of this document is to set out a series of preferred terms and terms to avoid by participants when describing open banking to consumers. We have identified two main language issues in the market:

We have seen the value of simplifying language and bringing consistency in other financial services markets, such as the pensions market which has made significant progress in eliminating unhelpful jargon and bringing greater consistency.

This introductory quote from the NEST work on pensions language could equally apply to open banking:

Words alone are rarely enough to change behaviour, especially when the change is needed on a national scale. It’s relatively easy to persuade someone that saving for retirement is a good idea – provided you can gain their attention in an ever-noisier communications environment. Yet decades of industry experience and academic studies have shown that it’s quite another matter to translate this good intention into action. The behavioural biases that stand in the way of retirement saving are well-known and they can be much more powerful than any positive intention to save.[1]Beyond the Defaults, 2020. See here

This document is based on existing research undertaken by Open Banking Ltd (OBL) over the last 4 years, a detailed audit of existing language used in the market, work undertaken on the naming of dashboards undertaken in early 2021 and an interactive workshop held in June 2021 with a range of participants including ASPSPs, TPPs and consumer experts.

This document is intended as guidance and following its recommendations is recommended but optional for participants.

[1] Beyond the Defaults, 2020. See here

 

Language Principles

In developing this language guide, we have used the following principles, developed and agreed with the Expert Advisory Group which met during May and June 2021

Recommended Language – Data Sharing Journeys

[table id=52 /]

 

Recommended Language – Payment Journeys

[table id=53 /]

 

Recommended Language – Consent Dashboards

[table id=54 /]

 

Recommended Language – Access Dashboards

[table id=55 /]

 

Recommended Language – Variable Recurring Payments (VRPs)

[table id=51 /]

 

Note: Whilst the SWIFT BIC is required to route the payments, for payments in Euro the customer does not have to provide this, the sending bank must derive it from the beneficiary IBAN

References

References
1 Beyond the Defaults, 2020. See here