Holder as a Service: Platform
Last Updated: December 3, 2025
This Schedule outlines the functional requirements for the Holder as a Service: Platform.
-
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
- Data Standards
- refers to the Data Standards website hosted at https://consumerdatastandardsaustralia.github.io/standards
-
-
Functional Requirements
The following requirements apply, as prescribed further in the Data Standards, for the delivery of the HaaS: Platform.
-
Identity Services
Consumer facing identity services as follows:
Functional Requirement Sectors Category Requirement I1 All Identity Comply with the Data Standards Information Security Profile I2 All Identity Comply with Financial-grade API Security Profile 1.0 Part 1: Baseline and Part 2: Advanced profiles I3 All Identity Incorporate an arrangement establishment interface (“consent flow”) I4 All Identity Store and maintain CDR Arrangement metadata I5 All Identity Incorporate the CDR Arrangement Revocation endpoint I6 All Identity Manage and maintain OAuth2 Tokens in accordance with the Data Standards I7 All DCR API Register Data Recipient oAuth Client I8 All DCR API Get oAuth Client Registration I9 All DCR API Update Data Recipient Registration I10 All DCR API Delete Data Recipient oAuth Client Registration I11 All Identity Support all prescribed Authorisation Scopes I12 All Identity Support for Joint Account relationships as outlined within the CDR Rules Division 4A -
Holder API Services
Delivery of current versions of Data Holder exposed endpoints, as defined by the Data Standards, as follows:
Functional Requirement Sectors Category Requirement U1 All Unauthenticated API Get Status U2 All Unauthenticated API Get Outages P3 Banking & NBL Unauthenticated API Pass through support for the Get Products P4 Banking & NBL Unauthenticated API Pass through support for the Get Product Detail C1 All Authenticated API Get Customer C2 All Authenticated API Get Customer Detail B1 Banking & NBL Authenticated API Get Accounts B5 Banking & NBL Authenticated API Get Account Detail B2 Banking & NBL Authenticated API Get Bulk Balances B3 Banking & NBL Authenticated API Get Balances for Specific Accounts B4 Banking & NBL Authenticated API Get Account Balance B6 Banking & NBL Authenticated API Get Transactions for Account B7 Banking & NBL Authenticated API Get Transaction Detail B8 Banking & NBL Authenticated API Get Direct Debits for Account B9 Banking & NBL Authenticated API Get Bulk Direct Debits B10 Banking & NBL Authenticated API Get Direct Debits for Specific Accounts B11 Banking & NBL Authenticated API Get Scheduled Payments for Accounts B12 Banking & NBL Authenticated API Get Scheduled Payments Bulk B13 Banking & NBL Authenticated API Get Scheduled Payments for Specific Accounts B16 Banking & NBL Authenticated API Get Instalment Plans for Account B17 Banking & NBL Authenticated API Get Instalment Plans Bulk B14 Banking & NBL Authenticated API Get Payees B15 Banking & NBL Authenticated API Get Payee Detail E1 Energy Authenticated API Get Service Points E2 Energy Authenticated API Get Service Point Detail E3 Energy Authenticated API Get Usage for Service Points E4 Energy Authenticated API Get Bulk Usage E5 Energy Authenticated API Get Usage for Specific Service Points E6 Energy Authenticated API Get DER for Service Points E20 Energy Authenticated API Get Bulk DER E21 Energy Authenticated API Get DER For Specific Service Points E7 Energy Authenticated API Get Energy Accounts E8 Energy Authenticated API Get Energy Account Detail E9 Energy Authenticated API Get Agreed Payment Schedules E10 Energy Authenticated API Get Concessions E11 Energy Authenticated API Get Balance for Energy Accounts E12 Energy Authenticated API Get Bulk Balances for Energy E13 Energy Authenticated API Get Balances for Specific Energy Accounts E14 Energy Authenticated API Get Invoices for Energy E15 Energy Authenticated API Get Bulk Invoices E16 Energy Authenticated API Get Invoices for Specific Accounts E17 Energy Authenticated API Get Billing for Energy E18 Energy Authenticated API Get Bulk Billing E19 Energy Authenticated API Get Billing for Specific Accounts -
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 Requirement Sectors Category Requirement P1 Energy Secondary DH API Get Service Points (SR) P2 Energy Secondary DH API Get Service Point Detail (SR) P3 Energy Secondary DH API Get Usage for Service Points (SR) P5 Energy Secondary DH API Get Usage for Specific Service Points (SR) P6 Energy Secondary DH API Get DER for Service Points (SR) P7 Energy Secondary DH API Get DER For Specific Service Points (SR) -
Regulator Accessible Services
Services utilised by the Regulator as prescribed with the Data Standards:
Functional Requirement Sectors Category Requirement R1 All Identity Manage and maintain CDR Metadata including the use of Get Software Product Statuses, Get Recipient Statuses, Get Data Recipients R2 All Identity Maintain usage statistics for the purpose of reporting metrics via the Get Metrics API R3 All Identity Provide OAuth2 client credentials grant authentication for Regulator access R4 All Admin API Metadata Update R5 All Admin API Get Metrics -
Consent Management Services
Services utilised by Client and Consumer for the display and management of established arrangements:
Functional Requirement Sectors Category Requirement D1 All Consent Dashboard Consumer accessible dashboard aligned to the Consumer Experience Standards and CX Guidelines D2 All Consent Dashboard Consumer Dashboard branded according to the Consumer Experience Theming configuration D4 All Consent Dashboard Consumer Dashboard authenticated using one of the methods outlined in Consumer Authentication D5 All Consent Dashboard Consumer Dashboard capability delivering the pre-approval and non-disclosure options of the Disclosure Option Management Service outlined within the CDR Rules Division 4A.2 M1 All Management API Provide API endpoint for the retrieval of Arrangement metadata M2 All Management API Provide API endpoint for the cancellation of an established Arrangement M3 All Management API Provide API endpoint for the listing of Arrangements -
Administration Interfaces
Services utilised by Client for the ongoing management of the Holder as a Service: Platform:
Functional Requirement Sectors Category Requirement Z2 All Administration Interfaces A web based interface for overall system monitoring and management Z3 All Administration Interfaces Single sign-on support for Client personnel access as outlined within Biza ID
-