ACCC & DSB | CDR Implementation Call Agenda & Minutes | 9 October 2025 - ConsumerDataStandardsAustralia/standards GitHub Wiki
Sign up: Sign Up
When: Fortnightly on Thursday's at 3pm-4:30pm (Canberra time)
Location: Microsoft Teams (dial in details are below)
Join on your computer, mobile app or room device
Click here to join the meeting
Meeting ID: 426 030 545 881 4
Passcode: 5d7Kp73X
Download Teams | Join on the web
Dial in by phone
+61 2 9161 1229,,538826932# Australia, Sydney
Find a local number
Phone conference ID: 538 826 932#
Join on a video conferencing device
Tenant key: [email protected]
Video ID: 135 792 992 7
- 5 min will be allowed for participants to join the call.
- This call is jointly facilitated by the ACCC and the DSB, and we welcome observers from APRA, OAIC and the Treasury.
We acknowledge the Traditional Custodians of the various lands on which we meet today and pay our respects to their Elders past and present.
The Consumer Data Right Implementation Calls are recorded for note taking purposes only. Recordings and transcripts are kept securely. No identifying material is provided without the participant's consent. Participants may email [email protected] with any questions or a request to have material redacted from the record.
By participating in the Consumer Data Right Implementation Call you agree to the Community Guidelines. These guidelines intend to provide a safe and constructive space for members to discuss implementation topics with other participants and members of the ACCC and Data Standards Body.
| Calendar Invite |
|---|
| We are aware that the Implementation Call calendar invite is showing the incorrect time inside people's calendars. This occurred since the switch to daylight savings, so this has been investigated by our software provider Trumba. Sorry for the confusion that it might have caused. Please continue to join at 3:00 PM AEDT for future calls. |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member | Minutes |
|---|---|---|---|
| DSB | Maintenance Iterations | Agi | We had put maintenance iteration calls on hold recently while we undertake a review, this review is still ongoing but to provide an update on where this is heading: Given the CDR program’s operational position and participant feedback, the Chair has been directed to rethink the approach to the scheduling, frequency and volume of change releases along with the rationale for making changes. As a result, we are currently reviewing the MI23 and MI24 scope to analyse the impact and then prioritise critical changes. Public consultation is potentially in November for MI23 and February for MI24. Long term, our approach to future MI's will change to conform to this new direction. We will continue to provide updates on this as we progress through the analysis. |
⭐ indicates change from last week.
| Type | Updated | Links |
|---|---|---|
| Standards ⭐ | CDR Data Standards v1.35.1 has been published 8 October 2025. The release contains changes from Decision 377 (Amendments to certificate management section). | Published: 8 October 2025 Change log |
| Standards ⭐ |
Decision Made Decision 377 was made by the Data Standards Chair on 7 October 2025. The decision makes a minor amendment to the standards in relation to a transfer of operational detail to the ACCC. As a minor amendment to the standards, this decision is being made without further consultation. Consultation on the issue was originally conducted through Maintenance issue #695. |
|
| Consultation ⭐ |
Consultation Draft 376 - White label brand arrangements - Draft Standards Feedback is open for Consultation Draft 376. This consultation proposes draft standards to accommodate data holders with white label brand arrangements as they relate to the consumer data provider list and product reference data. The accompanying Explanatory Document provides the background and context for these draft standards, and an assessment of potential impacts. You can submit responses to this consultation up until the close of Friday, 31 October 2025. Feedback may be provided on #376. You may also provide feedback in writing directed to [email protected]. |
|
| Guidance ⭐ |
CX Guidelines update - General maintenance As part of general maintenance, the following website pages and CX artefacts have been updated:
|
|
| DSB Newsletter ⭐ | The DSB Newsletter is published fortnightly, the next edition will be published on October 17 2025 |
None this week.
Questions will be received by the community via Microsoft Teams chat before the questions are opened to the floor. Participants can submit questions outside of the CDR Implementation Call to the CDR Support Portal.
In regards to topics for questions, we ask the participants on the call to consider the Community Guidelines when posing questions to the subject matter experts.
To view questions and answers from previous CDR Implementation Calls, click here.
| Ticket # | Question | Answer |
|---|---|---|
| 2585 |
Redirect to app clarification on CX requirements In the existing CX standards for authentication, we need to provide a link to CDR policy. Hence, wanted to check if the CDR policy need to be provided during ‘redirect-to-app’ and if there is a CX recommendation on the screens that should have this link. |
CDR Rule 7.2(8) (aka CX Checklist ref 2AU.00.01/annotation #1 on the Redirect to Web with One Time Password) is accompanied by the a CX Guideline 2AU.00.17 (or annotation #17 which states that:Data holders should consider including their CDR policy in the authentication process as this will likely be the first online service the CDR consumer uses to interact with their data holder for the purposes of CDR.Therefore, including the CDR policy during the authentication process is recommended but not mandatory. This inclusion may be more beneficial during a Redirect to Web with One Time Password authentication process, as consumers may spend more time interacting with these screens compared to when using a Redirect to App method. CDR Rule 7.2(8) can be satisfied if it’s readily available through each online service by means of which the CDR entity (or rep) ordinarily deals with the CDR consumer. CX Guideline 3AU.02.20/annotation #20 in Authorise to Disclose also recommends including the CDR policy in the Authorisation flow. |
| Verbal question 1 |
Deregister a brand for product data When someone tries to list products from the product API endpoint for a brand that does not have any products on the endpoint (as they are listed under the parent's brand product API rather than listing the products twice), they just get a 200 OK (request succeeded) and an empty array. Would it be possible to deregister that brand for product data. |
There is some detail related to that situation in Consultation Draft 376 about white labelling. It would address the ability to switch off PID sharing where it's not applicable. |
Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.
Minutes from 25 September Implementation Call: https://github.com/ConsumerDataStandardsAustralia/standards/wiki/ACCC-&-DSB-%7C-CDR-Implementation-Call-Agenda-&-Minutes-%7C-25-September-2025
Thursday, 3:00pm (Canberra Time)
View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.
| Data Standards Body | Consumer Data Right | Digital ID | Contact & Media |
| Chair | Standards | Accreditation Standards | Website |
| News | Maintenance Iteration | AGDIS Standards | |
| Advisory Committee | CX Guidelines | Calendar | |
| Support Portal | |||
| YouTube | |||
| GitHub | |||
| Newsletter |