Data holders are required to meet IT requirements under Australia’s Consumer Data Right. They also need to follow Consumer Data Standards which include information security controls, consent guidelines and API standards.
Website and app requirements
Consumer Data Right apps or websites must be designed to include the consumer authorisation process.
Data holders must also include an area on their website or app where consumers can clearly see and manage their data authorisations, and include the ability to withdraw authorisations.
Consumers must be able to see:
- details of the Consumer Data Right data they’ve authorised to be shared
- when they gave the authorisation
- the period for which they gave the authorisation
- when the authorisation expires (if the authorisation is current)
- when the authorisation expired (if the authorisation is not current).
The Consumer Data Standards
Consumer Data Right includes data standards for both data holders and accredited data recipients. The Consumer Data Standards are developed by the Data Standards Body.
Contribute to the discussion on standards development on GitHub.
The standards have five main components:
- The CX Standards focus on the consumer experience (CX). These mandatory requirements ensure Consumer Data Right elements are consistent for consumers.
- The CX Guidelines include examples of how to put the Consumer Data Right Rules and CX Standards into effect. These guidelines also include research-driven recommendations to help provide a positive consumer experience.
- The information security profile covers low-level technical details such as encryption algorithms and how tokens are transferred. The tokens dictate how the data is transferred between two entities in a secure way.
- The API standards govern how application programming interfaces (APIs) must be built and cover details such as errors, payload structures and URI taxonomies. These standards apply regardless of sector and enable accredited data recipients to request Consumer Data Right data from data holders across multiple sectors without making any changes to APIs.
- The non-functional requirements include minimum availability, maximum traffic expectations and data quality requirements. These requirements mainly apply to data holders.
Test approach for providers
Each new provider must complete the Conformance Test Suite before they can be made active on the CDR Register. See the ACCC’s Participant Conformance Approach (PCA) which covers providers that are looking to enter the Consumer Data Right system and providers that are already part of the system. The PCA helps all providers prepare for future releases while maintaining the ongoing integrity and operation of the Consumer Data Right system.
As part of the PCA, providers need to test their solution using the Conformance Test Suite. For new providers this is part of the on-boarding process. Find out more about conformance testing for data recipients and data holders in the For providers section.
Test scenarios and mock solutions are also available to assist with testing.
System production incidents
The CDR Service Management Portal is provided by the ACCC for CDR participants to communicate technical incidents between each other, or with the ACCC CDR Technical Operations team. Read the detailed user guide for the CDR Service Management Portal.
If you are a new provider entering the Consumer Data Right System you can apply for access to the CDR Service Management Portal by contacting the CDR Technical Operations team at CDRTechnicalOperations@accc.gov.au.
Find out about what you need to do to comply, including consent and reporting requirements.
Read or download the official Consumer Data Right Rules.