DocumentVersionDate releasedChange log
Consumer Experience Standards1.
Consumer Experience Guidelines1.
Consumer Experience Standards1.
Consumer Experience Guidelines1.
Consumer Experience Guidelines0.9.517.07.2019

The Data Standards Body (DSB) recognises that consumer adoption is critical to success for the CDR regime. This is particularly true in the early stages of implementation when consumers will not be familiar with the mechanisms and protocols required to engage with CDR participants and consent to share their CDR data.

To facilitate CDR adoption the DSB has developed Consumer Experience (CX) Guidelines and identified a number of key elements to be aligned to across the regime.

CDR Rules (8.11) also require data standards to be made for:

  • obtaining authorisations and consents, and withdrawal of authorisations and consents;
  • the collection and use of CDR data, including requirements to be met by CDR participants in relation to seeking consent from CDR consumers;
  • authentication of CDR consumers
  • the types of CDR data and descriptions of those types to be used by CDR participants in making and responding to requests

As stated in the CDR Rules Explanatory Statement, ‘at a minimum, accredited persons will be guided by the language and processes of guidelines produced by the DSB.’ The CX Workstream emphasises that aligning to the non-mandatory items in the CX Guidelines will help achieve consistency, familiarity and, in turn, facilitate consumer trust and adoption.

The CX Guidelines avoid being prescriptive to balance ecosystem consistency with the potential to innovate. The complete list of binding Consumer Experience Standards outlined in this section were created to balance these objectives.

CX standards will be binding data standards for the purposes of s56FA and in accordance with the Consumer Data Right rules made by the ACCC. The making and commencement of the data standards and the CDR rules is subject to the Consumer Data Right legislation.

Leave a Reply

Your email address will not be published. Required fields are marked *