Meeting Minutes

Release Plan

The current version is v1.30.0. The outcome of Maintenance Iteration 19 will likely be published in v1.31.0.

Requirements Analysis

Common

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

Security

• #628 Addition of a DH-side endpoint for querying the status of a consent establishment flow
  • Met with ADRs today, close to forming key issues from an ADR perspective and we're keen to share back in the MI call.

Maintenance Iteration 19 Candidates

Holistic Changes

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

CX

• #633 Collection Consents - Authorisation Amendment
  • Considering feedback on the ticket and working with other CDR agencies to work out an optimal way to provide clarification. Anticipate having more to update you on in the next meeting.

Register

• #561 Update Register API to return separate PRD and status/outage endpoint
  • The DSB has flagged in the past the need to consult on enhancements to the Register. Rather than making this change in isolation it will be looked at from a holistic view of the Register and consulted on as a package of changes.
  • Moved to backlog.

Banking

• #636 Remove BankingTransactionDetail and incorporate extendedData into BankingTransaction
  • This change is potentially related to NFRs and DP338.
  • Intention of removing an endpoint is to reduce traffic although unaware of complexity in combining these calls to retrieve all of the necessary information in a single call rather than making additional calls. There is increasing consumer demand for transaction detail.
  • Payer and Payee details are highly desirable and a DH indicated investigation had been undertaken.
  • Consensus that BankingTransactionDetail is likely to be needed due to payment overlays and future requirements.
  • ADRs raised concerns with the quality of information provided in transaction detail and a mismatch with other digital channels and this triggering the need for custom development to generate a suitable description.
  • DHs requested ADRs specify which fields they were interested in to enable DHs to investigate further.
  • Suggestion an online workshop might be suitable to surface relevant issues.
  • ACTION: ADRs to comment on the ticket with details of fields they'd like considered for inclusion in BankingTransaction.
  • The complexity of this issue is unlikely to be resolved in this MI, it will continue to be discussed under Requirements Analysis.

Energy

• #640 Retirement date for Get Generic Plan Detail v2 and Get Energy Account Detail v3
  • API versions were incremented in the last MI where the deprecation or retirement date was set for 12 months from the date the new version comes into effect.
  • Best practice is to set the retirement date three months after the obligation date.
  • ACTION: Energy retailers to consider implications and provide comment on the issue.

Documentation

• #615 Plan Obligation Milestones for 2025

  • Obligation dates are only planned until the end of 2024, ideally we'd like to extend out to 2025.
  • These dates are intended to apply across the Rules and Standards.
  • Finalising these dates may also be influenced by the outcomes of the Standards Assessment Framework Workshops.

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

  • Fix required to align with normative standards.
  • ACTION: DSB to clarify whether a documentation fix would align with normative standards.

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

  • Consider guidance instead of making a standards change.
  • ACTION: DSB to analyse further to make a recommendation.

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

  • Statements may be misaligned.
  • ACTION: DSB to investigate and advise.

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.