When: Weekly every Thursday at 3pm-4:30pm AEDT
Location: Microsoft Teams
Meeting Details: Join on your computer, mobile app or room device Click here to join the meeting
Meeting ID: 446 019 435 001
Passcode: BU6uFg
Download Teams | Join on the web
Join with a video conferencing device
[email protected]
Video Conference ID: 133 133 341 4
Alternate VTC instructions Or call in (audio only)
+61 2 9161 1229,,715805177# Australia, Sydney Phone Conference ID: 715 805 177# Find a local number | Reset PIN
Learn More | Meeting options

---

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

• 5 min will be al lowed for participants to join the call.

We acknowledge the Traditional Custodians of the various lands on which we work today and the Aboriginal and Torres Strait Islander people participating in this call.

We pay our respects to Elders past, present and emerging, and recognise and celebrate the diversity of Aboriginal peoples and their ongoing cultures and connections to the lands and waters of Australia.

The Consumer Data Right Implementation Calls are recorded for note taking purposes. All recordings are kept securely, as are the transcripts which may be made from them. No identifying material shall be provided without the participant's consent. Participants may [email protected] should they have any further questions or wish to have any 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.

⭐ indicates change from last week.

Type	Updated	Links
Standards	Version 1.30.0	Published: 24th of April 2024 Change log
Maintenance	Iteration 19 underway	You can sign up here. Look for the Maintenance Iteration 19 Series.
Maintenance	Iteration 19 Schedule 17/04/2024 Kick-off and backlog review 1/05/2024 Consultation 15/05/2024 Consultation and new issue checkpoint 29/05/2024 Proposal Checkpoint 12/06/2024 Approvals and Documentation	Agendas and Meeting Minutes
DSB Newsletter	To subscribe to DSB Newsletter	Link here
DSB Newsletter ⭐	3rd of May 2024	View in browser here
Consultation	Decision Proposal 229 - CDR Participant Representation	Placeholder: no close date Link to consultation
Consultation	Noting Paper 279 - Accessibility Improvement Plan	No Close Date Link to consultation
Consultation	Noting Paper 323 - NFR Workshops	Link to consultation
Consultation	Noting Paper 330 - UNSW Reports	Link to consultation
Consultation	Decision Proposal 340 - Maintenance Iteration 18	Link to consultation
Consultation	Noting Paper 342 - Information Security Working Group	Link to consultation
Consultation	Noting Paper 345 - Data Standards Body Capability, Consultation Processes and Operating Mode	Link to consultation
Consultation	Noting Paper 346 - Standards Assessment Framework	Feedback closes: 12th June 2024 Link to consultation
Workshop	Standards Assessment Framework Type: Physical Location: Melbourne, Australia Date: 14th May 2024 Time: 1PM - 5PM The workshop will discuss a draft Standards Assessment Framework (Framework) as a mechanism the Data Standards Chair will use to formalise and demonstrate decisions on changes to the Consumer Data Standards. The Framework builds on the DSB's and the Data Standards Chair's existing open and transparent consultation and decision making practices.	Sign up on our event calendar
Workshop	Decision Proposal 338 Workshop Type: Virtual Date: 21st May 2024 2:00PM - 4:00PM Join the Data Standards Body as they work through the prioritisation and planning of Decision Proposal 338. The workshop will be an online sorting exercise on how best to approach the Get Products, Get Product Detail and Get Account Detail endpoint changes.	Sign up on our event calendar
Guidance	Information Map This map is a topic-based listing of Consumer Data Right information published by the Commonwealth Treasury, the Australian Competition and Consumer Commission (ACCC), the Australian Office of the Information Commissioner (OAIC) and the Data Standards Body (part of Treasury).	Check out the Information Map
Engineering	Mock Data Holder (NodeJS) released with a multi-industry support.	v1.0.0

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

Organisation	Stream	Member
ACCC	Register and Accreditation Application Platform, Conformance Test Suite & Participant Tooling	Christian
DSB	Consumer Experience	Bikram
DSB	Standards Assessment Framework	Elizabeth
DSB	Tech Update	Mark

None this week.

Questions on Notice

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
2353	Requesting clarification on BankingScheduledPaymentSetV2 > BankingScheduledPaymentToV2 > Nickname which is listed as conditional. "The short display name of the payee as provided by the customer unless toUType is set to payeeId. Where a customer has not provided a nickname, a display name derived by the bank for payee should be provided that is consistent with existing digital banking channels" 1. Some of our scheduled payments do not have nicknames when the payment is established and don't display a nickname to the customer in existing digital banking channels when viewing the scheduled payment. Is it correct to leave out the nickname in this scenario to be consistent across channels or do we need to derive a nickname based on the To account name? 2. If the toUType is set to payeeId are we able to provide the nickname or is it mandatory to remove the nickname?	1. Just to clarify, the nickname field in BankingScheduledPaymentToV2 is for the Payee of the payment, not for the scheduled payment itself. I'd be interested in knowing how you present the payee detail in other channels - is there just a blank space where the 'Payee' details would normally be shown in these cases where there is no nickname or a 'To account' name? Are you able to share any kind of example for reference? 2. When the toUType is set to payeeId, it means you will provide a payeeId in the relevant field that corresponds to a payeeId available at the Get Payee Detail endpoint (assuming the consumer has given authorised the payees scope), and then the nickname and other detail will be provided by that endpoint, if available. It is not required to exclude the nickname value or field in BankingScheduledPaymentToV2 when the toUType is set to payeeId, but any value provided there may not be used, as it would not normally be expected in that scenario (the ADR would assume it should come from the other endpoint).
2325	Can applicants for Nominated Representatives supply generic email addresses such as [email protected]? Using generic emails is common practice in energy, outside of CDR. We are concerned that Nom Rep applicants ought to supply email addresses for specific individuals aligning to the guidance that Nom Reps must be 'individuals' under the Rules and therefore have unique identifiers.	The CDR Rules and Consumer Data Standards do not explicitly prevent nominated representatives or other consumers from supplying a generic email address. However, we note the use of a generic email as either a contact method or user identifier has the potential to raise security and/or authentication issues. For example, the use of a generic email address as a form of contact may result in other individuals accessing information sent specifically to the nominated representative, such as a one-time password. For more information on nominated representatives, including information about identifiers, please see our Nominated representatives guidance.
2334	if data holder located offshore, with deployment of CDR API gateway at origin location that outside australia? Is there a explicit restriction CDR rules state this scenario?	While we cannot provide compliance advice specific to individual scenarios, we believe this knowledge article is relevant to your query.

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

View a number of informative and useful links in the Consumer Data Standards Guide on Information Links.