ACCC & DSB | CDR Implementation Call Agenda & Meeting Notes | 13th of July 2023
When: Weekly every Thursday at 3pm-4:30pm AEST
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.
| Type | Topic | Update |
|---|---|---|
| Standards | Version 1.25.0 | The latest version 1.25.0 was Published on 8 July 2023, it incorporates Decision Proposal 303 Maintenance Iteration 15 and Decision Proposal 288 Non Functional Requirements Revision |
| Maintenance | Iteration 16 kicked off yesterday, 12 July 2023 | Email [email protected] to request an invitation |
| TSY Newsletter | To subscribe to TSY Newsletter | Link here |
| DSB Newsletter | To subscribe to DSB Newsletter | Link here |
| TSY Newsletter | 27th of June 2023 | View in browser here |
| DSB Newsletter | 7th of July 2023 | View in browser here |
| Consultation | Decision Proposal 229 - CDR Participant Representation | Placeholder: no close date Link to consultation |
| Consultation | Noting Paper 276 - Proposed v5 Rules & Standards Impacts | No Close Date Link to consultation |
| Consultation | Noting Paper 279 - Accessibility Improvement Plan | No Close Date Link to consultation |
| Consultation | Noting Paper 280: The CX of Authentication Uplift The CX Team will present on latest outcomes in today's session |
No Close Date Link to consultation |
| Consultation | Decision Proposal 306 - Updates to Banking Product and Account Detail | Feedback closes: 28th of July 2023 Link to consultation |
| Consultation | Noting Paper 307 - LCCD Consultation Approach | No Close Date Link to consultation Video |
| Consultation | Noting Paper 308 - Categories of Standards | No Close Date Link to consultation |
| Obligation Date: Authorisation Code Flow (ACF) |
10th of July 2023 obligation date has passed FAPI 1.0 adoption is introduced across four phases. Phase 4: Retire Hybrid Flow: Data Holders MAY retire Hybrid Flow |
The ACCC is reaching out to participants to gather information regarding the transition from Hybrid to ACF. If any data recipients have feedback they wish to provide regarding their overall experience of ACF, please get in contact with the ACCC at [email protected]. We also encourage recipients to continue raising individual issues with the relevant data holders for resolution. |
Provides a weekly update on the activities of each CDR stream and their work.
| Organisation | Stream | Member |
|---|---|---|
| ACCC | Register and Accreditation Application Platform (RAAP) | Eva |
| ACCC | Conformance Test Suite (CTS) | Seamus |
| DSB | Consumer Experience | Michael |
| DSB | Technical Standards - Energy | Hemang |
| DSB | Technical Standards - Information Security & Banking | Mark |
| DSB | Technical Standards - Maintenance Iteration 16 | Nils & Hemang |
| DSB | Technical Standards - Register | James |
This week there are two presentations:
Presenter: Lawrence Berry-Noronha, Business Operations ACCC
Link to Performance Dashboard https://www.cdr.gov.au/performance
This presentation will inform participants of upcoming changes in the next version of the Performance Dashboard.
Presenters: Holly McKee and Bikram Khadka, CX Designers DSB
Link to Noting Paper on GitHub
This presentation will provide a brief overview of:
- Consumer Experience of Authentication research to date
- Approach to CDR Authentication Uplift
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 |
|---|---|---|
| 2014 | Is a white labelled company required to have their own CDR policy? | A "CDR entity" within the meaning of section 56ED of the Competition and Consumer Act 2010 (Cth), is required to have and maintain a clearly expressed and up-to-date CDR policy, regardless of whether it has entered into a white label arrangement. CDR entities generally include data holders or accredited persons. For guidance on CDR policies, please see the OAIC’s Guide to developing a CDR policy. |
| 1560 | Will both the Elec AND Gas details of the customer be accessible via the Billing/Service Point/Account Detail/Billing for a Specific Account? | Gas data is shared if it is part of a bundled/duel fuel plan with energy. This is based on the designation instrument for the energy sector. |
| 1531 | When a consumer moves out of a property and another moves in, does the servicePointId change? | The servicePointId changes if the consumer changes. The CDR field servicePointId is not an NMI. A servicePointId is unique to an NMI and an ADR for a given consumer consent. |
| 1966 | Does the 'accountCharges' object hold charges/discounts/gst for ancilliary items that don't fit into energy usage, or is it a roll-up of all charges/discounts/gst for the invoice | The object accountCharges captures any charges applied an account level (for e.g. account setup charges). It's not a roll-up of all other charges for the invoice. |
| 1914 | Please clarify what is meant by "commensurate" data latency. | The meaning of this term is up to the regulator. However the DSB can say that the requirement for commensurate data latency was to avoid differences between a CDR channel and a proprietary channel. If the CDR channel is noticeably slower consumer confidence is undermined. |
| 1989 | In authorisation code flow (ACF), are these fields mandatory: registration authorization_encrypted_response_alg and authorization_encrypted_response_enc ? | The field authorization_encrypted_response_alg is Conditional, not mandatory. The field authorization_encrypted_response_enc is Optional, contingent on the ADR registration request. |
| 1976 | If the ADR has only one software product, can they register using both hybrid and ACF flows with the same Data Holder? During a DCR (client registration or Update Registration) can an ADR send both values ("code id_token" and "code") in the same request for a Software product in the field "response_types"? | Client Registration is on a software product by software product basis. An ADR software product is registered with a Data Holder to obtain an oAuth client ID. A separate OAuth client ID is registered for each individual Software Product. An ADR can register for both Hybrid and ACF flows for the same oAuth client. Yes, in a DCR an ADR can send "code id_token" and "code" in the same request. |
| 1825 | The Get Scheduled Payment schema has a field 'nickname' under the 'BankingScheduledPaymentTo' object. Do we need to supply this field if the toUType is payeeId? | The nickname is not required if the toUType is set to payeeId. This is because the payee nickname (and other details) can be retrieved from the Get Payee Detail endpoint by using the payeeId provided in BankingScheduledPaymentTo. |
| 1820 | Under what circumstances is an outage considered planned, and therefore not classified as an unavailable period? | All planned outages, other than for critical fixes, are expected to be published with at least one week lead time. All other outages are classified as unavailable periods. |
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.
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
 |