V1.25.0 Release Notes

Release notes for version v1.25.0 of the CDR Standards.

Changes Made

Change Requests

This release addresses the following minor defects raised on Standards Staging:

• None

This release addresses the following change requests raised on Standards Maintenance:

• Standards Maintenance Issue 516 - Get OpenId Provider Config and Get JWKS API documented paths are incorrect
• Standards Maintenance Issue 522 - OpenID Provider Configuration End Point parameter requirements
• Standards Maintenance Issue 536 - Define new toUType value to relevant schemas
• Standards Maintenance Issue 559 - FAPI 1.0 Final Phase 3 Obligation example for authorisation request using the Authorisation Code Flow does not have "response_mode" attribute
• Standards Maintenance Issue 586 - Maintenance Iteration 15 Holistic Feedback
• Standards Maintenance Issue 590 - Remove FAPI 1.0 draft references
• Standards Maintenance Issue 591 - Energy 'Get Agreed Payment Schedule' - BSB and Account Number Tokenisation/non-Tokenisation
• Standards Maintenance Issue 592 - EnergyBillingDemandTransaction - timeOfUseType - New Value

Decision Proposals

This release addresses the following Decision Proposals published on Standards:

• Decision Proposal 288 - Non-Functional Requirements Revision
• Decision Proposal 303 - Maintenance Iteration 15

Introduction

Change	Description	Link
Removed legacy obligation dates	Standards Maintenance #586: Removed legacy obligation dates more than 6 months in the past. Addresses this issue comment)	Future Dated Obligations
Added Data Holder Brands Summary API to endpoint schedule	Standards Maintenance #586: Included the Get Data Holder Brands Summary API into the endpoint version schedule. Addresses this issue comment	Endpoint Version Schedule
Typo correction in the endpoint schedule	Standards Maintenance #586: Corrected typos in the endpoint version schedule. Addresses this issue comment	Endpoint Version Schedule
Heading changes	Standards Maintenance #586: Renamed InfoSec Profile to Security Profile and CDR Register APIs to Register APIs in the endpoint version schedule. Addresses this issue comment	Endpoint Version Schedule
Spelling mistake	Standards Maintenance #586: Fixed misspelling of "Register". Addresses this issue comment	Future Dated Obligations

High Level Standards

No Change

API End Points

Change	Description	Link
Add digitalWallet to Scheduled Payments	Standards Maintenance #536: Added digitalWallet object to BankingScheduledPaymentToV2 structure. Incremented versions of Get Scheduled Payments For Account, Get Scheduled Payments Bulk and Get Scheduled Payments For Specific Accounts APIs. Updated description of name field in the EnergyPaymentSchedule.digitalWallet and TelcoPaymentScheduleDigitalWallet structures for consistency	Banking APIs Energy APIs Telco APIs
Corrected HTTP Methods	Standards Maintenance #586: Corrected the endpoint version schedule to correctly list POST not GET methods for energy APIs: Get Usage For Specific Service Points Get Balances For Specific Energy Accounts Addresses this issue comment)	Endpoint Version Schedule
Get Products	Standards Maintenance #586: Corrected typo in the Get Products API description. Addresses this issue comment)	Get Products API
Energy APIs	Standards Maintenance #591: Updated description of EnergyPaymentSchedule.isTokenised field to further clarify when it can be used	Energy APIs
Energy APIs	Standards Maintenance #592: Added ALL_DAY and EXCESS values to EnergyBillingDemandTransaction.timeOfUseType field. Added ALL_DAY value to EnergyBillingUsageTransaction.timeOfUseType field. Incremented versions of Get Get Billing For Account, Get Bulk Billing and Get Billing For Specific Accounts APIs.	Energy APIs
Get Metrics	Added v4 and v5 of the Get Metrics API	Admin APIs

Information Security Profile

Change	Description	Link
OpenID Provider Configuration End Point	Standards Maintenance #522: Provides an exhaustive list of the required OpenID discovery parameters Data Holders must publish.	OpenID Provider Configuration End Point
Authorization Code Flow non-normative example	Standards Maintenance #559: Added "response_mode" to the authorisation request examples in accordance with FAPI 1.0 requirements for Authorisation Code Flow and JARM use.	Security Profile
FAPI normative references	Standards Maintenance #590: Removed legacy draft FAPI references and legacy phasing ensuring all normative references for FAPI align to the final versions	Security Profile

Register Standards

Change	Description	Link
Register Base Paths	Standards Maintenance #516: Match the endpoints paths for jwks and well known to match actual Register implementation.	Register APIs

Consumer Experience

No Change

Non Functional Requirements

Change	Description	Link
Site Wide TPS Tiers	Added authorisation based tiering for site wide TPS thresholds	Traffic Thresholds
Low Velocity Data Sets	Added NFRs applicable to data recipients to accommodate low velocity data sets	Data Recipient Requirements

Known Issues

No Change