March '23 ☀️

🌟 What's new? 🌱

We are excited to announce that partners will now have access to additional customization options in the layout tab. These new features will allow partners to have more control over the appearance of their content, and include the ability to set a custom paragraph line height and change icon colors. These customization options are designed to help partners achieve their desired visual style and enhance the overall user experience. We hope these new features will provide partners with more flexibility and creative freedom to make their content stand out.

Here's a screenshot of what it's looking like.

Error Handling 🪝

We are pleased to announce that ConsentUI has been updated to handle and display certain errors more effectively. With this update, ConsentUI will now correctly handle and display the following errors:

Disconnected: If the client's internet connection is lost, ConsentUI will display an appropriate message to indicate that the connection has been lost and the user may need to try again later.

Data deletion in progress: If data deletion is in progress, ConsentUI will display a message to inform the user that their data is being deleted and to try again later.

Connections not enabled for a specific partner API key: If a partner API key does not have connections enabled, ConsentUI will display an error message indicating that connections need to be enabled for that partner API key.

Payments not enabled: If a partner tries to use the payment parameter but payments are not enabled, ConsentUI will display an error message indicating that payments need to be enabled.

We believe these improvements will provide a better user experience for partners and users alike, by providing more specific and informative error messages in these scenarios. We are committed to continuing to improve the functionality and usability of ConsentUI, and we look forward to sharing further updates in the near future. 💙

Consent UI Updates 📣

We are excited to announce that ConsentUI has been updated to display an expiry countdown for MFA (multi-factor authentication) connections, as well as providing the ability for users to retry or go back if the MFA connection expires.

With this update, users will be able to see the remaining time before the MFA connection expires, which will help them better manage their session and prevent any unexpected disconnections. In addition, if the MFA connection does expire, the user will be presented with options to retry or go back to the previous screen, making the overall experience more seamless and user-friendly.

We believe that these new features will provide a more streamlined and intuitive experience for users, particularly those who rely on MFA connections for added security. We are committed to continually improving the functionality and usability of ConsentUI, and look forward to sharing further updates in the future.

Consent Scopes Updates 🚀

We would like to inform our partners that, as part of our compliance with open banking requirements, it is no longer possible to add the account.detail scope without also including the account.basic scope.

This means that partners will need to include both the account.detail and account.basic scopes in any requests that require access to account information. This requirement is designed to ensure that partners are only accessing the minimum amount of data necessary to provide their services, while also maintaining a high level of security and compliance.

We understand that this may require partners to update their existing integrations, and we apologize for any inconvenience this may cause. However, we believe that this change is necessary to ensure that we are complying with industry standards and regulations, and maintaining the highest level of security and trust for our users.

We are committed to providing our partners with the necessary support to make this transition as smooth as possible. If you have any questions or concerns about this change, please do not hesitate to contact our support team. We appreciate your cooperation and understanding.

Discontinued Support ☔

We would like to inform our partners that as part of our ongoing efforts to improve the security and compliance of our platform, it is no longer possible to request unsupported scopes such as Direct Debits and Saved Payees.

This change is designed to ensure that partners are only requesting the minimum amount of data necessary to provide their services, while also ensuring compliance with industry standards and regulations. We believe that this change will help to maintain a high level of security and trust for our users, and reduce the risk of unauthorized access to sensitive data.

We understand that this may require partners to update their existing integrations, and we apologize for any inconvenience this may cause. However, we believe that this change is necessary to ensure the continued reliability and security of our platform.

We are committed to providing our partners with the necessary support to make this transition as smooth as possible.

📘

Future Updates

If you have any questions or concerns about this change, please do not hesitate to contact our support team at [email protected]. We appreciate your cooperation and understanding.

February '23 ☀️

🌟 What's new?

Trusted Advisor Model Update

Trusted Advisor update is live on Consent UI. We will always display Application name.

💰 Payments UI

Payments UI has been updated to use action=payments parameter instead of Capture payment accounts toggle

ℹ️ Consent Scopes

• Removed Direct Debits and Saved Payee scopes from consent permission list. We do not support retrieval of these via open banking

• Updated scope requirements so that account.basic is required when adding account.detail.

January '23 ❄️

🌟 What's new?

ConsentUI has been updated

Now shows Trusted Advisor details when available (if CDR Access Model is TA Organisation or TA Individual)

Trusted advisor can be TA organisation or TA individual.

December '22 🔗

🌟 What's new?

Basiq Customise UI

Partners can use the Layout tab within ConsentUI customise to adjust the fonts, colors, text size and appearance of other elements of ConsentUI.

Read more about this update here.

November '22 ⛅

🎆 What's new?

• Partners can now see if a user has given a consent, and see consent details (date, scopes etc.)
• Partners can now withdraw consent for a user.

API Docs Try Out Button Published 🎉

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...

October '22 ⛅

🎆 What's new?

Introducing FAQ's in BASIQ Documentation

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.

Introducing Creating Payment Sandbox and Production applications via BASIQ Dashboard.

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

Consent UI Updates

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

August '22 ⛅

🎆 What's new?

We've launched our new Consent UI Config! 🎨

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.

🔨 What's Improved?

Handle alternate redirects with the new state parameter

Additional 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 ⚡

July '22 🔗

🌟 What's new?

Basiq ConnectAuth

We are announcing the release of our new ConnectAuth.

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!

June '22 ❄️ :

🌟 What's new?

Basiq ConnectAuth

Enabling access to v3.0 for partners using auth links

 
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.

Stay tuned...

May '22 🍂 :

🐣 What's new?

New data holders!

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. 👏

🔨 What's Improved?

Consent UI improvements

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:

• Support for multiple connections within a single consent flow
• Support to be able to skip the confirmation screen on success of creating a connection

PLUS uplift in the Consent UI's responsive design to ensure a seamless experience across all devices. 📱

Enrich 💰

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.