Skip to main content

πŸ”‘ Key Terms

HaaS (re)uses a number of key which are defined below.


Account​

For HaaS the term Account refers to the Account component according to Consumer Data Right (CDR). For Banking this is a specific Bank Account, for Energy this is a specific billing contract. We deliberately specify what Account is because it is often used interchangeably between a billing account, Principal and User ID.


Account Owner​

An individual or entity that is legally responsible for an account (i.e., a bank or utility account).


Account Identifier (accountId)​

This is a unique identifier specifying an account within a backend system. It is not, typically, the customer known account number but rather the internal database handle for an account.


Arrangement​

The term used by the Consumer Data Standards (CDS) to describe an establish sharing agreement. Biza refers to this as a type of Grant, ostensibly Sharing Arrangement V1. Please see β€œconsent” for the corresponding Biza definition.


Arrangement ID (Grant ID)​

A unique identifier associated with a consumer’s consent to share their data with an accredited data recipient.


Authorisation Scopes​

Define the specific types of consumer data that an Accredited Data recipient can request from a data holder. Authorisation scopes are presented to the consumer during the consent process, allowing them to control what data is shared. Please see Data Cluster for the corresponding CDS term.


Authority to Operate​

Authority to Operate (ATO) is, in essence, an "impersonation" capability where a specific User is granted the ability to perform actions as if they were a specific principal. This applies primarily to individual Principals.

info

ATO is different to Nominated Representative


Brand​

Refers to the brand name of a data holder registered in the CDR register. Brands assist with identifying different products offered by data holders in the same sector (e.g., business banking products and retail products) and across different sectors (e.g., banking products and energy products).


Change Control Management​

Biza uses this term to refer to the structured approach for planning, reviewing, approving, and implementing changes to the Biza platform and infrastructure.


Client​

See software product


Consumer Data Standards (CDS)​

The binding technical specifications released by the Data Standards Body (DSB). Often shortened to simply Data Standards which is the same reference used in the CDR Rules.


Biza uses this term when a consumer agrees to share their CDR data with an accredited data recipient for a specific purpose. Please see β€œarrangement” for the corresponding CDS definition.


Biza typically describes the screens used to receive consent for establishment of an Arrangement as the Consent Flow. Within the Data Standards CX Guidelines this is referred to in a number of ways, most frequently as Authorisation to Disclose.


Consent Management Dashboard refers to the Consumer accessible online dashboard prescribed by the Standards, for both Holders and Recipients, that provides Arrangement management. It is prescribed through a combination of Standards and Guidelines.


Customer​

A person who gives permission for their information to be used by a Software Product.


Customer Context (HaaS Manager)​

Refers to a specific customer who the HaaS Manager user in operating the interface on behalf of.


Data Cluster​

The term used to describe the authorisation scopes within an Arrangement.


DOMS​

The Disclosure Option Management Service (DOMS) is the term used by the CDR Rules and Data Standards Body to describe the permission management system for Joint Accounts within the CDR.


DOMS Request Identifier​

The unique identifier of a request workflow to alter the DOMS status on one or more accounts.


DSB​

Data Standards Body (DSB) is the team within Treasury responsible for the definition of the binding Data Standards and the CX Guidelines.


Grant​

This is the term used by Biza (and ostensibly OAuth2) to describe an established set of tokens providing permissions to designated APIs and is essentially a record of the permission given by the customer to use their information to execute actions. Currently, within the CDR the only Grant structure supported is the Sharing Arrangement V1 structure.


The HaaS environment differentiates between an access arrangement (Grant) and the actions that took place to establish that arrangement. Biza refers to these as a set of Grant Consent events. Examples of such events include extending the length of a grant, adding additional scopes and/or accounts.


HaaS Manager​

The tool provided by Biza for administrators to manage and oversee their HaaS Instance.


Individual Account​

An account owned by an individual consumer.


Instance​

A reference to your organisation's specific installation of the Holder as a Service (HaaS) solution.


Joint Account​

Refers to an account that is held by two or more individuals with a CDR data holder (such as bank or energy provider) where each account holder has equal ownership of that account.


Non-individual / Business Accounts​

An account for a firm, partnerships or the corporates to be opened and operated for their business needs.


Nominated Representative​

Nominated Representative is an individual nominated by the non-individual consumer who is able to give, amend, and manage authorisations to disclose CDR data on behalf of the non-individual consumer (e.g., a Director in a company). There may be more than one nominated representative.


MPA​

Multi Party Accounts (MPA) is the term that Biza uses to refer to its implementation of permission management for accounts accessible by more than one account.


Principal​

In the context of HaaS and the CDR, a Principal refers to a single entity for which data is being shared. This could be either an individual consumer (person), or a business entity that may have multiple users.

Biza adopted this term to provide clarity, as different customers define end-users in various ways. Essentially, the Principal is the entity on whose behalf dat is being shared.


Principal Identifier (principalId)​

The Principal Identifier is a globally unique identifier for the Principal.
Biza distinguished an entity as either being an individual (e.g., a person) or a non-individual (e.g., a business, partnership etc) where either entity will have a unique Principal ID assigned to it.


Principal Selector​

This refers to an optional step within the consent flow that presents a list of principals to operate on behalf of.


Power of Attorney (PoA)​

A PoA is a legal authority that allows one person (the attorney) to act on behalf of another (the principal) in making financial and data-related matters.


Recipient​

The legal entity (Accredited Data Recipient) that received the grant.


Recipient Brand​

The brand name of the recipient.


Red​

Refers to Production spaces/environments.


Release Management​

Biza uses this term to describe the controlled deployment of software updates including new features, and regulatory changes. This process is described in Biza Guides.


Secondary User​

A secondary user within the HaaS environment relates to users (as identified by their userId) that have access to a specific Principal (Account, Account Holder or Account Holders) with actions to be associated directly with that user (as opposed to impersonating them).


Secondary User Instruction​

This is an instruction given by a Consumer to enable CDR sharing, by a Secondary User.


Series​

Refers to a major HaaS Software release,


Software Product​

The software installation used by the Data Recipient to request the creation of Grants.


Truth Clusters​

Refers to a grouping of data which can either be sourced/set within the HaaS environment or read from an external system via the Data Adapter. In a number of circumstances HaaS supports using an external system to determine certain settings associated with a User.


Updates​

Refers to the releases within a Series.


User​

A User within HaaS is an authenticating end user (essentially a human) who performs actions on one or more Principals.


User Identifier (userId)​

The User Identifier is a unique, immutable identifier representing a human user. While it may be the same as principalId this isn't implicitly the case as a Principal may represent a Company with more than one individual User Identifier.


User Principal​

Refers to a Principal.


Username (username)​

The Username is the login that the customer is aware of and inputs into their digital experience and, in most cases, the first page of the CDS consent flow.


Vulnerable Customer​

A vulnerable customer is an end-user who has been identified by the Holder as vulnerable and for which vulnerability handling shall apply.


Yellow​

Refers to Non-Production environments/spaces.