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

---

1. Introductions
2. House Keeping
3. CDR Stream updates
4. General Updates
5. Presentation
6. Q&A
7. Any other business

• 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.

Provides a weekly update on the activities of each CDR stream and their work.

Organisation	Stream	Member
DSB	Energy	Hemang
DSB	Standards	Nils

⭐ indicates change from last week.

Type	Updated	Links
Standards ⭐	CDR Data Standards version 1.35.0 has been published. The release contains changes from: Decision 364 - Maintenance Iteration 22, Decision 367 - incorporating the March 2025 Rules amendment including NBL and BNPL, Decision 369 - Redirect to App, and Decision 370 - amendment of Decision 338 obligation date.	Published: 29 July 2025 Change log
Maintenance ⭐	Maintenance Iteration 24 The next call will be held on 6 August 2025. You can stay up to date on the discussion by checking out the meeting notes in Consultation Draft 373.	Sign up Consultation Draft 373
DSB Newsletter ⭐	The DSB Newsletter is published fortnightly, the next edition will be published on August 8 2025	25 July 2025 Newsletter Subscribe
Guidance ⭐	The ACCC has published its updated Compliance guide for data holders in the banking and non-bank lenders sectors. The compliance guide is designed to assist data holders to understand and comply with their CDR obligations. It was updated to reflect the extension of CDR to the non-bank lenders sector and other changes made by the v8 rules.	Compliance guide for data holders in the banking and non-bank lenders sectors
Guidance ⭐	The ACCC has also published a revised version of the CDR Quick Reference Guide to help CDR participants locate and access the various iterations of the CDR Rules as well as other CDR legislative framework material.	CDR Quick Reference Guide
Decision ⭐	The Chair has approved Decision 364 (Maintenance Iteration 22), which has been posted to GitHub.	Decision 364
Decision ⭐	The Chair has approved Decision 367 (Non Bank Lenders), which has now been posted to GitHub.	Decision 367

Presentation: CDR Journey Mapping Workshop Awareness
Presenter: Sumaya
Download: CDR Journey Map Workshop Awareness.pdf

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.

Ticket #	Question	Answer
2413	X2App Interaction flows Is there a proposed ETA of when would X2App be an accepted interaction flow for a data holder instead of the current OTP-Redirect interaction flow?	Decision #369 includes detail for Redirect to App flows. This decision is now incorporated into version 1.35.0 of the standards.
2486	Transaction security ciphers The transaction security talks about MTLS and Ciphers. Do we have to apply these ciphers for the unauthenticated endpoints products, products details, status and outages?	The Transaction Security section notes Endpoints for transferring CDR Data that are classified as not requiring authentication (i.e. public endpoints) or those specified as TLS, MUST NOT use [MTLS]. The endpoints you noted, all state "This operation does not require authentication." which means they are public endpoints, and therefore TLS only. The Ciphers section applies to both TLS and MTLS, but note that the requirements changed from March 17th 2025.
2511	Deprecation scheduled for Banking Transaction Details V1 API How long must the Banking Transaction Details V1 API be supported by Data Holders?	Decision #364 has now confirmed the date from which Data Holders may retire Get Transaction Detail v1 as November 10, 2025.
2519	Admin APIs - Metadata Update Are Data Holders required to support use of the Metadata Update API? The GitHub issue #53 "Adopt Data Holder metadata update support" remains open for consultation and details that the CDR Register design will not support Data Holder Metadata updates.	The Metadata Update endpoint is currently defined in the Standards, but the ACCC Register has not yet adopted that mechanism for communicating changes with participants.
2528	Handling Multiple constraints of the same type in GET Product Details For Get Product Detail v5, we have identified that some of our products have multiple LVR constraints that are dependent on property type. For BankingProductConstraintV3 is the preferred implementation either: - two separate entries are provided against (for example) constraintType=MAX_LVR, each displaying their own additionalValue with additionalInfo used to contextualise the property type that each applies to, or - a single entry of constraintType=MAX_LVR using the greatest of the two LVR limits as the additionalValue with additionalInfo specifying that there are other additional maximum LVRs based on property type.	New guidance has been published in relation to this query - Multiple LVR constraints not differentiated by rate
2568	Redirect to app - CX Guidelines When will the data holder CX guidelines for ‘redirect to app’ be published?	We aim to publish CX Guidelines within 3 months of rules and standards changes being made. As Decision 369 was made by the Chair on 30 June, you can expect guidance to be published by the end of September. The CX team will be publicly consulting on the draft guidance via Github on Change Request 700. We welcome your participation in this process and feedback on the draft guidance. You can participate either by commenting on the Github thread or by joining the Maintenance Iteration 24 calls.

Attendees are invited to raise topics related to the Consumer Data Right that would benefit from the DSB and ACCCs' consideration.

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	Email
Advisory Committee	CX Guidelines		Calendar
	Support Portal		LinkedIn
			YouTube
			GitHub
			Newsletter