Skip to main content

Holder as a Service: Platform

Last Updated: December 3, 2025

See What's Changed

This Schedule outlines the functional requirements for the Holder as a Service: Platform.

  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
      Data Standards
      refers to the Data Standards website hosted at https://consumerdatastandardsaustralia.github.io/standards
  2. Functional Requirements

    The following requirements apply, as prescribed further in the Data Standards, for the delivery of the HaaS: Platform.

    1. Identity Services

      Consumer facing identity services as follows:

      Functional RequirementSectorsCategoryRequirement
      I1AllIdentityComply with the Data Standards Information Security Profile
      I2AllIdentityComply with Financial-grade API Security Profile 1.0 Part 1: Baseline and Part 2: Advanced profiles
      I3AllIdentityIncorporate an arrangement establishment interface (“consent flow”)
      I4AllIdentityStore and maintain CDR Arrangement metadata
      I5AllIdentityIncorporate the CDR Arrangement Revocation endpoint
      I6AllIdentityManage and maintain OAuth2 Tokens in accordance with the Data Standards
      I7AllDCR APIRegister Data Recipient oAuth Client
      I8AllDCR APIGet oAuth Client Registration
      I9AllDCR APIUpdate Data Recipient Registration
      I10AllDCR APIDelete Data Recipient oAuth Client Registration
      I11AllIdentitySupport all prescribed Authorisation Scopes
      I12AllIdentitySupport for Joint Account relationships as outlined within the CDR Rules Division 4A
    2. Holder API Services

      Delivery of current versions of Data Holder exposed endpoints, as defined by the Data Standards, as follows:

      Functional RequirementSectorsCategoryRequirement
      U1AllUnauthenticated APIGet Status
      U2AllUnauthenticated APIGet Outages
      P3Banking & NBLUnauthenticated APIPass through support for the Get Products
      P4Banking & NBLUnauthenticated APIPass through support for the Get Product Detail
      C1AllAuthenticated APIGet Customer
      C2AllAuthenticated APIGet Customer Detail
      B1Banking & NBLAuthenticated APIGet Accounts
      B5Banking & NBLAuthenticated APIGet Account Detail
      B2Banking & NBLAuthenticated APIGet Bulk Balances
      B3Banking & NBLAuthenticated APIGet Balances for Specific Accounts
      B4Banking & NBLAuthenticated APIGet Account Balance
      B6Banking & NBLAuthenticated APIGet Transactions for Account
      B7Banking & NBLAuthenticated APIGet Transaction Detail
      B8Banking & NBLAuthenticated APIGet Direct Debits for Account
      B9Banking & NBLAuthenticated APIGet Bulk Direct Debits
      B10Banking & NBLAuthenticated APIGet Direct Debits for Specific Accounts
      B11Banking & NBLAuthenticated APIGet Scheduled Payments for Accounts
      B12Banking & NBLAuthenticated APIGet Scheduled Payments Bulk
      B13Banking & NBLAuthenticated APIGet Scheduled Payments for Specific Accounts
      B16Banking & NBLAuthenticated APIGet Instalment Plans for Account
      B17Banking & NBLAuthenticated APIGet Instalment Plans Bulk
      B14Banking & NBLAuthenticated APIGet Payees
      B15Banking & NBLAuthenticated APIGet Payee Detail
      E1EnergyAuthenticated APIGet Service Points
      E2EnergyAuthenticated APIGet Service Point Detail
      E3EnergyAuthenticated APIGet Usage for Service Points
      E4EnergyAuthenticated APIGet Bulk Usage
      E5EnergyAuthenticated APIGet Usage for Specific Service Points
      E6EnergyAuthenticated APIGet DER for Service Points
      E20EnergyAuthenticated APIGet Bulk DER
      E21EnergyAuthenticated APIGet DER For Specific Service Points
      E7EnergyAuthenticated APIGet Energy Accounts
      E8EnergyAuthenticated APIGet Energy Account Detail
      E9EnergyAuthenticated APIGet Agreed Payment Schedules
      E10EnergyAuthenticated APIGet Concessions
      E11EnergyAuthenticated APIGet Balance for Energy Accounts
      E12EnergyAuthenticated APIGet Bulk Balances for Energy
      E13EnergyAuthenticated APIGet Balances for Specific Energy Accounts
      E14EnergyAuthenticated APIGet Invoices for Energy
      E15EnergyAuthenticated APIGet Bulk Invoices
      E16EnergyAuthenticated APIGet Invoices for Specific Accounts
      E17EnergyAuthenticated APIGet Billing for Energy
      E18EnergyAuthenticated APIGet Bulk Billing
      E19EnergyAuthenticated APIGet Billing for Specific Accounts
    3. Secondary Data Holder API Passthrough (Energy Sector)

      Pass-through of relevant API calls to the Australian Energy Market Operator (AEMO) for the Energy sector as prescribed with the Data Standards:

      Functional RequirementSectorsCategoryRequirement
      P1EnergySecondary DH APIGet Service Points (SR)
      P2EnergySecondary DH APIGet Service Point Detail (SR)
      P3EnergySecondary DH APIGet Usage for Service Points (SR)
      P5EnergySecondary DH APIGet Usage for Specific Service Points (SR)
      P6EnergySecondary DH APIGet DER for Service Points (SR)
      P7EnergySecondary DH APIGet DER For Specific Service Points (SR)
    4. Regulator Accessible Services

      Services utilised by the Regulator as prescribed with the Data Standards:

      Functional RequirementSectorsCategoryRequirement
      R1AllIdentityManage and maintain CDR Metadata including the use of Get Software Product Statuses, Get Recipient Statuses, Get Data Recipients
      R2AllIdentityMaintain usage statistics for the purpose of reporting metrics via the Get Metrics API
      R3AllIdentityProvide OAuth2 client credentials grant authentication for Regulator access
      R4AllAdmin APIMetadata Update
      R5AllAdmin APIGet Metrics
    5. Consent Management Services

      Services utilised by Client and Consumer for the display and management of established arrangements:

      Functional RequirementSectorsCategoryRequirement
      D1AllConsent DashboardConsumer accessible dashboard aligned to the Consumer Experience Standards and CX Guidelines
      D2AllConsent DashboardConsumer Dashboard branded according to the Consumer Experience Theming configuration
      D4AllConsent DashboardConsumer Dashboard authenticated using one of the methods outlined in Consumer Authentication
      D5AllConsent DashboardConsumer Dashboard capability delivering the pre-approval and non-disclosure options of the Disclosure Option Management Service outlined within the CDR Rules Division 4A.2
      M1AllManagement APIProvide API endpoint for the retrieval of Arrangement metadata
      M2AllManagement APIProvide API endpoint for the cancellation of an established Arrangement
      M3AllManagement APIProvide API endpoint for the listing of Arrangements
    6. Administration Interfaces

      Services utilised by Client for the ongoing management of the Holder as a Service: Platform:

      Functional RequirementSectorsCategoryRequirement
      Z2AllAdministration InterfacesA web based interface for overall system monitoring and management
      Z3AllAdministration InterfacesSingle sign-on support for Client personnel access as outlined within Biza ID