We are excited to share the latest updates and improvements we've made to the API, dashboard and Basiq Connect in October 2024. These updates focus on enhancing user experience, improving connectivity, and providing more accurate data insights. Here's what's new:
Enhanced Consent Management in Dashboard & Basiq Connect
π Consent Screen Refresh: The Basiq Dashboard consent request screen and Basiq Connect have been updated to improve user experience and expand functionality.
π Unified Query Parameters: Basiq Connect now supports the same query parameters as the Basiq Consent UI. Dashboard users can now:
Request consent extensions.
Target specific institutions.
Update consent settings or reauthorize existing connections.
Request Consent with various options
π¨ Customizable Purpose Selection UI
Partners can now select from a list of predefined templates when specifying the purpose of their consent request.
π οΈ Want a unique purpose?
Partners can still add custom purposes by selecting the last option in the list.
Purpose with - Add a custom purpose at bottom
π§βπ« Sandbox Personas & Use Cases Update
New Personas Added for Real-World Testing Scenarios:
Wentworth-Smith (whislter): Joint account, stable income, mortgage, car loan.
Whistler (ShowBox): Fortnightly salary, BNPL, large transfers, and minimal daily expenses.
Gilfoyle (PiedPiper): Unemployment benefits, BNPL with late fees.
gavinBelson (hooli2016): Salary + tutoring, personal loan, steady expenses.
jared (django): Uber income, mortgage, volatile earnings.
richard (tabsnotspaces): High stable income + rental, multiple credit accounts.
We are excited to share the latest updates and improvements we've made to the API and Dashboard in September 2024. These updates focus on enhancing user experience, improving connectivity, and providing more accurate data insights. Here's what's new:
π New Event Types for Partners
Partners can now subscribe to three new event types:
We are excited to introduce our Income Verification Tutorial, designed to help users automate the process of verifying their income. This tutorial provides guidance on securely connecting bank accounts and generating comprehensive income reports using the Reports API.
We are excited to share the latest updates and improvements we've made to the API and Dashboard in August 2024. These updates focus on enhancing user experience, improving security, and providing more accurate data insights. Here's what's new:
π Consent Management Enhancements
Mandatoryaccount.basic Scope: To streamline consent management, the account.basic scope is now a required field in the Customiser UI for Consent Management. This applies to:
Platform > Consent Management > Consent Scopes: Learn more
We have added a new revoked field to the GET Consent API to indicate the date a consent was revoked. This field will be populated when user consent is deleted or when a user is deleted. The revoked field uses the format: now().UTC().Format(time.RFC3339).
Improved Metrics Logic: Metrics are now calculated using deduplicated transaction sets, resulting in more accurate data points. Previously, transactions that appeared in multiple groups could cause skewed metrics due to duplication. This update ensures that each transaction is counted only once, even if it falls under multiple groups.
Multi-Factor Authentication (MFA) is now enforced to enhance the security of our systems. For more details, please check our documentation.
π Improved CDR Receipt Notifications:
Consent Creation Notifications: Notifications are now sent only upon CDR connection activation, preventing unnecessary alerts.
π Web Connectors Update
Greater Bank: Updated the web connector to accommodate recent changes to Greater Bank's online banking portal.
π New Data Holder Coming Soon: Liberty Financial Pty Ltd
We are pleased to announce that Liberty Financial Pty Ltd will soon be added as a supported data holder in our Connectors API. Liberty Financial has recently become available for Open Banking, and we are working to ensure our platform supports this institution.
We are excited to expand our support for Open Banking by including Liberty Financial Pty Ltd and look forward to providing you with enhanced connectivity and services. Stay tuned for further updates on the availability of this new data holder in our Connectors API.
Stay Updated π’
If you have any questions or need further assistance, don't hesitate to reach out to our support team.
We're thrilled to announce significant improvements to the Basiq API & Consent UI.
New Features π
Consent History in Consent UI - Manage Action
On the Consent Management screen, you can now view the history of previously expired/revoked consents. Additionally, if you trigger action=manage with no active consent, a list of all previously revoked or expired consents will be displayed. You can read more here.
Enhancements β¨
DH Authorization Errors in the Jobs Endpoint
Enhanced Error Reporting: If the DH authorization flow is not successfully completed by the user (e.g., user cancels the flow or encounters other DH-related issues), the error details are now exposed in the jobs endpoint. This helps our partners better understand the issues.
Basiq Connect (AuthUI)
The length of the OTP code has been increased from 4 to 6 characters to enhance security.
We have updated the appearance of the Trusted Adviser (TA) banner and popup for a more streamlined and user-friendly experience. Additionally, we have added a TA disclaimer message above the consent confirmation button to provide clearer information and improve the overall transparency of the consent process. You can read more here.
Stay Updated π’
If you have any questions or need further assistance, don't hesitate to reach out to our support team.
π Authenticator Apps for 2FA: The Basiq Dashboard now supports Authenticator apps as a method for Two-Factor Authentication (2FA). We will gradually prompt users who have not enabled 2FA to set it up, and eventually, it will become mandatory.
π MFA Connection Status: The Basiq Dashboard now accurately displays the status of Multi-Factor Authentication (MFA) connections.
π Product Updates
Please find below the key highlights of the latest features and improvements our team has released over the past few weeks.
π€ Enhanced User Connections Visibility: All connections, except for deleted ones, are now visible through the get user connections endpoints. This improvement enhances the developer experience and provides better visibility during the initial stages of the Consumer Data Right (CDR) journey.
π New Events for Enhanced Notifications: We have added new events for account.updated, connection.invalidated, and transactions.updated. These events enable our partners to set up notifications based on more meaningful and specific triggers.
π Extended Connectors Endpoint: The connectors endpoint has been extended with new CDR fields, offering more comprehensive data integration capabilities.
π§ cdrEmail - The email address for CDR-related inquiries.
π cdrPolicy - The URL to the CDR policy document detailing the institution's data practices and consumer rights.
π’ cdrProviderNumber - A unique identifier assigned to the CDR institution by the CDR program.
ποΈ Improved Data Deletion Process: Our data deletion process has been refined to ensure more efficient handling of data.
β CDR Compliance Updates: We have updated our CDR compliance with the ACCC CDR Exemption register. Additionally, we've added a CDR Policy Link, CDR Support Email, and CDR Provider Number on the Business Consumer Consent (BCC).
π New Account Verification Guide: Weβve created a simplified βHow-Toβ guide on Account Verification. Previously, we only had the starter kit. This new guide allows customers to see prerequisites, flow, and screens used for Account Verification. The new guide can be found here.
π Connection Status Documentation: All connection statuses, including Pre-init, are now defined in our documentation. You can find the details here.
π¨οΈ PDF Report Retrieval via API: You can now retrieve PDF format directly from the API. Previously, this was only possible via the Dashboard. For Statements & reports, PDFs are retrieved when using the Accept header (application/pdf) on a GET request. Only portrait mode is supported.
π Payments Feature Sunset
We've officially sunsetted the Payments feature from Basiq. As part of this, the Payment APIs and Payment Guides have been removed from our Developer Hub.
Stay Updated π’
If you have any questions or need further assistance, don't hesitate to reach out to our support team.
Account Updated Event Released: We're excited to announce the launch of the Account Updated Event! π Stay up-to-date with the latest account changes instantly.
New Payment Details in CDR:
Weβve introduced new paymentDetails fetching capabilities through CDR:
BPAY Options:
billerCode: Instantly identify your biller.
billerName: Clearly see who you are paying.
crn: Use Custom Reference Numbers for simplified payment tracking.
apcaNumber is also now available for more streamlined banking transactions. π¦π³
Dashboard Updates: We have added 2 additional fields in the dashboard customiser: Reference name and Manage consent URL. The values of these fields will be shown in the Cancellation modal and Manage your data sharing modal. π οΈπΌ Read more details here.
Enhancements β¨
Reports for Multi Users: Generate comprehensive reports for multiple users at once. More power to team management! π You can read more details here.
Expense Details Update in Dashboard: We've refined how expense details are presented on your dashboard for users of Affordability, making it easier to track your spending and manage finances efficiently. π
π
Note
This update is specific to the Affordability product, and does not apply to Insights/Reporting.
Improvements π§
Updated Upload Statement Form on Basiq Dashboard:
To improve customer experience and minimise errors, we now require partners to select a file format before uploading a statement. This ensures compatibility and prevents uploads for unsupported institutions. ππ
API Updates π
New Event in Production:
The connection.invalidated event is now live in production. This event is triggered when a connection status changes from active to invalid due to user-related errors. The specific user-related errors that will trigger this event for web and OB connections are as follows:
Web Connections:
π user-action-required.
β invalid-username-or-password.
π« invalid-connection.
π locked-account.
π multifactor-required.
OpenBanking Connections:
β³ expired CDR arrangement - user didnβt re-authorise.
β οΈ any issue occurred during user re-authorisation.
We're continuously working to make our services better for you! Keep the feedback coming! π
We're thrilled to announce significant enhancements to the Basiq Dashboard. Here's what's new:
π Enhanced Reports and Statements Generation
PDF Statement Generation: Partners enabled for Reports can now generate PDF Statements directly from the User Account detail screen, integrating with our robust Bank Statements APIs by Insights.
Per-Partner Enablement: To enable this feature for new partners, please reach out to our Support team.
β¨ UI Redesigns
Redesigned Signup and Login UI: We've updated the appearance of Dashboard registration, login, and other related screens to align visually with our redesigned Basiq website.
SSO/Azure Partners: The login prompt has changed from 'Login with AzureAD' to 'Sign in using SSO' to better reflect the authentication process.
π§ Dashboard Functionalities
Configurable Access: Access to the Reports screen and the ability to generate statements within a user account is now configurable through our Support team.
Improved Feedback Mechanisms: The Dashboard now displays success and error messages more accurately. JSON output for reports now presents the full report data.
Visual and Wording Updates: Various UI elements and phrases have been refined for clarity and usability.
π οΈ Improvements and Bug Fixes
Statement Uploads: We've made several enhancements to the upload statements form as we prepare to transition partners from the Classic Dashboard.
Bug Fix in Permissions: Resolved an issue where Partners sometimes faced difficulties assigning permission sets to Members.
π Identity Endpoint Enhancements
Expanded Schema: The schema for GET /identities and GET /identities/{identityID} has been expanded to include two new fields: connectionID and institutionID.
π
π Your Feedback Matters!
We are continuously looking to improve, especially in enhancing our Statement functionality. Please keep sharing your valuable feedback!
We're excited to announce some key changes aimed at enhancing the experience for our partners on Basiq Dashboard and Basiq ConsentUI. Here's a rundown of what's new:
Business Consumer Changes πΌ
We've rolled out Business Consumer changes to Basiq Dashboard and Basiq ConsentUI.
Business Applications: Partners can now seamlessly create Business applications directly through Basiq Dashboard.
Creation of Business Users: Partners now have the capability to create Business users complete with Business-specific fields.
Enhanced User Interface: Business details are now conveniently accessible in the side menu of the User screen in Basiq Dashboard.
Expanded Features for Business Users: Business-type users can now access additional fields within the ConsentUI.
Open Banking Scopes: Business-type users can easily create and share business scopes via Open Banking.
Customiser Enhancement
Custom Brand Name: Partners can now configure the name displayed to their customers in the Customiser. Which is now a required field.
Mandatory Brand Name: We've made Brand name a mandatory value for all applications, including non-Business Consumer Changes (BCC). Partners who haven't defined it yet will be prompted to do so the next time they edit ConsentUI.
Removal of Payment Application Option: With this update, we've removed the option for partners to create Payment applications.
If you have any questions or need further assistance, don't hesitate to reach out to our support team.