Data holders must meet IT requirements under Consumer Data Right. They also need to follow data standards, which include information security controls, consent guidelines and API standards, as well as the Consumer Data Right Register design, which defines client registration requirements.

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 data standards

Consumer Data Right includes data standards for data holders and accredited data recipients. The standards are developed by the Data Standards Body.

Contribute to the discussion on standards development on GitHub.

The standards have five main components:

  1. The CX Standards focus on the consumer experience (CX). These mandatory requirements ensure Consumer Data Right elements are consistent for consumers.
  2. 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.
  3. 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. 
  4. 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. 
  5. The non-functional requirements include minimum availability, maximum traffic expectations and data quality requirements. These requirements mainly apply to data holders

System test requirements for current providers

You must test your IT systems to ensure they are working correctly in compliance with Consumer Data Right rules and standards in preparation for data sharing. See the ACCC’s testing approach for the November 2020 phase release for details, including the test stages, test scenarios and timing of industry testing.

System test requirements for new providers

If you are a provider that is new to Consumer Data Right, you are required to go through on-boarding. On-boarding helps prepare providers to actively participate in the Consumer Data Right system.

Once you are successfully accredited (as a data recipient) or registered (as a data holder), you must on-board into the Consumer Data Right system, including successfully passing the Consumer Data Right Conformance Test Suite. You will then receive an active status on the Consumer Data Right Register after all on-boarding requirements are fulfilled.

This is the last step you must go through as a new provider before you can start sharing consumer data in the Consumer Data Right system.

More information about on-boarding can be found in the on-boarding frequently asked questions (FAQs). The Consumer Data Right On-boarding Guide, due to be published in October 2020, includes more detailed information on the end-to-end on-boarding process steps, legal requirements, technical requirements and expectations of providers.

Consumer Data Right Register requirements

Data holders must meet certain client registration requirements relating to the Register, which is designed and managed by the Australian Competition and Consumer Commission. 

The Register is also known as the Register of Accredited Persons. 

Contribute to the discussion on the Register design on GitHub.

Related links