Hey Guys,
We have pushed Try Out Button on our API docs for you to play with our APIs.
Eager to Try out 🔨
This is what you will receive as a response...
We are introducing FAQ's in our documentations for our partners to open discussions. Please feel free to open a thread and someone will get back to you as soon as possible.
Our Partners can now Create Payment Sandbox and Production applications (or edit existing ones). Whenever a Payments Production app is created, please contact us on [email protected] to the team to proceed with your application enablement.
Payments: Head over to the dashboard to check it out
Partners can now pass a connectionId parameter in the URL to initiate a credential update flow. This only works for non-CDR connections.
Users will now see their previous connections pinned to the top. If a user taps on a CDR connection that they already exists, an ℹ️ popup will appear
You can read more about the consent UI and other actions available here
Our Consent UI was the first step in providing Fintechs with an out of the box solution to manage the complex nature of capturing customers consent to access their financial data.
Now its even easier for teams to customise their consent policy fields and UI directly from Basiq's dashboard editor! Read our blog post on it here.
state parameterAdditional parameterstate available when using our Consent UI, allowing partners to track state after redirect.
This enables partners to be able to launch the consent UI from more than one location in their app, and ensure their user resumes the journey in the same place. For example, the user may skip the bank connection step during their initial onboarding flow, but decide to connect from a separate settings page later on ⚡
All links generated by our all partners via BASIQ Dashboard will use the new version of ConnectAuth on https://connect.basiq.io to support v3.0 of the API.
This release enables our partners to customise the text, list of institutions, add redirect links to their web pages and more ⚡
More customisation options will become available with time, as we continue improving the Basiq Dashboard 🎨
This update is already relatively mature, since it's used by our Open Banking enabled partners, so it's ready to adopt and we can't wait for your feedback!
While we work on upgrading https://connect.basiq.io to support v3.0 of the API, we have released an npm package for our partners who are itching to access CDR data. ✨ This UI component handles the 2FA before redirecting the user to the Basiq Consent UI. All it needs is the ID generated when creating an auth link. Check it out here.
The addition of even more connectors means we have reached 100 Open Banking Data Holders available via the Basiq platform! Check it out on your Basiq dashboard - there are new connectors being added all the time. 👏
We are always striving for greatness, so of course there have been many updates to our Consent UI to improve the experience of both our partners, and their users. More flexibility in the Consent UI now exists through:
PLUS uplift in the Consent UI's responsive design to ensure a seamless experience across all devices. 📱
Enrich has entered the world of CDR! We've added support for 3.0 tokens on the /enrich endpoint, as well as improvements to the efficiency & security to the Enrich service.
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.
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.
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?
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, orOur 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.