Meeting Minutes

Release Plan

• Candidates for MI18 are progressively being staged and will be published in v1.30.0.

Requirements Analysis

Common

• #610 Addition of an (18 or over) Age Verification Flag
  • No update.

Errors

• #412 Proposal to change specific error codes from MUSTs to SHOULDs
  • May be withdrawn, no progress for ANZ to report.

Security

• #628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
  • Offline discussions with ADRs to gain more insight into the problems have been fruitful. A third meeting will be scheduled in a fortnight. The topics range from types of errors, different scenarios causing drop outs, DH support and consideration of identifiers that might assist in tracking issues. DSB will report on findings when the detail has been finalised.

Maintenance Iteration 18 Candidates

Energy

• #623 Add new pricing models to EnergyPlanContractV2
  • It was clarified that providing an empty array of tariffPeriod is a valid response for plans that do not include them, e.g. plans with only controlled load rates.
  • Based on discussions to date, this change would only require a description update of the pricingModel field for clarification purposes. It is therefore a non-breaking change.
• #624 Improved structure for Solar Time Varying Tariffs
  • Participants noted preference for Option 1 described in this comment.
  • ACTION: DSB to update the ticket with Option 1 as the proposed solution with a recommended FDO noting the time when the changes would likely be made and aligns with other Energy changes.
• #625 Additional field to support Step Tariff calculations
  • DSB noted the change proposed has been summarised for feedback in this comment and requested DEECA/AER to review and confirm it aligns with the requested change.
  • The value of the specific start and end of the rate reset period for a consumer's plan was questioned. An option could be to revisit this at a later stage as a separate Change Request.
  • Participants questioned whether changes like this warrant alignment with the public PRD endpoints and consumer account endpoints which shares common structures. It was discussed that the optionality of the proposed field would allow for the separation of responses if required.
  • ACTION: Feedback from participants on this Change Request, particularly ADRs, is welcome.
• #627 EnergyPlanTariffPeriod - Change to daily supply charge
  • Whilst the original Change Request suggested the banded daily supply charge was isolated to QLD, DSB mentioned a VIC based retailer has raised a similar issue in the CDR Support Portal.
  • Whilst AER has noted they do not support banded daily supply charges, Ergon stated they do supply the data to AER in multiple/duplicate plans. Participants highlighted the potential for this to result in misrepresentation of the information and data quality issues.
  • DSB noted the way retailers provide data to AER/DEECA is outside the scope of CDR.
  • ACTION: DSB to investigate banded daily supply charge concerns with AER/DEECA.

MI 18

• #629 Maintenance Iteration 18 Holistic Feedback
  • No further comments or concerns with the changes in this issue were raised in the call.
  • ACTION: Participants are invited to review the staged changes.

CX

• #557 Withdrawal of a SUI by an Account Holder leaving an "Empty" Authorisation
  • Participant feedback requested increased visibility of changed items in the CX Guidelines change log for future releases.
  • DSB will aim to publish updates to the CX Guidelines to resolve this ticket at the same time the July 2023 rule changes to Dashboards are made.
• #633 Collection Consents - Authorisation Amendment
  • DSB acknowledged participants concern regarding timing for the change, and clarification has been posted in this comment.
  • This issue will be carried into the next Maintenance Iteration.

Security

• #543 refresh_token_expires_at and sharing_expires_at claims listed as MUST be supported
  • Discussed the Decision 209 change was the removal of the CDR custom claims to be standards-aligned.
  • Future need for CDR claims can be considered as part of the FAPI 2.0 migration where such claims might be presented in the RAR authorisation response, or via Grant Management (for example).
  • One large bank confirmed that any load impacts to the introspection endpoint are minimal and already being dealt with - they did not see an increased load on their systems.
  • Also discussed that ADRs cannot currently rely on the custom claims, and instead introspect the refresh token to get the 'exp' time for sharing duration.
  • Agreement on the call that this change be accepted.
  • ACTION: Participants requested to review proposed solution and comment on the issue.
• #631 Updates to 'Revoking consent' Standards
  • Proposed solution accepted.
• #632 Concurrent consent support and cdr_arrangement_id
  • Proposed solution accepted.

Admin

• #626 AuthorisationMetricsV2 abandonmentsByStage property descriptions and CDS Guide
  • Discussion from the call has been captured in a comment on the issue.
  • ACTION: DSB to consider feedback on interpretation of steps in the process to better distinguish between Rejection and Abandonment.
  • ACTION: DSB to review CX Guideline wire frames to determine alignment with OAuth errors.

Other business

None

Next Steps

DSB will finalise proposed solutions for each issue and continue to stage the changes for v1.30.0. Community review and comment on each of the issues is essential to ensure DSB's proposed solutions align with your understanding of the requirements and discussion outcomes.