ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 1st of February 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 | Topic | Update |
|---|---|---|
| Standards | Version 1.29.0 | Published: 21st December 2023 Change log |
| Maintenance | Maintenance Iteration 18 commences 7th February 2024 | Invitations issued Please reach out to [email protected] for an invitation |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| DSB Newsletter ⭐ | 26th of January 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 |
| Engineering ⭐ | JS Holder SDK (Demo): has been updated to align to CDS version (1.28.0) | Github repository. |
| Guidance ⭐ | Update to the CDR Register Metrics Collection article. In response to a query on the data latency with CDR Register Metrics, the article has been refreshed and updated. | Link to the CDR Support Portal |
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 | Michael |
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.
| Ticket # | Question | Answer |
|---|---|---|
| 2244 | Due to some limitation of the data availability in our core banking system, the "paymentDueAmount" field for Credit card is currently not available. Previously, we defaulted this field to "0.00" however an incident was raised against us via the ACCC Jira portal by an ADR. We have raised this gap with the business owner to find a way to get this data from our card management system provider, however, it will take some time as we are going through some transitions. In the interim, can you please advise what will be the best defaulted option for this field. Should we continue using 0.00 or if we can use empty string. All the other fields in the BankingCreditCardAccount structure are the real data. We receive the data for other fields from the card management system to our core banking system except the paymentDueAmount. |
An empty string would not be valid for the AmountString format, and "0.00" should not be disclosed if it is inaccurate. The correct approach for a response with the paymentDueAmount value missing, would be to exclude the whole creditCard object (and the optional 'specificAccountUType' referring to it), as it would be schema-non-compliant if it didn't contain all the mandatory fields. |
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.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
 |