Overview

Your digital application is represented on the Tapico Platform by the ApplicationApplication - Your digital application that is represented on and consumes services from the Tapico Platform. entity. It is your Application that consumes services from the Tapico Open Finance API.

Under your OrganisationOrganisation - The entity that represents your company on the Tapico Platform. Anything that you or any other member of your Organisation creates on Tapico will be in the context of your Organisation. you can create as many Applications as you like. and consumes services from the Tapico Platform.

1. Create an Application

Input basic details for your application such as Name, Summary, Category and a Description.

You can also add informational links for your business or application such as your Website URL, Terms and Conditions.

These are displayed to the user when your application is deployed to the Tapico App Store.

2. Select a Service

Under Application → Services, click + ADD and select the "Open Wealth" Service Pack - This will allow you to connect to Open Finance API.

🚧

Open Wealth API Access

Service pack subscriptions must be approved by the owner, in the case of the Open Wealth Service Pack this is Tapico. You will receive an email notification once it has been approved.

3. Adding Account Servicers

Under Application → Open Wealth → Account Servicers click + ADD to add to link the financial institutions (referred to as 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. that you want your application to connect to.

🚧

Account Servicer Access

Links to Account Servicers will need to be approved by Tapico. You will receive an email notification once it has been approved.

4. Select Consents

Under the Open Wealth service pack, configure the ConsentsConsents - The data categories your application will receive regarding an end-users account information. The end-user will review and accept these consents during the consent journey.s you want to request from your 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. (known as Authorising-UserAuthorising-User - A user of your application who is also a user of one or more Account Servicers. The Authorising User is the person who authorises your application to access data on their behalf from Account Servicer Platforms. See also: End-User. in the API).

For more details on consents and how they map to API Endpoints see the ConsentTypes guide.