Future Dated Obligations (FDOs) by topic

Introduction

CDS v1.23.0

This table is taken from the CDS Future Dated Obligations (FDOs) section. The content is arranged here in topic order. FDOs for past dates are shown with a grey background.

APIs

For endpoint obligation dates, listed by topic, see the CDS Endpoint Version Schedule. This covers not only Future Dated Obligations for all APIs, but also other dates including retirement date and date deprecated.

Error Codes

Section	Description	Applicable Date
Standard Error Codes	Data Recipients and Data Holders MAY implement the standard error codes from July 1st 2021	July 1st 2021
Standard Error Codes	Data Recipients and Data Holders MUST implement the standard error codes from February 1st 2022	February 1st 2022
Standard Error Codes	Data Holders MAY retire application-specific error codes in favour of standard error codes from November 1st 2022	November 1st 2022
Standard Error Codes	Data Holders MAY implement the isSecondaryDataHolderError field on November 15 2022 Affected Data Holders MUST implement the isSecondaryDataHolderError field by May 15 2023	May 15th 2023

Consent

Section	Description	Applicable Date
Amending Consent	Data Holders MUST implement the following standards from November 1st 2021 when a CDR consumer is invited to amend a current authorisation as per rule 4.22A and the ADR has supplied a cdr_arrangement_id	November 1st 2021
Data Recipient CDR Arrangement Endpoint	From March 31st 2022, Data Recipients MUST support "CDR Arrangement JWT" method and "CDR Arrangement Form Parameter" method. Data Recipients SHOULD support the "CDR Arrangement JWT" method before March 31st 2022	March 31st 2022
Data Recipient CDR Arrangement Endpoint	From July 31st 2022, Data Recipients MUST only support "CDR Arrangement JWT" method and MUST reject "CDR Arrangement Form Parameter" method. Data Holders MUST revoke consent using "CDR Arrangement JWT" method only. Data Holders SHOULD use the "CDR Arrangement JWT" method from March 31st 2022	July 31st 2022

Consumer Experience (CX)

Section	Description	Applicable Date
CX Standards: Unavailable Accounts	Data Holders MAY implement the following data standards effective from 1 November 2021: Unavailable Accounts: No accounts can be shown Unavailable Accounts: Authorisation not permitted Unavailable Accounts: Request sharing rights	November 1st 2021
CX Standards: Withdrawals	Data Holders MUST implement the following data standards effective from 1 February 2022: Withdrawal: Secondary User Instruction	February 1st 2022
Profile Scope Data Language	For new and amended consents and authorisations only, CDR participants SHOULD comply with the following standards from 1 February 2022, but MUST comply by 1 July 2022: Technical Standards: Revised Claims CX Standards: Profile Scope - Data Language Standards Note: These standards changes do not apply to existing consents and authorisations unless they are amended on or following the compliance dates.	July 1st 2022
CX Standards: Joint Accounts	Data holders MUST implement the following data standards from 1 July 2022: Notifications: Alternative notification schedules for joint accounts Notifications: Joint account alerts Authorisation: Pending status Withdrawal: Joint accounts	July 1st 2022

Information Security

See:

• CDS Security Profile

Section	Description	Applicable Date
Information Security profile	FAPI 1.0 adoption is introduced across three phases. Phase 1: Voluntary FAPI 1.0 support & hygiene enhancements includes, amongst other changes: Enforces requirements for authorisation code, token and request object use Data Holders MAY support of FAPI 1.0 Final Data Holders MAY support of Authorization Code Flow (including [PKCE] and [JARM]) in conjunction with Hybrid Flow	July 4th 2022
Self-Signed JWT Client Authentication	Until July 31st 2022, Data Recipients MUST accept the Resource Path for the endpoint and the <RecipientBaseURI> as a valid audience value. From July 31st 2022, Data Holders MUST use an audience value matching the Resource Path for the endpoint and the Data Recipient MUST verify the audience matches the Resource Path for the endpoint.	July 31st 2022
Registration Validation	Data Holders MUST ignore unsupported authorisation scopes presented in the SSA for the creation and update of client registrations from August 31st 2022	August 31st 2022
Information Security profile	FAPI 1.0 adoption is introduced across three phases. Phase 2: FAPI 1.0 Final (Baseline & Advanced) includes, amongst other changes: Enforces additional requirements for authorisation code, token and request object use Enforces PAR-only authorisation request data submission Refresh token cycling is not permitted Data Holders and Data Recipients MUST support FAPI 1.0 Final including [RFC9126], [RFC7636] and [JARM] Data Holders SHOULD support of Authorization Code Flow in conjunction with Hybrid Flow	September 16th 2022
Data Recipient CDR Arrangement Endpoint	From November 15th 2022, Data Recipients MUST validate the cdr_arrangement_id, if presented, is the same as the value included in the "CDR Arrangement JWT".	November 15th 2022
Registration Validation	Data Holders MUST ignore unsupported authorisation scopes presented in the SSA for the creation and update of client registrations from November 15th 2022	November 15th 2022
Information Security profile	FAPI 1.0 adoption is introduced across three phases. Phase 3: Retire Hybrid Flow includes, amongst other changes: Data Holders MUST support Authorization Code Flow Data Holders MUST support Hybrid Flow	April 14th 2023
Information Security profile	FAPI 1.0 adoption is introduced across four phases. Phase 4: Retire Hybrid Flow: Data Holders MAY retire Hybrid Flow on July 10th 2023	July 10th 2023