Skip to main content

HaaS: Connector for UniVerse

Last Updated: December 3, 2025

See What's Changed

This Schedule outlines the functional requirements for the HaaS: Connector for UniVerse.

  1. Definitions and Interpretations

    1. In this Agreement Terms defined in the Master Service Agreement (MSA) and used in this Schedule have the same defined meaning.

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

  3. Functional Requirements

    The following requirements apply for the delivery of HaaS: Connector for UniVerse.

    1. 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 RequirementSectorsCategoryRequirement
      UDA1Banking & NBLData Adapter APIGet Endpoint Meta
      UDA2Banking & NBLData Adapter APIGet Customer
      UDA3Banking & NBLData Adapter APIGet User
      UDA4Banking & NBLData Adapter APIList Banking Accounts
      UDA5Banking & NBLData Adapter APIList Transactions
      UDA6Banking & NBLData Adapter APIList Payments
      UDA7Banking & NBLData Adapter APIList Payees
      UDA8Banking & NBLData Adapter APIGet User Notification Endpoint
      UDA9Banking & NBLData Adapter APIGet Service Health Status
    2. 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 RequirementSectorsCategoryRequirement
      UR1Banking & NBLRelationship ManagementProvision of OWNER attribute in List Banking Accounts response for accounts with a single owner
      UR2Banking & NBLRelationship ManagementProvision of OWNER attribute in List Banking Accounts response for accounts with a multiple owners (i.e. joint accounts)
      UR3Banking & NBLRelationship ManagementProvision of Power of Attorney where matching the Account Relationship Mapping
      UR4Banking & NBLRelationship ManagementProvision of Secondary Users where matching the Account Relationship Mapping
      UR5Banking & NBLRelationship ManagementProvision of Nominated Representatives where matching the Account Relationship Mapping
      UR6Banking & NBLRelationship ManagementSupport for username to member id lookup within My Viewpoint 3
    3. Product & Transaction Type Support

      Delivery of product and transaction type support as described within the Data Standards:

      Functional RequirementSectorsCategoryRequirement
      UP1Banking & NBLAttribute MappingDynamic population of Banking Account attributes, including features, fees and rates, using Ultracs™ product code to HaaS: Product Manager mappings
      UT1Banking & NBLAttribute MappingSupport for mapping file based mapping from Ultracs™ transaction types to CDR Transaction Types
    4. Integration Capabilities

      Delivery of integration capabilities as follows:

      Functional RequirementSectorsCategoryRequirement
      UI1Banking & NBLIntegrationProvide single sign-on capability for Consumers accessing Client My Viewpoint 3 installation
      UI2Banking & NBLIntegrationProvide Azure Marketplace appliance for connectivity to Client UniVerse database
      UI3Banking & NBLIntegrationSIEM events for UniVerse database activity
  4. Excluded Functionality

    The following functionality is not delivered by Connector for UniVerse (HCU):

    1. Vulnerable User Management: Vulnerable user management for HCU customers occurs via HaaS Manager