Working with existing aggregators

We often get asked what the process looks like of working with Bud if a client is already working with an existing aggregator, in this guide we will look to document and walk you through the options that are available to you as well as the benefits of each.

The Bud platform is set up in a way that we're agnostic to the aggregation method, this means if you're already working with a third-party aggregator you have the choice between continuing to use them for data aggregation or replacing them with Bud.

Continuing with your existing aggregator

If you're happy with your existing aggregator's abilities to ingest and refresh data but you want to make use of Bud's market-leading enrichment you can do so by utilising our first party ingestion endpoints.

These endpoints have the ability to ingest both account and transaction data into the Bud platform, that you have already aggregated. Once ingested the data will be enriched and made available via Bud's various endpoints. A variety of both transaction and account formats are available and upon request we can also map data to any major third-party aggregator's format, this ensures that you won't need to manipulate or map your data before passing it onto Bud.

The benefits of this approach are that you can continue to reuse existing customer AIS consents meaning there is minimum disruption for your existing customers and their user experience.

Changing aggregator to Bud

If you're looking to replace your existing aggregator, Bud can also support this. We're fully licensed in the UK for AIS capabilities and allow your customers to connect to over 60+ UK banks, a full list of our coverage can be found here.

If you're not licensed for AIS activities we have a customisable connection journey that can be tailored to your brand, alternatively, if you do have your own license we can also accommodate acting as a technical service provider (TSP) ensuring you retain full control over the user journey. More information about Bud's Connect product can be found here.

The benefits of changing aggregator are that it will typically be cheaper than paying two suppliers, however, due to technical limitations with Open Banking consents, you will need your customers to reconsent with their bank in order to share their information directly with Bud. Due to the friction that this may cause your customers, clients often choose to migrate existing customers slowly as and when they naturally have to reconfirm their consent with their bank. In these situations, clients typically opt for a dual approach where they slowly migrate customers from old consents with your existing aggregator onto new consents with Bud whilst utilising the first party ingestion endpoints to handle the enrichment of all of your customer's data.

If you have any questions, please contact us via the chatbot (bottom-right of screen 👉) or via a support request or check our FAQs.