DSB Maintenance Iteration 23: Meeting Notes (25 June 2025) - ConsumerDataStandardsAustralia/standards GitHub Wiki

Meeting Notes

  • Meeting 5 of MI23 focused on finalising proposed solutions for the candidates that can be resolved. Candidates that cannot be resolved will be carried into MI24.

Requirements Analysis

Energy

Banking

  • TBA - Potential new issue relating to banking issues included, but deferred in Decision 338

    • ACTION: DSB to review issues #283, #284, #567 and #569 to determine the best way to proceed.

  • 692 - ISO 8601 - Home Loan Repayments

    • This issue has been moved to the Support Portal to discuss the requirements in more detail and will be moved to the backlog on conclusion of MI23.

  • 697 - Commercial Credit Card Structure under Get Account Details

    • NAB advises a fix to stop errors occurring will go live at the end of the month or shortly thereafter.
    • The problem has been put on the rectification schedule until the fix occurs.
    • The CR will remain open for further discussion.
      • ACTION: NAB to post details of the fix on the issue.
      • ACTION: DSB to assess next steps once NAB has posted.

MI23 Candidates

MI23

CX

Register

  • 679 - Update SSA specification

    • No feedback from DHs on the impact of this change has been received.
    • A proposal to rely on a configuration endpoint advertising SSA versions offered by DHs doesn't appear to be supported as a change at this time.
    • Additional changes proposed on the issue were intended to provide a better foundation for future DCR changes.
    • Intention of the original request was to streamline the standards. ACCC observes that most DHs do allow changes, so any impact is anticipated to be minor.
    • The proposed solution is limited to allowing fields to be modified and will be finalised in this MI.

  • 665 - Review Register error code documentation

    • ACCC reviewed current implementation of register APIs and the Future Improvements sections of the standards and suggested a set of changes for 400 errors.
    • ACCC is reviewing the impact and will post details on the issue
    • These changes are likely to be introduced along with other register changes required to accommodate Non-Bank Lending
      • ACTION: ACCC to post detail of changes to error messages on the issue.
    • This issue will be carried to the next MI.

  • 695 - Digicert Certificate Trust Chain Migration

    • ACCC has posted an update on the issue to confirm the date is fixed as notified in the last meeting, see comment.
    • Communications from ACCC have been sent which explain how transition to the new certificate will work.
    • Further communication is targeted for 1 August to provide new certificates.
    • ACCC is considering where to house operational information which will inform an update to content in the Certificate Management section of the standards.
      • ACTION: ACCC to advise outcome of Certificate Management section review.
    • This issue is anticipated to be resolved in this MI.

Energy

Banking

  • 687 - Bank account balance calculation time is indeterminate

    • This issue has been moved to Requirements Analysis for MI24 while we wait for the outcome on Issue 656 in the MI22 Consultation Draft.
    • Analysis will continue on how a timestamp field might be used if needed.

  • 688 - BankingBalancePurse currency field is optional

    • The general assumption is that every DH is providing the currency value because the data doesn't make sense without it.
    • Discussion on differentiating between breaking change in source of data and behaviour of API. Providing data already in the schema may be a breaking change in the backend, but not in the API interface.
    • DSB is anticipating this is a non-breaking change as a value is already expected.
    • The proposed solution will be adopted to resolve the issue as a non-breaking change in this MI.

  • 694 - Add a Card identifier to the Transaction endpoint

    • A proposal has been made to resolve this issue, described in this comment.
    • Further discussion on the description of the new field is required.
    • Priority for this change is corporate credit cards as opposed to retail accounts.
    • The proposed solution will be adopted to resolve the issue as a breaking change in this MI.

  • 173 - Behaviour where posted transactions only have an associated date

    • Two parts to this change, DSB is proposing to proceed with the guidance draft in this MI.
    • One participant voiced support for guidance to proceed.
    • Guidance changes will not have any impact on the standards, however it may have an impact on DH implementations.

Documentation

  • 668 - Review References detail
    • Specific impacts on each change have been bolded to provide further clarity.
    • DSB is proposing to proceed with the clean up on these links to resolve the issue as a non-breaking change in this MI.

NFR

  • 660 - Revise the Availability Requirements NFRs
    • Two changes proposed
      • Part A Update non functional availability requirements; they MUST be commensurate to the day, length and frequency of other digital channels.
      • Part B Outage notifications extended to provide additional technical information to help ADRs understand the need for the outage.
    • Important to note both Parts A and B will be proposed in the consultation draft.
    • Discussion on use cases affected by outages, described in this comment.
    • Related issues, that are not addressed in the proposed solution, but should be considered in future discussions around the accurate reporting of partial outages.
    • Expectation is status endpoint should provide real time status. Services coming online earlier than planned is as equally important as delays in services coming online following a planned outage. It was noted that a planned outage can become an unplanned outage and should be reflected in the status endpoint.
    • There is an expectation that outages are as minor as possible, and further discussion on a preference for partial outages. Options to provide notifications at product or customer level were discussed but not supported by DHs or ADRs.
    • The proposed solution will be adopted to resolve the issue as a breaking change in this MI.

Any other business

Maintenance Iteration 24 MI24 will kick off on 9 July. The Consultation Draft issue will be created on the standards repository in the coming days, inviting participants to propose candidates for consideration.