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 20 Kick-off is 10th of July 2024	Sign-up and Register Data Standards Body Events
Maintenance ⭐	Iteration 20 Schedule: 10/07/2024 Kick-off and backlog review 24/07/2024 Consultation 7/08/2024 Consultation and new issue checkpoint 21/08/2024 Proposal Checkpoint 4/09/2024 Approvals and Documentation	Agenda page to come
DSB Newsletter	To subscribe to DSB Newsletter	Link here
DSB Newsletter ⭐	21st of June 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 347 - Maintenance Iteration 19	Link to consultation
Consultation	Noting Paper 348 - Use Case Enablement Experiment: Account Origination	Open for comment: 12th July 2024 Link to Noting Paper
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

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
2375	Rate Field -Get Account Detail Endpoint-Clarification This is regarding the "Rate" field present in Get Account Detail API endpoint. As per requirement, it is mentioned that the format expected in “Rate” is RateString -> A string representing a percentage (e.g. an interest rate). A rate of 100% would be represented by the value 1.0 and a rate of -100% by -1.0 - At least 1 and up to a total of 16 significant digits before decimal point - Up to 16 digits following the decimal point - No formatting, eg thousand separating commas Considering above premise, is 0 acceptable value or it has to be 0.00?	"0" (as a string) is acceptable as it is equivalent to "0.0", "0.00" and "0.000000". We will review the description and examples associated with that type to clarify. See Issue 410
2383	We are wondering what the correct error code and message would be to return for any endpoint, if the request is made without an x-v value. It seems as if it should be Missing Header, since x-v is a required header, but Missing Header isn't listed as a possible error code for any endpoint. Instead, we thought to use Invalid Version. What would be the correct approach?	We have this guidance available: https://cdr-support.zendesk.com/hc/en-au/articles/5729181240591-Error-scenarios-and-responses#Missing_required_header:_400 on error codes. This includes the reference to the Standards: https://consumerdatastandardsaustralia.github.io/standards/#error-400-header-missing

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.