β Historical Obligations
This page summarises historical obligations for the Data Adapter, Management API, CDR Rules and Data Standards.
Note
See here for all current Future Dated Obligations.
Data Adapter Obligationsβ
This section outlines the obligations Data Adapter implementers must have met in order to complete a functional HaaS deployment.
| Reference | Obligation | Sector(s) | Obligation Date | Status | Summary |
|---|---|---|---|---|---|
| 25Q301 | Implement Adapter GetEndpointMetaV4 and ListBankingTransactionsV1 | Banking | 14-Jul-25 | Implemented in Magellan-RC7 | Adds additional NPP overlays to transaction details. |
| 25Q204 | Retire SECONDARY_USER_PRIVATE from EnumAdapterAccountRelationshipTypeV1 | All | 14-Jul-25 | Implemented in Magellan | Customers MUST no longer return this relationship type from the Data Adapter. If present, HaaS will ignore the relationship of that user on the account. |
| 25Q103 | Implement Adapter Get Endpoint Meta V3 operation | All | 17-Mar-25 | Implemented in Magellan | Customers MUST implement V3 of the Get Endpoint Meta endpoint which removes legacy SUPPORTS_V0_VERSIONING support as well as superseded List Energy Accounts V0 and List Energy Account Billing Transactions V0 |
| 25Q102 | Retire List Energy Account Billing Transactions V1 operation | Energy | Optional | Implemented in Magellan | Energy sector customers MAY retire V1 of the List Energy Account Billing Transactions endpoint if V2 is implemented |
| 25Q101 | Retire Adapter Profiles Phase 1:
| All | 01-Feb-25 | N/A | Customers MUST implement a supported adapter security profile |
| 24Q401 | Implement Adapter List Energy Accounts V2 operation | Energy | 15-Nov-24 | Implemented in Phobos | Energy sector customers MAY implement V2 of the List Energy Accounts endpoint to support CDS Get Energy Account Detail V4 if the adapter V1 upgrade mapping does not meet their business requirements |
| 24Q402 | Implement Adapter List Energy Account Billing Transactions V2 operation | Energy | 15-Nov-24 | Implemented in Phobos | Energy sector customers MAY implement V2 of the List Energy Account Billing Transactions endpoint to support CDS Get (Account|Specific Accounts|Bulk) Billing V3 if the adapter V1 upgrade mapping does not meet their business requirements |
| 24Q404 | Implement Adapter Get Endpoint Meta V2 operation | Energy | 15-Nov-24 | Implemented in Phobos | Energy sector customers MUST implement V2 of the Get Endpoint Meta endpoint if they have chosen to implement V2 of the List Energy Accounts endpoint or V2 of the List Energy Account Billing Transactions endpoint |
| 24Q403 | Restrict principalId's, userId's and accountId's to the following regular expression: ^[0-9A-Za-z .,=_-]+$ | All | 15-Nov-24 | Implemented in Phobos | Customers MUST ensure that all principalId's, userId's and accountId's returned from data adapter calls match the given regular expression |
| 24Q201 | Implement Adapter Get User Notification Info | All | 01-Jul-24 | Implemented in Vega | Customers MUST implement V0 of the Adapter Get User Notification Info operation |
| 24Q103 | Implement Adapter Versioning | Banking | 11-Mar-24 | Implemented in Helios | Banking sector customers MUST implement adapter versioning by this time |
| 24Q104 | Implement Get Endpoint Meta | Banking | 11-Mar-24 | Implemented in Helios | Banking sector customers MUST implement the Get Endpoint Meta endpoint by this time |
| 24Q105 | Implement Adapter listBankingPayments V1 operation | Banking | 11-Mar-24 | Implemented in Helios | Banking sector customers MUST implement V1 of the Adapter List Banking Payments endpoint to support Standards endpoint upgrades |
| 24Q101 | Retire Adapter getBankingCustomer endpoint and migrate to Adapter getCustomer | All | 11-Mar-24 | Implemented in Helios | Customers utilising the legacy getBankingCustomer operation MUST relocate this endpoint to the replacement operation of getCustomer |
| 24Q102 | Implement Adapter Get Health V0 operation | All | 11-Mar-24 | Implemented in Helios | Customers MUST implement V0 of the Adapter Get Health operation |
| 23Q101 | Implement customerUType and principal name in Adapter Get User response | All | 01-Feb-23 | Implemented in Apollo | Customers MUST introduce customerUType and principal name attributes in Get User responses to avoid fall through to Get Customer. Please note this has been mandatory since the Apollo Release in Feb 2023. |
| 23Q102 | Remove loginId from initLogin to align with Adapter getUsernameAttributes | All | 01-Feb-23 | Implemented in Apollo | loginId MUST be removed from initLogin to align with getUsernameAttributes. Please note this has been mandatory since the Apollo release in Feb 2023. |
| 23Q401 | Implement Adapter Versioning | Energy | 01-Nov-23 | Implemented in Lunokhod | Energy sector customers MUST implement adapter versioning by this time |
| 23Q402 | Implement Get Endpoint Meta | Energy | 01-Nov-23 | Implemented in Lunokhod | Energy sector customers MUST implement the Get Endpoint Meta endpoint by this time |
| 23Q403 | Implement Adapter listEnergyAccounts V1 operation | Energy | 01-Nov-23 | Implemented in Lunokhod | Energy sector customers MUST implement V1 of the List Energy Accounts endpoint to support Standards endpoint upgrades |
| 23Q404 | Implement Adapter listEnergyBillings V1 operation | Energy | 01-Nov-23 | Implemented in Lunokhod | Energy sector customers MUST implement V1 of the List Energy Billings endpoint to support Standards endpoint upgrades |
PRD Obligationsβ
Banking Obligationsβ
| Reference | Obligation | Obligation Date | Status | Summary |
|---|---|---|---|---|
| 25Q301 | GetBankingProductDetail V5 | 14-Jul-25 | Implemented in Magellan-RC7 | PRD Adapter Customers MUST implement GetBankingProductDetail V5 in their PRD Adapter |
Management APIβ
| Reference | Obligation | Sector(s) | Obligation Date | Status | Summary |
|---|---|---|---|---|---|
| 25Q104 | Implement the 1.31.0.0 specification for the withdrawJointAccount endpoint along with other changes | All | 17-Mar-25 | Implemented in Magellan | Customers utilising the management API MUST uplift their dashboards to use this new endpoint in order to comply with CDR rule 4A.12(2). Other changes in this specification include returning userId and principalId in GrantV1 so that clients can distinguish whether the grant was created by the user and principal in the request. |
| 25Q301 | Implement v5 of the Get Banking Product Detail endpoint by July 14th 2025. | Banking | 14-Jul-25 | Implemented in Magellan-RC7 | Data Holders MUST implement v5 of the Get Banking Product Detail endpoint by July 14th 2025. |
| 25Q104 | Implement the 1.31.0.0 specification for the withdrawJointAccount endpoint along with other changes | All | 17-Mar-25 | Customers utilising the management API MUST uplift their dashboards to use this new endpoint in order to comply with CDR rule 4A.12(2). Other changes in this specification include returning userId and principalId in GrantV1 so that clients can distinguish whether the grant was created by the user and principal in the request. | Implemented in Magellan |
| 24Q202 | Integrate with listGrantLogs for creation/amendment history | All | 01-Jul-24 | Customers utilising the management API MUST uplift their dashboards to use the grant creation and amendment events in Management API 1.17.0 to display the newly required amendment history. | Implemented in Vega |
Data Standards Obligationsβ
This section outlines historical FDOs mentioned in the Consumer Data Standards: Future Dated Obligations, when and how these obligations should have been met by HaaS and what customer actions were required to meet the obligation.
| Obligation | Sector(s) | Obligation Date | Status | Adapter Obligation | Summary |
|---|---|---|---|---|---|
| Retire Get Billing for Account V2, Get Bulk Billng V2 and Get Billing for Specific Account V2 | Energy | Optional | Magellan | 25Q103 | |
| Get Service Points V2 (25Q402) | Energy | 10-Nov-25 | Implemented in Magellan.09 | N/A | Data Holders MUST implement v2 the Get Service Points endpoint by November 10th 2025. Data Holders MAY retire v1 of this endpoint from March 16th 2026. |
| Get Service Point Details V2 (25Q403) | Energy | 10-Nov-25 | Implemented in Magellan.09 | N/A | Data Holders MUST implement v2 the Get Service Point Detail endpoint by November 10th 2025. Data Holders MAY retire v1 of this endpoint from March 16th 2026 |
| Get Service Points (SR) V2 (25Q404) | Energy | 10-Nov-25 | Implemented in Magellan.09 | N/A | Data Holders MUST implement v2 of the Get Service Points (SR) endpoint by November 10th 2025. Data Holders MAY retire v1 of this endpoint from March 16th 2026. |
| Get Service Point Detail (SR) V2 (25Q405) | Energy | 10-Nov-25 | Implemented in Magellan.09 | N/A | Data Holders MUST implement v2 of the Get Service Point Detail (SR) endpoint by November 10th 2025. Data Holders MAY retire v1 of this endpoint from March 16th 2026. |
| [Shared responsibilities -> Energy -> Additional Requirements] (25Q406) | Energy | Implemented in Magellan.09 | N/A | Energy data holders MUST support additional requirements for sharing electricity usage data according to the Last Consumer Change Date (LCCD) by November 10th 2025. | |
| Get Transaction Detail V2 | Banking | 14-Jul-25 | Implemented in Magellan-RC7 | 25Q301 | Get Transaction Detail V2 MUST be supported by July 14th 2025. |
| Get Banking Product Detail v5 | Banking | 14-Jul-25 | Implemented in Magellan-RC7 | N/A | Data Holders MUST implement v5 of the Get Banking Product Detail endpoint by July 14th 2025. |
| JARM encryption requirements | ALL | 10-Nov-25 | Implemented | N/A | [JARM encryption requirements] From November 10th 2025, Data Holders SHALL NOT perform authorization response encryption unless requested by the ADR |
| Report applicable error code | All | 12-May-25 | Implemented in Magellan | N/A | Data Holders MUST report on all applicable error codes by May 12th 2025 |
| Refresh tokens | All | 12-May-25 | Implemented prior to Magellan | N/A | Refresh Tokens MUST be issued with an exp value equal to the time of the sharing duration authorised by the consumer from May 12th 2025 |
| Authorization Code Flow | All | 12-May-25 | Implemented in Magellan | N/A | Data Holders SHALL only support Authorization Code Flow from May 12th 2025 |
| Get Energy Account Detail V4 | Energy | 11-Nov-2024 | Implemented in Phobos | N/A | Get Energy Account Detail V4 |
| Get (Account|Specific Accounts|Bulk) Billing V3 | Energy | 11-Nov-2024 | Implemented in Phobos | N/A | Get (Account|Specific Accounts|Bulk) Billing V3 |
| Get Generic Plan Detail V3 | Energy | 11-Nov-2024 | Denied | This is not required because HaaS does not handle energy PRD | |
| Revoke arrangement when user becomes ineligible | All | 17-Sep-2024 | Implemented in Mir | 2024Q301 | DHs MUST choose which data adapter change to make as per the minimum requirements |
| Data Holder Dashboards | All | 01-Jul-2024 | Implemented in Vega | ||
| Get Scheduled Payments For Account V2 Get Scheduled Payments Bulk V2 Get Scheduled Payments For Specific Accounts V2 | Banking | 11-Mar-24 | Implemented in Helios | 24Q105 | DHs MUST make V2 of these endpoints available |
| InfoSec Profile - FAPI 1.0 Transition Phase 4 | All | 10-Jul-2023 | Biza decommissioned Hybrid flow in Salyut. | ||
| Get Metrics V4 | All | 1-Nov-2023 | Superseded by V5 | Biza has chosen to skip V4 as is allowed by the CDS | |
| Get Metrics V5 | All | 13-May-2024 | Implemented in Salyut | Biza will collect new metrics and implement Get Metrics V5 | |
| Get Energy Account Detail V3 | Energy | 1-Nov-2023 | Implemented in Salyut | 23Q403 | |
| Get Billing For Account V2 Get Bulk Billing V2 Get Billing For Specific Accounts V2 | Energy | 1-Nov-2023 | Implemented in Salyut | 23Q404 | |
| Get Accounts V2 | Banking | 10-Jul-23 | Implemented in Soyuz | DHs MUST make V2 of this endpoint available | |
| Get Account Detail V3 | Banking | 10-Jul-23 | Implemented in Soyuz | DHs MUST make V3 of this endpoint available | |
| Secondary Data Holder flag | Energy | 15-May-2023 | Implemented in Apollo | DHs MUST implement isSecondaryDataHolderError field in error response. | |
| Get Energy Accounts V2 | Energy | 14-Apr-2023 | Implemented in OAO | DHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation. | |
| Get Energy Account Details V2 | Energy | 14-Apr-2023 | Implemented in OAO | DHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation. | |
| InfoSec Profile - FAPI 1.0 Transition Phase 3 | All | 14-Apr-2023 | Implemented in Apollo | DHs MUST support JARM for Authorisation Code Flow and MUST continue to support Hybrid Flow (until 10-Jul-23) | |
| Retire Get Account Detail V1 | Banking | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V1 of this endpoint | |
| Retire Get Product Detail V3 | Banking | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V3 of this endpoint | |
| Retire Get Customer Detail V1 | All | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V1 of this endpoint | |
| Get Account Detail V2 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Get Customer Detail V2 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Get Product Detail V4 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Retire Get Payees V1 | Banking | 31-Aug-22 | Implemented in OAO | Superseded by Get Payees V2 - FDO date 31-Jul-22 | |
| Retire Get Payee Detail V1 | Banking | 31-Aug-22 | Implemented in OAO | Superseded by Get Payee Detail V2 - FDO date 31-Jul-22 |
CDR Rules Obligationsβ
These historical Rules obligations were intended to align with the amendments to the CDR Rules up to F2023L01027 dated 11 July 2023.
| Obligation | Sector(s) | Obligation Date | Status | Adapter Obligation | Summary |
|---|---|---|---|---|---|
| Division 1.4: General provisions relating to data holders and to accredited persons 1.15(3)(h) | All | 1-Jul-2024 | Implemented in Vega | This will require Biza to uplift the HaaS Consumer Dashboard to fulfil the CX Standards created for this rule. | |
| Get Metrics V5 | All | 1-Jun-2024 | Implemented in Salyut | Biza will collect new metrics and implement Get Metrics V5 | |
| Tranche 4 - Large Retailers | Energy | 1-May-2024 | Implemented in Salyut | Large retailers servicing complex requests including large customers, secondary users and joint or partnership accounts | |
| Division 4.3: Giving and amending consents - accredited persons 4.14(2)(a) | All | 1-Dec-2023 | N/A | No change to the Biza HaaS platform is expected. | |
| Get Metrics V4 | All | 1-Nov-2023 | Superseded by V5 | Biza has chosen to skip V4 as is allowed by the CDS | |
| Division 4.4: Authorisations to disclose CDR data 4.26A | All | N/A | N/A | No change in existing behaviour is expected. | |
| InfoSec Profile - FAPI 1.0 Transition Phase 4 | All | 10-Jul-2023 | Biza decommissioned Hybrid flow in Salyut. | ||
| Get Energy Account Detail V3 | Energy | 1-Nov-2023 | Implemented in Salyut | 23Q403 | |
| Get Billing For Account V2 Get Bulk Billing V2 Get Billing For Specific Accounts V2 | Energy | 1-Nov-2023 | Implemented in Salyut | 23Q404 | |
| Get Accounts V2 | Banking | 10-Jul-23 | Implemented in Soyuz | DHs MUST make V2 of this endpoint available | |
| Get Account Detail V3 | Banking | 10-Jul-23 | Implemented in Soyuz | DHs MUST make V3 of this endpoint available | |
| Secondary Data Holder flag | Energy | 15-May-2023 | Implemented in Apollo | DHs MUST implement isSecondaryDataHolderError field in error response. | |
| Get Energy Accounts V2 | Energy | 14-Apr-2023 | Implemented in OAO | DHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation. | |
| Get Energy Account Details V2 | Energy | 14-Apr-2023 | Implemented in OAO | DHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation. | |
| InfoSec Profile - FAPI 1.0 Transition Phase 3 | All | 14-Apr-2023 | Implemented in Apollo | DHs MUST support JARM for Authorisation Code Flow and MUST continue to support Hybrid Flow (until 10-Jul-23) | |
| Retire Get Account Detail V1 | Banking | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V1 of this endpoint | |
| Retire Get Product Detail V3 | Banking | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V3 of this endpoint | |
| Retire Get Customer Detail V1 | All | 28-Feb-2023 | Retired in Soyuz | DHs MAY decommission V1 of this endpoint | |
| Get Account Detail V2 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Get Customer Detail V2 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Get Product Detail V4 | Banking | 30-Nov-22 | Implemented in OAO | ||
| Retire Get Payees V1 | Banking | 31-Aug-22 | Implemented in OAO | Superseded by Get Payees V2 - FDO date 31-Jul-22 | |
| Retire Get Payee Detail V1 | Banking | 31-Aug-22 | Implemented in OAO | Superseded by Get Payee Detail V2 - FDO date 31-Jul-22 |