Skip to content

DSB Maintenance Iteration 4: Final iteration review: Agenda & Meeting Notes (19th August 2020)

Jump to bottom
CDR API Stream edited this page Aug 20, 2020 · 4 revisions

DSB Maintenance Iteration 4 - Final iteration review - Agenda & Meeting Notes (2020-08-19)

Date and time: 19/08/2020, 2pm - 3pm AEST Location: WebEx

Chair: Mark Verstege, DSB
Maintenance overview: Further information
Maintenance project board: See here

Agenda

Meeting notes

Introductions

  • Allow for participants to join
  • Housekeeping
  • Overview, purpose and intended outcomes of the meeting

Objectives

  • Finalise recommendations for in-scope change requests
  • Discuss implementation impacts and obligation dates

Actions

Release 1.4.0

November obligations

Decision Proposals

Open

Under Review

Iteration Candidates

Iteration Summary

Review of Change Requests

# Change Request Proposed Status Recommendation Obligation dates / Implementation considerations
#42 ANZSIC Code multiple version support Supported: Updated Consultation Proposal; Adopt versioning support for ANZSIC 2006 and ANZSCO 2006 v1.0 - 2013 v1.3 codes Future dated obligation (FDO) necessary - breaking change. Proposed February 2021.
#153 Maturity instructions for a term deposit may not always be known Supported: Updated Consultation Proposal;
Original Change Not Supported
  • maturityInstructions remains mandatory
  • Update the description field
  • Introduce new HOLD enumeration for maturity instructions
 FDO proposed Feb 2021. Should not break existing implementations
#150 A loan may have no end date but loanEndDate is mandatory Carried Over Insufficient feedback N/A
#151 A payee may have no nickname provided by the customer Supported: Updated Consultation Proposal;
Original Change Not Supported 		Nickname remains mandatory and change description to be "determined by the Data Holder in line with existing digital banking channels"
#152 CRN in BankingBillerPayee should be optional Supported: Updated Consultation Proposal;
Original Change Not Supported 		Conditionally mandatory. Introduce enumeration for CRN Type FDO is necessary - breaking change. Proposed February 2021.
#176 Update Query Parameter Transaction Not Supported No consensus N/A
#177 Negative Available Balance in Get Balances response Not Supported Available balance remains zero or greater. N/A
#229 Service field in the Get Transaction Details API Carried Over Insufficient feedback N/A
#271 Update Get Metrics rejections counts and clarify affected APIs Supported Option C - authenticated AND unauthenticated rejection counts. FDO is necessary - breaking change. Proposed Feb 2021.
#240 'SHOULD' for access token revocation Not Supported Access Tokens must be able to be revoked by ADRs N/A
#273 Update claims permitted in Token Introspection Supported with changes Username is excluded FDO is necessary - breaking change. Proposed Feb 2021.
#272 Transition arrangements for November 2020 CDR Consent obligations In Consultation See DP 135 N/A
#266 Decrement BankingProduct Not supported This change to increment BankingProduct was intentional to align with BankingProductDetail N/A
#247 ADR Revocation Endpoint Carried Over For discussion

Notes

Actions

  • WBC to provide analysis on the schema changes for SCT transactions and X2P1.02/03.
  • DSB to follow up with discussion on whether all authenticated/unauthenticated rejection counts are accessible in real-time (e.g. where WAF logs need to be ingested over a period of time)
  • DSB to review proposed obligation dates in conjunction with ACCC phasing obligations for February

Supported change requests

The following change requests have been supported - this may include an updated position

  • #42: ANZSIC Code multiple version support
    • Updated proposal supported to introduce versioning for ANZSIC and ANZSCO codes
  • #153: Maturity instructions for a term deposit may not always be known
    • Maturity instructions will remain mandatory
  • #151: A payee may have no nickname provided by the customer
    • Payee nickname will remain mandatory
  • #152: CRN in BankingBillerPayee should be optional
    • Updated proposal makes CRN conditional based on CRN Type; it would remain mandatory for fixed CRNs
  • #271: Update Get Metrics rejections counts and clarify affected APIs
  • #273: Update claims permitted in Token Introspection

Carried Over

The following change requests have been carried over in the next maintenance iteration over to allow time to consult and review

  • #150: A loan may have no end date but loanEndDate is mandatory
  • #229: Service field in the Get Transaction Details API
    • Further DH analysis to be provided to progress this change request in the next iteration
  • #240: 'SHOULD' for access token revocation
  • #272: Transition arrangements for November 2020 CDR Consent obligations
    • Run through DP 135
  • #247: ADR Revocation Endpoint
    • Noting that further consultation under the CDR Register stream is being consulted

No Change Adopted

  • #177: Negative Available Balance in Get Balances response
  • #176: Update Query Parameter Transaction
  • #266: Decrement BankingProduct

Other business

  • Discussed the cumulative affect of changes with future dated obligations combined with Rules-related obligations required by ADRs and DHs

Next Steps

  • DSB to progress supported changes through the decision process for approval by the Data Standards Chair

Getting Started

Meetings

Maintenance Iterations

CDR Implementation Call

Clone this wiki locally