Skip to main content

βŒ› 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.

ReferenceObligationSector(s)Obligation DateStatusSummary
25Q301Implement Adapter GetEndpointMetaV4 and ListBankingTransactionsV1Banking14-Jul-25Implemented in Magellan-RC7Adds additional NPP overlays to transaction details.
25Q204Retire SECONDARY_USER_PRIVATE from EnumAdapterAccountRelationshipTypeV1All14-Jul-25Implemented in MagellanCustomers MUST no longer return this relationship type from the Data Adapter. If present, HaaS will ignore the relationship of that user on the account.
25Q103Implement Adapter Get Endpoint Meta V3 operationAll17-Mar-25Implemented in MagellanCustomers 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
25Q102Retire List Energy Account Billing Transactions V1 operationEnergyOptionalImplemented in MagellanEnergy sector customers MAY retire V1 of the List Energy Account Billing Transactions endpoint if V2 is implemented
25Q101Retire Adapter Profiles Phase 1:
  • Azure Private Link + MTLS + Static API
  • IPSEC Tunnel + MTLS + Static API Key
  • AWS ELB via PrivateLink + MTLS + Static API Key
  • AWS ELB via PrivateLink + MTLS + Implicit Trust
All01-Feb-25N/ACustomers MUST implement a supported adapter security profile
24Q401Implement Adapter List Energy Accounts V2 operationEnergy15-Nov-24Implemented in PhobosEnergy 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
24Q402Implement Adapter List Energy Account Billing Transactions V2 operationEnergy15-Nov-24Implemented in PhobosEnergy 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
24Q404Implement Adapter Get Endpoint Meta V2 operationEnergy15-Nov-24Implemented in PhobosEnergy 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
24Q403Restrict principalId's, userId's and accountId's to the following regular expression: ^[0-9A-Za-z .,=_-]+$All15-Nov-24Implemented in PhobosCustomers MUST ensure that all principalId's, userId's and accountId's returned from data adapter calls match the given regular expression
24Q201Implement Adapter Get User Notification InfoAll01-Jul-24Implemented in VegaCustomers MUST implement V0 of the Adapter Get User Notification Info operation
24Q103Implement Adapter VersioningBanking11-Mar-24Implemented in HeliosBanking sector customers MUST implement adapter versioning by this time
24Q104Implement Get Endpoint MetaBanking11-Mar-24Implemented in HeliosBanking sector customers MUST implement the Get Endpoint Meta endpoint by this time
24Q105Implement Adapter listBankingPayments V1 operationBanking11-Mar-24Implemented in HeliosBanking sector customers MUST implement V1 of the Adapter List Banking Payments endpoint to support Standards endpoint upgrades
24Q101Retire Adapter getBankingCustomer endpoint and migrate to Adapter getCustomerAll11-Mar-24Implemented in HeliosCustomers utilising the legacy getBankingCustomer operation MUST relocate this endpoint to the replacement operation of getCustomer
24Q102Implement Adapter Get Health V0 operationAll11-Mar-24Implemented in HeliosCustomers MUST implement V0 of the Adapter Get Health operation
23Q101Implement customerUType and principal name in Adapter Get User responseAll01-Feb-23Implemented in ApolloCustomers 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.
23Q102Remove loginId from initLogin to align with Adapter getUsernameAttributesAll01-Feb-23Implemented in ApollologinId MUST be removed from initLogin to align with getUsernameAttributes. Please note this has been mandatory since the Apollo release in Feb 2023.
23Q401Implement Adapter VersioningEnergy01-Nov-23Implemented in LunokhodEnergy sector customers MUST implement adapter versioning by this time
23Q402Implement Get Endpoint MetaEnergy01-Nov-23Implemented in LunokhodEnergy sector customers MUST implement the Get Endpoint Meta endpoint by this time
23Q403Implement Adapter listEnergyAccounts V1 operationEnergy01-Nov-23Implemented in LunokhodEnergy sector customers MUST implement V1 of the List Energy Accounts endpoint to support Standards endpoint upgrades
23Q404Implement Adapter listEnergyBillings V1 operationEnergy01-Nov-23Implemented in LunokhodEnergy sector customers MUST implement V1 of the List Energy Billings endpoint to support Standards endpoint upgrades

PRD Obligations​

Banking Obligations​

ReferenceObligationObligation DateStatusSummary
25Q301GetBankingProductDetail V514-Jul-25Implemented in Magellan-RC7PRD Adapter Customers MUST implement GetBankingProductDetail V5 in their PRD Adapter

Management API​

ReferenceObligationSector(s)Obligation DateStatusSummary
25Q104Implement the 1.31.0.0 specification for the withdrawJointAccount endpoint along with other changesAll17-Mar-25Implemented in MagellanCustomers 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.
25Q301Implement v5 of the Get Banking Product Detail endpoint by July 14th 2025.Banking14-Jul-25Implemented in Magellan-RC7Data Holders MUST implement v5 of the Get Banking Product Detail endpoint by July 14th 2025.
25Q104Implement the 1.31.0.0 specification for the withdrawJointAccount endpoint along with other changesAll17-Mar-25Customers 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
24Q202Integrate with listGrantLogs for creation/amendment historyAll01-Jul-24Customers 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.

ObligationSector(s)Obligation DateStatusAdapter ObligationSummary
Retire Get Billing for Account V2, Get Bulk Billng V2 and Get Billing for Specific Account V2EnergyOptionalMagellan25Q103
Get Service Points V2 (25Q402)Energy10-Nov-25Implemented in Magellan.09N/AData 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)Energy10-Nov-25Implemented in Magellan.09N/AData 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)Energy10-Nov-25Implemented in Magellan.09N/AData 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)Energy10-Nov-25Implemented in Magellan.09N/AData 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)EnergyImplemented in Magellan.09N/AEnergy 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 V2Banking14-Jul-25Implemented in Magellan-RC725Q301Get Transaction Detail V2 MUST be supported by July 14th 2025.
Get Banking Product Detail v5Banking14-Jul-25Implemented in Magellan-RC7N/AData Holders MUST implement v5 of the Get Banking Product Detail endpoint by July 14th 2025.
JARM encryption requirementsALL10-Nov-25ImplementedN/A[JARM encryption requirements] From November 10th 2025, Data Holders SHALL NOT perform authorization response encryption unless requested by the ADR
Report applicable error codeAll12-May-25Implemented in MagellanN/AData Holders MUST report on all applicable error codes by May 12th 2025
Refresh tokensAll12-May-25Implemented prior to MagellanN/ARefresh 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 FlowAll12-May-25Implemented in MagellanN/AData Holders SHALL only support Authorization Code Flow from May 12th 2025
Get Energy Account Detail V4Energy11-Nov-2024Implemented in PhobosN/AGet Energy Account Detail V4
Get (Account|Specific Accounts|Bulk) Billing V3Energy11-Nov-2024Implemented in PhobosN/AGet (Account|Specific Accounts|Bulk) Billing V3
Get Generic Plan Detail V3Energy11-Nov-2024DeniedThis is not required because HaaS does not handle energy PRD
Revoke arrangement when user becomes ineligibleAll17-Sep-2024Implemented in Mir2024Q301DHs MUST choose which data adapter change to make as per the minimum requirements
Data Holder DashboardsAll01-Jul-2024Implemented in Vega
Get Scheduled Payments For Account V2
Get Scheduled Payments Bulk V2
Get Scheduled Payments For Specific Accounts V2
Banking11-Mar-24Implemented in Helios24Q105DHs MUST make V2 of these endpoints available
InfoSec Profile - FAPI 1.0 Transition Phase 4All10-Jul-2023Biza decommissioned Hybrid flow in Salyut.
Get Metrics V4All1-Nov-2023Superseded by V5Biza has chosen to skip V4 as is allowed by the CDS
Get Metrics V5All13-May-2024Implemented in SalyutBiza will collect new metrics and implement Get Metrics V5
Get Energy Account Detail V3Energy1-Nov-2023Implemented in Salyut23Q403
Get Billing For Account V2
Get Bulk Billing V2
Get Billing For Specific Accounts V2
Energy1-Nov-2023Implemented in Salyut23Q404
Get Accounts V2Banking10-Jul-23Implemented in SoyuzDHs MUST make V2 of this endpoint available
Get Account Detail V3Banking10-Jul-23Implemented in SoyuzDHs MUST make V3 of this endpoint available
Secondary Data Holder flagEnergy15-May-2023Implemented in ApolloDHs MUST implement isSecondaryDataHolderError field in error response.
Get Energy Accounts V2Energy14-Apr-2023Implemented in OAODHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation.
Get Energy Account Details V2Energy14-Apr-2023Implemented in OAODHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation.
InfoSec Profile - FAPI 1.0 Transition Phase 3All14-Apr-2023Implemented in ApolloDHs MUST support JARM for Authorisation Code Flow and MUST continue to support Hybrid Flow (until 10-Jul-23)
Retire Get Account Detail V1Banking28-Feb-2023Retired in SoyuzDHs MAY decommission V1 of this endpoint
Retire Get Product Detail V3Banking28-Feb-2023Retired in SoyuzDHs MAY decommission V3 of this endpoint
Retire Get Customer Detail V1All28-Feb-2023Retired in SoyuzDHs MAY decommission V1 of this endpoint
Get Account Detail V2Banking30-Nov-22Implemented in OAO
Get Customer Detail V2Banking30-Nov-22Implemented in OAO
Get Product Detail V4Banking30-Nov-22Implemented in OAO
Retire Get Payees V1Banking31-Aug-22Implemented in OAOSuperseded by Get Payees V2 - FDO date 31-Jul-22
Retire Get Payee Detail V1Banking31-Aug-22Implemented in OAOSuperseded 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.

ObligationSector(s)Obligation DateStatusAdapter ObligationSummary
Division 1.4: General provisions relating to data holders and to accredited persons 1.15(3)(h)All1-Jul-2024Implemented in VegaThis will require Biza to uplift the HaaS Consumer Dashboard to fulfil the CX Standards created for this rule.

Get Metrics V5All1-Jun-2024Implemented in SalyutBiza will collect new metrics and implement Get Metrics V5
Tranche 4 - Large RetailersEnergy1-May-2024Implemented in SalyutLarge 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)All1-Dec-2023N/ANo change to the Biza HaaS platform is expected.
Get Metrics V4All1-Nov-2023Superseded by V5Biza has chosen to skip V4 as is allowed by the CDS
Division 4.4: Authorisations to disclose CDR data 4.26AAllN/AN/ANo change in existing behaviour is expected.
InfoSec Profile - FAPI 1.0 Transition Phase 4All10-Jul-2023Biza decommissioned Hybrid flow in Salyut.
Get Energy Account Detail V3Energy1-Nov-2023Implemented in Salyut23Q403
Get Billing For Account V2
Get Bulk Billing V2
Get Billing For Specific Accounts V2
Energy1-Nov-2023Implemented in Salyut23Q404
Get Accounts V2Banking10-Jul-23Implemented in SoyuzDHs MUST make V2 of this endpoint available
Get Account Detail V3Banking10-Jul-23Implemented in SoyuzDHs MUST make V3 of this endpoint available
Secondary Data Holder flagEnergy15-May-2023Implemented in ApolloDHs MUST implement isSecondaryDataHolderError field in error response.
Get Energy Accounts V2Energy14-Apr-2023Implemented in OAODHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation.
Get Energy Account Details V2Energy14-Apr-2023Implemented in OAODHs MUST implement V2 of this endpoint. Closed account support implemented in initial energy implementation.
InfoSec Profile - FAPI 1.0 Transition Phase 3All14-Apr-2023Implemented in ApolloDHs MUST support JARM for Authorisation Code Flow and MUST continue to support Hybrid Flow (until 10-Jul-23)
Retire Get Account Detail V1Banking28-Feb-2023Retired in SoyuzDHs MAY decommission V1 of this endpoint
Retire Get Product Detail V3Banking28-Feb-2023Retired in SoyuzDHs MAY decommission V3 of this endpoint
Retire Get Customer Detail V1All28-Feb-2023Retired in SoyuzDHs MAY decommission V1 of this endpoint
Get Account Detail V2Banking30-Nov-22Implemented in OAO
Get Customer Detail V2Banking30-Nov-22Implemented in OAO
Get Product Detail V4Banking30-Nov-22Implemented in OAO
Retire Get Payees V1Banking31-Aug-22Implemented in OAOSuperseded by Get Payees V2 - FDO date 31-Jul-22
Retire Get Payee Detail V1Banking31-Aug-22Implemented in OAOSuperseded by Get Payee Detail V2 - FDO date 31-Jul-22