added

Regular Payments - New Endpoint

We have added a new endpoint, GET payment-instructions that returns details of regular payment (deposits and withdrawals) instruments that are against an account.

added

GET / customers - New sourceSystemId property on the response payload

Customer data that can be pulled from an Account Servicer may not have originated from their system - For example if the Account Servicer is an advised investment platform the customer could have been imported into their system from a CRM. In these scenarios the identifier from the originating CRM system will be populated into the sourceSystemId property.

added

New Servicing Organisations Scope in id_token for Servicing Agents

For Servicing Agent users (e.g. Advisers, Wealth Managers), our OIDC id_token that is returned as part of the Single Sign-on with Tapico now includes the additional scope https://tapico.io/servicing_organisations that contains the identifiers for the Servicing Organisation(s) the user belongs to.

added

GET/instruments - lastChangeDetectedDatetime

A lastChangeDetectedDateTime data attribute has been added to the GET/instruments payload. This signifies the last time a change was detected on the Account Servicer's system.

added

GET/holdings - lastChangeDetectedDateTime

A lastChangeDetectedDateTime data attribute has been added to the GET/holdings payload. This signifies the last time a change was detected on the Account Servicer's system.

added

Transaction type and subtype search

For the GET / transactions endpoint you can now search by type and subtype.

deprecated

GET/authorising-user.userId

userId has been deprecated from the GET/authorising-user endpoint. userId is now under the GET/account-access-consents endpoint. This allows links a consent to a particular Tapico user ID.

added

GET/account-access-consents.userId

userId has been added to the GET/account-access-consents endpoint and deprecated from the GET/authorising-user endpoint. This allows links a consent to a particular Tapico user ID.

improved

Tapico Entity ID Enhancements

Tapico Entity ID {entity}.id is now consistent across authorising users. Previously the Tapico Entity ID would differ for the same underlying source entity when the same entity is accessed via different consents — e.g. distinct authorising users who have access to the same account on the same platform.

added

Launchpad SDK

The launchpad SDK has been updated to allow end-users to search for Apps that they are currently unsubscribed too. Making it easier for end-users to find new Apps and for your Apps to get in front of new end-users.