HaaS: Connector for UniVerse
Last Updated: December 3, 2025
This Schedule outlines the functional requirements for the HaaS: Connector for UniVerse.
-
Definitions and Interpretations
-
In this Agreement Terms defined in the Master Service Agreement (MSA) and used in this Schedule have the same defined meaning.
-
The following additional definitions apply:
- Biza Guides
- refers to the technical documentation hosted at https://guides.biza.io
- CDR Rules
- refers to the CDR Rules published and updated from time to time at https://www.legislation.gov.au/F2020L00094/latest/text
- Data Adapter Specification
- refers to the HaaS source system connectivity specified at https://guides.biza.io/haas/developer-resources/specifications/adapter
- Data Standards
- refers to the Data Standards website hosted at https://consumerdatastandardsaustralia.github.io/standards
- HaaS Minimum Requirements
- refers to the Data Adapter Minimum Requirements specified at https://guides.biza.io/haas/developer-resources/minimum-requirements
-
-
Preamble
The Holder as a Service environment provides a turnkey solution for delivering the Consumer Data Right requirements for mandated Data Holders. To make this functionality available, Biza requires the Client to deliver a set of compatible endpoints referred to as the Data Adapter. For Client installations utilising the Ultracs™ core banking platform Biza makes available Connector for UniVerse which performs translation between Rocket® UniVerse data structures and the Data Adapter requirements.
-
Functional Requirements
The following requirements apply for the delivery of HaaS: Connector for UniVerse.
-
Data Adapter API
Delivery of Data Adapter endpoints in accordance with the Data Adapter Specification and maintained to at least the HaaS Minimum Requirements, as follows:
Functional Requirement Sectors Category Requirement UDA1 Banking & NBL Data Adapter API Get Endpoint Meta UDA2 Banking & NBL Data Adapter API Get Customer UDA3 Banking & NBL Data Adapter API Get User UDA4 Banking & NBL Data Adapter API List Banking Accounts UDA5 Banking & NBL Data Adapter API List Transactions UDA6 Banking & NBL Data Adapter API List Payments UDA7 Banking & NBL Data Adapter API List Payees UDA8 Banking & NBL Data Adapter API Get User Notification Endpoint UDA9 Banking & NBL Data Adapter API Get Service Health Status -
Relationship Support
Delivery of account and customer relationship attributes to enable the utilisation of various account types, including Simple & Complex Accounts, as prescribed under the CDR Rules:
Functional Requirement Sectors Category Requirement UR1 Banking & NBL Relationship Management Provision of OWNERattribute in List Banking Accounts response for accounts with a single ownerUR2 Banking & NBL Relationship Management Provision of OWNERattribute in List Banking Accounts response for accounts with a multiple owners (i.e. joint accounts)UR3 Banking & NBL Relationship Management Provision of Power of Attorney where matching the Account Relationship Mapping UR4 Banking & NBL Relationship Management Provision of Secondary Users where matching the Account Relationship Mapping UR5 Banking & NBL Relationship Management Provision of Nominated Representatives where matching the Account Relationship Mapping UR6 Banking & NBL Relationship Management Support for username to member id lookup within My Viewpoint 3 -
Product & Transaction Type Support
Delivery of product and transaction type support as described within the Data Standards:
Functional Requirement Sectors Category Requirement UP1 Banking & NBL Attribute Mapping Dynamic population of Banking Account attributes, including features, fees and rates, using Ultracs™ product code to HaaS: Product Manager mappings UT1 Banking & NBL Attribute Mapping Support for mapping file based mapping from Ultracs™ transaction types to CDR Transaction Types -
Integration Capabilities
Delivery of integration capabilities as follows:
Functional Requirement Sectors Category Requirement UI1 Banking & NBL Integration Provide single sign-on capability for Consumers accessing Client My Viewpoint 3 installation UI2 Banking & NBL Integration Provide Azure Marketplace appliance for connectivity to Client UniVerse database UI3 Banking & NBL Integration SIEM events for UniVerse database activity
-
-
Excluded Functionality
The following functionality is not delivered by Connector for UniVerse (HCU):
- Vulnerable User Management: Vulnerable user management for HCU customers occurs via HaaS Manager