-
Notifications
You must be signed in to change notification settings - Fork 53
ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 16th of May 2024
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
- 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 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 ⭐ | 10th 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 346 - Standards Assessment Framework |
Feedback closes: 12th June 2024 Link to consultation |
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 | CDR Test Documentation: The latest release v2.4.0 of the relevant Github Repository includes and updated README file and some refactoring to remove outdated/irrelevant components. | - |
Engineering | DSB Postman Collections: The latest release of the relevant Github Repository includes and updated README file. | - |
Video | Maintenance Iteration 19 Candidate Issues - narrated by Neale Morison | DSB YouTube Channel |
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 | Callina |
DSB | Consumer Experience | Bikram |
DSB | Standards Assessment Framework | Elizabeth |
Title: Decision Proposal 338 Workshop board
Presenter: Nils Berge
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 |
---|---|---|
2329 | I would like to have the list of fields included as a part of a CDR receipt for both DH and DR. I want to understand the difference from a consumer perspective of how these varies in DH and DR. Not specifically the CX piece. But to understand which key fields would be appropriate for a CDR receipt from both DH and DR perspective. a. If key fields are same for both DH and DR? b. What are the mandatory and optional fields to be a part of CDR receipt? If I get a list of key fields, this will be helpful going further. We can refer the information for preparation of CDR receipt which will be aligned with the guidelines as well |
Only ADRs are required to provide a CDR Receipt, however we recommend DHs also provide a CDR Receipt. Many DHs are doing this today via email, including major banks. Rule 4.18 outlines the requirements for ADRs providing a CDR Receipt. Rule 4.18(1) sets out when a CDR receipt must be provided, and Rule 4.18(2), (2A), and (3) describe the information required to be included in the notification. This includes the information set out at rule 4.18(3)(a) – (f). Only ADRs are required to provide a CDR Receipt, however we recommend DHs also provide a CDR Receipt. Many DHs are doing this today via email, including major banks. Rule 4.18 outlines the requirements for ADRs providing a CDR Receipt. Rule 4.18(1) sets out when a CDR receipt must be provided, and Rule 4.18(2), (2A), and (3) describe the information required to be included in the notification. This includes the information set out at rule 4.18(3)(a) – (f). The current version of the Rules can be accessed here. |
2341 | This relates to this conversation on the miro board | The cx artefact displays the recommended implementation of the DH dashboard in relation to amendments. It is at the DH’s discretion to: 1 - only include the summary text under the date on the ‘Authorisation history summary’ screen without any ‘amended’ labels on the screens under the ‘Authorisation history details’ tab, 2 - only include the ‘amended’ labels in the screens under the ‘Authorisation history details’ tab without any summary text on the ‘Authorisation history summary’ screen. However, we would encourage DHs to implement both options (i.e. to provide both the summary text and the ‘amended’ labels), as there may be times when it is insufficient to only implement one. DHs are not limited to these two options. However, simply displaying past versions of an authorisation e.g. under the ‘Authorisation history details’ tab without flagging the details of what has been amended would not be compliant. |
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.