DSB Maintenance Iteration 22: Meeting Notes (19 February 2025)

Meeting Notes

Current version is 1.33.0, however the decision on Decision Proposal 338 - Updates to Banking Products and Accounts - Binding Standards was made on 18 February and resulting changes will be published in version 1.34.0.
Changes resulting from this MI will be published in version 1.35.0 or later.

Maintenance Iteration 22

#683 - Maintenance Iteration 22 Holistic Feedback

Noted that the issue is available to capture minor corrections and non-breaking changes.
Highlighted the comment regarding the isSecondaryDataHolderError field proposed to be added to the Energy API schema as a non-breaking change.

CX

CX team reiterated that the final feedback and questions period for the draft CX Guidelines wireframes and Change Logs was closing on February 20, 2025.

A question arose about whether Clause 7.2 of Schedule 3 would affect both ADRs and data holders. The DSB clarified that this clause will affect accredited persons who are ADIs, and may affect non-bank lenders once NBL rules take effect.
There was an action item for the community to submit questions they want addressed in these CX Guidelines. The deadline was extended to COB Friday, February 21.

Security

#650 - Weaken JARM Encryption Requirements for ADRs

Issue was discussed.
The DSB has noted that the majority of Data Holders do not advertise support for JARM authorisation encryption.
Where Data Holders advertise support but ADRs choose not to use it, the standards allow the Data Holder to encrypt the response anyway, due to the statement noted in the issue. It is unclear how many Data Holders actually do this.
This issue proposes the removal of the statement that allows Data Holders to encrypt responses where the ADR has not requested it.
ACTION Data Holders to raise any concerns with the removal of the 'MAY' statement.

Register

#679 - Update SSA specification-

Issue was reviewed.
Proposal is for minimal change to allow ADR maintenance.
ACTION Data Holders to raise any concerns with making some SSA fields modifiable to support ADR updates.

Banking

Issue was reviewed.
One participant suggested that an NFR may solve the problem of misaligned balances and transactions.
Other participants commented that a timestamp provides a more functional solution to work with.
It was suggested that effectiveAt may provide a clearer interpretation of when the balance value was accurate.
Participants noted the intent is that posted transactions are available and align to the balance as at the effectiveAt time.
ACTION Participants to provide views on wording that provides the clearest interpretation.

Issue was reviewed.
Proposed retirement date of Get Transaction Detail V1 would align to the obligation date for Decision 338 changes (10 Nov. 2025).

Issue was reviewed.
Proposal is to update guidance to indicate that rate detail must be provided when one or more rates are defined.

Participants noted challenges with identifying transactions made with different cards on an account, in support of business accounting use cases.
ACTION SISS Data Systems to create a more specific CR to be considered as a candidate in this MI.

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

ACTION Frollo to summarise of key aspects from issues #283, #284, #567 and #569 in a new CR to be considered as a candidate in this MI. Further discussion with DSB may be required.
Challenges relate to lending use cases relying on Account data, including:
- Fixed rate end date
- Revert rate
- Interpretation of the application of discount rates
- Other stages that a rate may go through.