April '22

by Bridget Turnbull

April '22 🐰

🔨 What's Improved?

Consent UI

Once again, this month we've seen more improvements made to the Consent UI, making our partners lives easier. The Consent UI now handles decisioning to create a more logical flow for your users. The Consent UI now checks for any updates to the policy since their last login, and if needed, will direct them to accept the new consent policy before proceeding.

Take a look at the decision process below..

2708

Enrich

We ❤️ Enrich! So we gave it some TLC.

Our team has been working for a few months on improving how we enrich our data. These changes have resulted in substantially more efficient, more reliable, and more accurate results. All you need to do is reap the benefits.

Connection time for OB connections

As we go down our CDR path we are always looking for ways to improve! This month, we found a way to drastically reduce the time it takes for Open Banking connections to complete. We know it was fast before, but why not make it faster?

March '22

by Bridget Turnbull

March '22 ☀️

🌟 What's new?

Slick new API Docs

 

 

Introducing the fresh, new API docs that version 3.0 deserves:

  • Interactive code snippets
  • Examples in over 20 different languages!
  • Better in-context error documentation and examples

In order to enable partners to manage their users consent across both CDR and non CDR applications, they can now use the API to:

  • delete a users consent directly, or
  • retrieve the current, active consent for a user

New Open Banking Connectors

  • We've added 50 (yes, FIFTY) more institutions to the Open Banking ecosystem! Check out all of our available connectors for both DDC and Open Banking in your dashboard.

🔨 What's Improved?

Consent UI

Our v3.0 Consent UI is always evolving, and this month has been no different! UI tweaks have been made to improve look, feel and performance, as well as adding action parameters allowing you to define the flow of your user's journey.

We also strengthened security 🔒 by requiring the userId to be bound to the access token when launching the Consent UI.