DSB Maintenance Iteration 19: Minutes (15 May 2024)

Meeting Minutes

Release Plan

The current version is v1.30.0. The outcome of Maintenance Iteration 19, if any changes are made, will likely be published in v1.31.0.

Requirements Analysis

Common

• #610 Addition of an (18 or over) Age Verification Flag
  • No update to report, however DSBs team member is working on this with Treasury. An update has been posted on the issue in this comment.

Security

• #628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
  • The DSB has had a number of constructive meetings with ADRs and as a result presented high level findings to DSAC around authorisation drop off last week. There are solutions emerging for the resulting themes.
  • ACTION: DSB to present the findings on #628 in the next Maintenance Iteration meeting.

Banking

• #636 Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction
  • Continued discussion on the merits of this change.
  • Participants requested consideration of the Data Minimisation Principle and purpose based consents, undertaking to post comments on the thread.
  • Eight examples of NPP payment information from different DHs were shared in the chat to further illustrate the problem faced by ADRs in identifying payment information in transactions.
  • ACTION: Josh to post data shared in the chat on the thread for broader visibility.
  • Evidence suggests the information shared via CDR is not consistent with information shared via other channels for the same transactions resulting in Jira tickets requesting DHs to investigate with no resolution.
  • Discrepancies between banks means ADRs are making lots of calls to DHs to get the required information and then writing custom code for each DH to translate information for consistency in presentation to consumers.
  • Once possible cause of the discrepancies worth investigation is payment schemes and extensive use of legacy systems in payment processing.
  • ACTION: Dima to request Australian Payments investigate to provide an opinion.

Maintenance Iteration 19 Candidates

Holistic Changes

• #638 Maintenance Iteration 19 Holistic Feedback
  • No requests for change have been made on this thread.

Candidates

CX

• #633 Collection Consents - Authorisation Amendment
  • Three options proposed on the issue were summarised.
  • An ADR Representative indicated all options were fine and if forced to choose would select Option 2.
  • ACTION: Data Holders are required to indicate a preference for Option 1, 2 or 3 and confirm it is a non-breaking change.

Energy

• #640 Retirement date for Get Generic Plan Detail v2 and Get Energy Account Detail v3
  • 3 months (March 3rd 2025) has been proposed as an appropriate timeframe.
  • Participant agreed that retirement date of 3 months from FDO is preferable.
  • ACTION: Energy retailers requested to comment on the thread to determine appropriate retirement date.

Documentation

• #573 Clarification on handling of standard claims in request object

  • Discussion resulted in general agreement that DHs shouldn't fail a request when unsupported optional claims are included as this aligns with upstream standards.
  • Standards change is not necessary.
  • ACTION: Request for participants to comment on the ticket as to whether more guidance is required or a standards change is necessary.

• #362 Security Profile: Request Object - Inconsistency in example for sharing_duration and cdr_arrangement_id

  • DSB clarified that claims are represented in an claims object within the request object as per normative OIDC standards and the non-normative example is correct.
  • Discussion resulted in a suggestion that this could be dealt via guidance.
  • ACTION: Request for participants to comment on the ticket to clarify requirements.

• #415 Disambiguation of the claims for a response from the introspection endpoint

  • Upstream standards apply, further clarification on the specification could be provided.
  • ACTION: DSB to propose a way to address this issue.

Other business

NONE

Next Steps

The DSB will continue to analyse the issues, including comments, from the community to propose a solution where the requirements have been sufficiently clarified.