Skip to main content

❓ Frequently Asked Questions

Contact Us​

How do I contact Biza?

The best way to contact us is via a service desk ticket. Instructions for doing so can be found HERE

Multi Party Accounts​

The implementation of Joint Account support within the CDR has introduced significant ambiguity in both the Rules and Standards and how to deal with various situations. We provide, and will continue to expand, a collated list of frequently asked questions here to provide as much clarification as possible.

Is it possible to opt out of individual accounts or only joint accounts?

Individual Accounts cannot be opted out. Only those designated as Secondary User Accounts (i.e., had a secondary user registered on them) and Joint Accounts are currently in-scope for Disclosure Option Management Service (DOMS) behaviours.

What is the behaviour of existing arrangements when one or more accounts are switched to Non Disclosure?

The arrangement remains active with all accounts still present however technical access is suspended for the account and existing access tokens are immediately revoked forcing a refresh of permissions.

Source: DSB Implementation call on 2022-02-10

If one party is <18 and the other is >=18 is the account eligible?

The account is ineligible.

Are ineligible accounts required to be shown in consent flow?

No, this remains a MAY and is therefore not a hard requirement.

Is there a cost difference between Truth Cluster selection?

No, HaaS is all-inclusive of any combination of features.

Is Vulnerability at the Consumer or Account level?

Vulnerability flag is at the Principal (Customer) level and this is, in reflective scenarios, in the context of another Principal (Customer).

Whether the vulnerability status of a Principal is relevant depends on the scenario, i.e., for a single user account type the fact the user is vulnerable would have no effect on the behaviour of the HaaS environment.

Do the Secondary User Notifications use the same Notification APIs as Account Owners

Yes. The notification API will be used in the same way between normal account owners and secondary users. Secondary User identifiers will be provided within the from attribute of the notifications.

If the account holder is marked vulnerable, can a Secondary User still create a data sharing arrangement?

Yes. A vulnerability flag never blocks the creation of a data sharing arrangement β€” it only changes behaviour (notifications are suppressed, arrangements are stored as private, and joint-account approval steps are bypassed). Vulnerability is evaluated for the Consumer performing the action; it is not a barrier to sharing for any other party, including a Secondary User on that account.

See Vulnerability and Secondary Users β€” Account Holder Restrictions.

If an account holder has a Legal / Call Centre / Ineligible block, can a Secondary User still create a data sharing arrangement?

These blocks are communicated by the Data Adapter to HaaS as an HTTP 451 response on the Get User or List Accounts calls. A 451 is scoped to the user and principal of that specific request β€” it is not evaluated per account.

Because a Secondary User authenticates as themselves, against their own principal, a block applied to the account holder's principal does not cascade to the Secondary User. Cascading it would incorrectly suppress any of the Secondary User's own unrelated accounts.

To prevent a Secondary User from sharing a specific account, the Data Adapter should remove that Secondary User's relationship to the account in the List Accounts accountCustomers response. HaaS will then disable the Secondary User Instruction and revoke any existing active arrangements for that account.

See Secondary Users β€” Account Holder Restrictions.

Holder as a Service (HaaS)​

Why is it called Multi Party Accounts (MPA)?

When initiating design to meet the currently known Joint Accounts and Notification obligations we wanted, as best as we can, to design for the (likely) future of accounts with more than simply two accounts. As we continued on our discovery of the requirements of the Joint Accounts components we also discovered that, in fact, Joint Accounts when combined with Authority to Operate or Secondary User behaviours were >2 accessors each with their own CX and data disclosure behaviours.

Thus, we decided upon Multi Party Accounts as the name for our feature. As we can't predict the future we may end up with Multi Party Accounts V2 but we hope to have at least forward planned for this possibility.

Why are Notifications separated?

Fundamentally when the Data Standards Body announced a combination of Joint Accounts and Notifications together we found ourselves asking why one action was being implicitly coupled to the other purely based on known business rules.

Consequently, while we acknowledge that Notifications are linked to the Joint Account requirements, and the delivery timelines are aligned, we foresee a highly likely requirement for notifications unrelated to the feature at hand right now and, therefore, separate them while linking where appropriate.

Data Adapter​

If the data adapter only supports V1 (for example), but a getEndpointMeta request is received where x-haas-max-v = V0, can the data adapter respond with V1?

No, the getEndpointMetadata operation is the only endpoint where multi-version support must be implemented if you choose to advance ahead of the currently supported version of this endpoint.

Mandatory reporting to the ACCC/OAIC​

What are my reporting obligations?

Data holders must submit CDR reports twice a year to the ACCC and OAIC. These reports must be in an approved format and contain specific information (here you will find further information for banking and energy). Biza helps you meet your reporting obligations by providing you with a report that covers all the necessary metrics collected by us.

When and how will I receive my report from Biza?

The reports will be sent to you approximately 1-2 weeks prior to the ACCC/OAIC deadline. They will be sent to you as a PDF file via a Service Desk ticket to the contacts we have on file.

When are the reports due to the ACCC/OAIC and how do I submit it?

See the table below for report due dates

Reporting periodDue by
1st January - 30th June30th July
1st July - 31st Decemeber30th January

To submit your reports you complete an online web form in the CDR Participant Portal. See the relevant section of the CDR Participant Portal user guide for more details.

What does my organisation need to provide for the reports?

You will need to provide the information below.

  • Total CDR Consumer Complaints Received
  • CDR Consumer Complaints by Complaint Type
    • Total CDR Consumer Complaints Resolved
    • Complaints Resolved in this Reporting Period
    • Complaints Resolved in previous Reporting Period
  • Average number of days to resolve complaints through internal dispute resolution
  • Complaints referred to external dispute resolution
  • Complaints resolved by external dispute resolution.

For further information about the specific requirements in your sector, see here for banking and here for energy.

What information does Biza provide for the reports?

Biza provides the remaining metrics as required by the ACCC/OAIC. For further information about the specific requirements in your sector, see here for banking and here for energy.

Can I see a sample report from Biza?

Yes, click here to download it

How do I submit my report?

You can refer to the ACCC Report Submission Guide for instructions.

Data Retention​

What is Biza's data retention policy?

For data sent from a Data Holder to an Accredited Data Recipient (ADR), the Biza HaaS platform is a pass-through service. All data is sent directly to the ADR and is not stored by us.

The CDR does however require CDR-related metadata to be stored for 6 years. Biza stores the metadata for 7 years and this may include active authorisations which can run for up to 1 year.

Support​

What types of customer support are available and how quickly can I expect a response?

You can find our support guidance material here