Data Model

Overview of how the different API endpoints relate to each other

Overview

Tapico Data ModelTapico Data Model

Tapico Data Model


Entity Definitions

Authorising-User

Represents your Application's End-UserEnd-User - Your application's user, and ultimately the person that has given consent to access account information from accounts they are permissioned to and that are held by an account servicer., and is the real world person who executes the Consent JourneyConsent Journey - The workflow provided by Tapico allowing your end-user to give consent for your application to access their financial data., authenticates with their credentials at the Account ServicerAccount Servicer - The entity that holds the account(s) that contains your end-user's account information, e.g. a bank like Natwest or a financial institution like Aviva. Tapico facilitates the connection between your application and the account servicer. and consents to allowing your ApplicationApplication - Your digital application that is represented on and consumes services from the Tapico Platform. to access their data on their behalf.

We support a couple different models with regards to the relationship an End-User might have with their Account Servicer:

The End-User is the account holder. EG: The End-User is an individual in the real world that has consented to give your Application access to Account Information from their bank account. In this scenario they are the customer that has a direct relationship with the account(s).

The End-User is an agent. An agent is someone that has a relationship with the customer that holds the accounts to which the account information relates. EG: The End-User is a Financial Advisor or Wealth Manager that has consented to give access to their account on an Advisory Platform or Wealth Management System. Through that account they manage 1 to n customer(s) who each have relationships with 1 to n account(s).

End-User TypesEnd-User Types

End-User Types

Customer

The real world person that has a relationship with an account. The type of relationship is defined by Customer Account Role attribute.

Account Group

A logical grouping of accounts.

For Example:

  • An Advisor or Wealth Manager might manage multiple accounts as part of a mandate or family group. The account group entity would represent this grouping.

  • The entity is not mandatory in the data model - Customers are mapped to both Accounts and Account Groups, which allows us to support querying at both an Account and Account Group level for a given Customer.

Account

Represents a financial account. These is the entity that holdings and a cash-balances are against.

For Example:

  • A bank account
  • Individual Savings Accounts (ISAs)
  • General Investment Accounts (GIAs)

What’s Next

Enumerations

Different Account ServicerAccount Servicer - The entity that holds the account(s) that contains your end-user's account information, e.g. a bank like Natwest or a financial institution like Aviva. Tapico facilitates the connection between your application and the account servicer. may use different naming conventions for enumerations such as account types, transaction types etc. Where an entity has a type enumeration, the account servicer (source) names are included in the corresponding APIs via a sourceType property.

Tapico maps these source types to a set of normalised enumerations contained in type and optionally subType. These normalised enumerations are described below.

Entity Enumerations

Did this page help you?