ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 29th of August 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 allowed 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.31.0 | Published: 3rd of July 2024 Change log |
| Maintenance | Iteration 20 Commenced 10th of July 2024 |
Sign-up and Register Data Standards Body Events |
| Maintenance | Iteration 20 Schedule: 4/09/2024 Approvals and Documentation |
MI20 Agendas and Minutes |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 23rd of August 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 ⭐ | Decision Proposal 350 - August 2024 Rules - Standards Impacts | Feedback closes: 9th of September 2024 Link to consultation |
| Consultation | Noting Paper 351 - LCCD Risk workshop summary | No feedback sought Link to Noting Paper |
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 |
Title: Decision Proposal 350 August 2024 Rules - Standards Impacts
Presenter: Dr Michael Palmyre
Organisation: Data Standards Body
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 |
|---|---|---|
| 2412 | The accountNumber field in BankingAccountDetailV3 schema is defined as: "The unmasked account number for the account. Should not be supplied if the account number is a PAN requiring PCI compliance. Is expected to be formatted as digits only with leading zeros included and no punctuation or spaces." The schema also defines a separate bsb field. We have recently encountered an issue with one Data Holder that is interpreting the rules as: 1. bsb: sending the BSB number through this field 2. accountNumber: sending the account number prepended with bsb through this field. Please clarify if it is compliant with the standard that Data Holders send the account number prepended with BSB through the accountNumber field? |
The specification clearly requires the two fields to be provided separately and the explanation from the Data Holder doesn't seem to justify non-conformance. |
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.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |