Skip to main content

Verification Testing Suite

Last Updated: December 3, 2025

See What's Changed

This Schedule outlines the functional requirements for the Verification Testing Suite.

  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 Verification Testing Suite.

    1. Ecosystem Access

      1. For Named User (Non-Production) licenses: Provide access to the Biza Test Ecosystem for each of the Client Data Holder Brands.
      2. For Named User (Production) licenses: Provide access to the Consumer Data Right ecosystem operated by the ACCC for each of the Client Data Holder Brands.
    2. Ecosystem Register

      Provide the functionality of a CDR Register as defined by the Data Standards:

      Functional RequirementSectorsCategoryRequirement
      R1AllRegister APIProvide the Get OpenId Provider Config endpoint
      R2AllRegister APIProvide the Get JWKS endpoint
      R3AllRegister APIProvide the Get Software Statement Assertion (SSA) endpoint
      R4AllRegister APIProvide the Get Data Holder Brands endpoint
      R5AllRegister APIProvide the Get Data Holder Brands Summary endpoint
      R6AllRegister APIProvide the Get Data Holder Statuses endpoint
      R7AllRegister APIProvide the Get Software Products Statuses endpoint
      R8AllRegister APIProvide the Get Data Recipients Statuses endpoint
      R9AllRegister APIProvide the Get Data Recipients endpoint
      R10AllRegister CAOperate a TLS certificate authority meeting the Certificate Management requirements of the Data Standards
      R11AllRegister MetadataManage and maintain the metadata required to operate the Register API
    3. General Functionality

      Provide the following general functionality:

      Functional RequirementSectorsCategoryRequirement
      V1AllArrangement EstablishmentAllows for the establishment of a CDR Sharing Arrangement while specifying the Data Clusters and sharing duration, as defined within the Data Standards
      V2AllArrangementAllow for the listing of arrangements previously established by the user.
      V3AllArrangementProvide a JSON based display of thge metadata associated with the arrangement.
      V4AllArrangementProvide the ability to trigger, including modifying Data Clusters and sharing duration, an Arrangement amendment request.
      V5AllArrangementProvide the ability to trigger, via a graphical user interface, an arrangement revocation.
      V6AllAuthenticationSingle sign-on support for Client personnel access as outlined within Biza ID
    4. Data Holder Graphical Access

      Provide graphical access, as a Data Recipient, to the following Data Holder endpoints, as defined by the Data Standards:

      Functional RequirementSectorsCategoryRequirement
      VC1AllAuthenticated APIGet Customer
      VC2AllAuthenticated APIGet Customer Detail
      VB1Banking & NBLAuthenticated APIGet Accounts
      VB5Banking & NBLAuthenticated APIGet Account Detail
      VB2Banking & NBLAuthenticated APIGet Bulk Balances
      VB3Banking & NBLAuthenticated APIGet Balances for Specific Accounts
      VB4Banking & NBLAuthenticated APIGet Account Balance
      VB6Banking & NBLAuthenticated APIGet Transactions for Account
      VB7Banking & NBLAuthenticated APIGet Transaction Detail
      VB8Banking & NBLAuthenticated APIGet Direct Debits for Account
      VB9Banking & NBLAuthenticated APIGet Bulk Direct Debits
      VB10Banking & NBLAuthenticated APIGet Direct Debits for Specific Accounts
      VB11Banking & NBLAuthenticated APIGet Scheduled Payments for Accounts
      VB12Banking & NBLAuthenticated APIGet Scheduled Payments Bulk
      VB13Banking & NBLAuthenticated APIGet Scheduled Payments for Specific Accounts
      VB16Banking & NBLAuthenticated APIGet Instalment Plans for Account
      VB17Banking & NBLAuthenticated APIGet Instalment Plans Bulk
      VB14Banking & NBLAuthenticated APIGet Payees
      VB15Banking & NBLAuthenticated APIGet Payee Detail
      VE1EnergyAuthenticated APIGet Service Points
      VE2EnergyAuthenticated APIGet Service Point Detail
      VE3EnergyAuthenticated APIGet Usage for Service Points
      VE4EnergyAuthenticated APIGet Bulk Usage
      VE5EnergyAuthenticated APIGet Usage for Specific Service Points
      VE6EnergyAuthenticated APIGet DER for Service Points
      VE20EnergyAuthenticated APIGet Bulk DER
      VE21EnergyAuthenticated APIGet DER For Specific Service Points
      VE7EnergyAuthenticated APIGet Energy Accounts
      VE8EnergyAuthenticated APIGet Energy Account Detail
      VE9EnergyAuthenticated APIGet Agreed Payment Schedules
      VE10EnergyAuthenticated APIGet Concessions
      VE11EnergyAuthenticated APIGet Balance for Energy Accounts
      VE12EnergyAuthenticated APIGet Bulk Balances for Energy
      VE13EnergyAuthenticated APIGet Balances for Specific Energy Accounts
      VE14EnergyAuthenticated APIGet Invoices for Energy
      VE15EnergyAuthenticated APIGet Bulk Invoices
      VE16EnergyAuthenticated APIGet Invoices for Specific Accounts
      VE17EnergyAuthenticated APIGet Billing for Energy
      VE18EnergyAuthenticated APIGet Bulk Billing
      VE19EnergyAuthenticated APIGet Billing for Specific Accounts
    5. Automated Testing

      Provide automated testing capability including:

      Functional RequirementSectorsCategoryRequirement
      AT1AllTestingSchema validation and graphical reporting for each API endpoint as described above
      AT2AllTestingProvide an automated test execution capability producing a graphical and CSV based report