# Version control

# v4.0.1 Release Candidate 2 - 2026-02-04

# Added

Added LWMH, LXMH, & TWYR to Frequency Examples in PIS Domestic Standing Order consents & AIS Standing Orders
Added Frequency Examples table to PIS International Standing Order Consents
[CDRW-4937] - added example of query string date-time where only the Date is required.

# Fixed

Fixed list formatting in transaction permissions code (opens new window)
Fixed the table of contents links on the majority of pages.
[v40_KI48] - OBReadStatement2/Data/Statement/StatementInterest/RateType was incorrectly listed as using OBInternalStatementInterestType1Code, this has been corrected to OBInternalStatementInterestRateType1Code

# Changed

[CDRW-4948] - Description for OBReadStatement2/Data/Statement/StatementFee/RateType changed to "This code indicates the specific type of fee rate (e.g., AER, EAR)"
[CDRW-4948] - Description for OBReadStatement2/Data/Statement/StatementInterest/RateType changed to "This code specifies the type of interest (e.g., BOE Base Rate, Fixed Rate, Gross)"
[CDRW-4937] - Amended description of query string date-time usage to clarify how to represent values where only the Date component is required.

# v4.0.1 Release Candidate 1 - 2026-01-05

# Changed

Updated Payment Initiation Release Management (opens new window) section to consistently reference ConsentId in the consent section.
Moved the initial File Payment status information to the POST /file-payments (opens new window) section.

# v4.0.1 Draft 1 - 2025-11-20

# Added

Add OBRemittanceInformation2 definition and Data Dictionary to AIS Standing Orders page (opens new window)
Added a note regarding the use of ExternalPaymentTransactionStatus1Code values in payment-details endpoints in PIS (opens new window) and Domestic VRPs (opens new window)
Optional Rate Limit Headers (opens new window) added.
NumberOfPayments has been restored to the following classes and guidance advising that TPPs should refer to ASPSP developer portals for further information on whether NumberOfPayments is supported has been added to the pages above the data dictionaries:
The following text has been added to OBMandateRelatedInformation1/Frequency/Type on the Account and Transaction API Profile (opens new window) and Payment Initiation API Profile (opens new window) pages:

For compatibility with v3, an ASPSP may choose to optionally support legacy v3 regex patterns in this field.

TPPs should refer to ASPSP developer portals for further information on whether legacy values are supported, alongside any additional information relevant to MandateRelatedInformation usage.
OBCashAccountDebtorWithName has been added to:
Clarification on the usage of the term 'optional fields' (opens new window) in reference to Conditional fields.
An overarching Events Release Management (opens new window) section has been introduced to the Event Notification API Profile
OBReferredDocumentInformation has been split out from OBRemittanceInformation2 and added to the following pages:
Added additional guidance to POST /file-payment-consents/{ConsentId}/file (opens new window):
- ASPSPs should document accepted file types on their developer portal.
- ASPSPs who accept the UK.OBIE.PaymentInitiation.4.0 file type should specify which payload schemas they accept as payload structures vary across payment types.
  - E.g. An ASPSP accepting domestic, international and domestic standing orders via file payment should explicitly specify support for these 3 payload schemas on their developer portal.
Added a Release Management (opens new window) section to the Variable Recurring Payments API Profile
Introduced a new OBIntermediaryAgent (opens new window) class which can appear up to 3 times in payload as IntermediaryAgent1, IntermediaryAgent2 and IntermediaryAgent3.
- This is used in OBReadTransaction6/Data/Transaction (opens new window)
- Returning these fields requires use of the ReadTransactionDetail permission and the Permission Codes table (opens new window) has been updated accordingly.
Added the following guidance to the Transactions notes (opens new window):
- TPPs should refer to ASPSP developer portals for information on whether individual Bacs transactions are available in the Transactions endpoint.
Added the following note to File Payments (opens new window):
- TPPs should refer to ASPSP developer portals for information on which File Payment endpoints are available, specification of accepted file format(s) and information on File Payment statuses.
Clarified how Mandatory (opens new window) and Conditional (opens new window) fields are represented in the Data Dictionaries.
- Mandatory fields are represented as 1..1 or 1..* in the Data Dictionary Occurrence column and UML diagrams.
- Conditional fields are represented as 0..1 or 0..* in the Data Dictionary Occurrence column and UML diagrams
Added guidance to the Transaction page (opens new window) for returning Counterparty information in the TransactionInformation field.
ReadStandingOrdersBasic and ReadStandingOrdersDetail added to overarching Permission Codes list (opens new window)

# Changed

Updated the relevant OBInternalConsentStatus1Code codeset references throughout PIS response data dictionaries, to use separated codesets:
- Changed to OBInternalConsentStatus2Code in:
- Changed to OBInternalConsentStatus3Code in:
  - File Payment Consent (opens new window)
Remap ReferredDocumentAmount from Int32 to OBActiveCurrencyAndAmount_SimpleType in OBRemittanceInformation2 located in PIS (opens new window), VRP (opens new window), and AIS (Standing Orders) (opens new window)
Updated the relevant ExternalPaymentTransactionStatus1Code codeset references to use separate codesets:
- Changed to ExternalPaymentTransactionStatus2Code in:
  - Domestic Scheduled Payments (opens new window)
  - International Scheduled Payments (opens new window)
- Changed to ExternalPaymentTransactionStatus3Code in:
  - Domestic Payments (opens new window)
  - International Payments (opens new window)
- Changed to ExternalPaymentTransactionStatus4Code in:
  - File Payments (opens new window)
- Changed to ExternalPaymentTransactionStatus5Code in:
  - Domestic VRPs (opens new window)
Event Notification Resources (opens new window) are now listed under the Event Notification API (opens new window) section.
Meta (opens new window) has been reclassified as conditional.
Links (opens new window) has been reclassified as conditional.
The Multiple Authorisation (opens new window) text has been updated to include the full set of values for AuthorisationType (Single, Multiple or Any).
TPPs and ASPSPs must now verify payload signatures (opens new window) - previously this was should.
VRP instance of OBCashAccountDebtorWithName/Name max size has increased from 70 to 350 to align with other areas of the spec and is no longer mandatory.
The following classes have been updated to use OBCashAccountDebtorWithName instead of OBCashAccount6:
- OBReadTransaction6/Data/Transaction/DebtorAccount (opens new window)
- OBFundsConfirmationConsent1/Data/DebtorAccount (opens new window)
- OBDomestic2/DebtorAccount (opens new window)
- OBDomesticScheduled2/DebtorAccount (opens new window)
- OBDomesticStandingOrder3/DebtorAccount (opens new window)
- OBFile2/DebtorAccount (opens new window)
- OBInternational3/DebtorAccount (opens new window)
- OBInternationalScheduled3/DebtorAccount (opens new window)
- OBInternationalStandingOrder4/DebtorAccount (opens new window)
The 'Optional Fields' section describing changes to payloads when a field has no value has been renamed to Conditional Fields (opens new window)
OBRemittanceInformation2/Structured/ReferredDocumentInformation updated from Array to Array of OBReferredDocumentInformation on the following pages:
- Payment Initiation API Profile (opens new window)
- AIS - Standing Orders (opens new window)
- Variable Recurring Payments API Profile (opens new window)
OBReferredDocumentInformation/LineDetails (previously displayed as part of the OBRemittanceInformation2 class) has been updated to have a maximum string length of 2048 characters on the following pages:
- Payment Initiation API Profile (opens new window)
- AIS - Standing Orders (opens new window)
- Variable Recurring Payments API Profile (opens new window)
Removed incorrect File Payment Status codes and replaced with guidance that the initial Status must be PDNG (opens new window)
Replaced incorrect File Payment State Model diagram (opens new window).
Updated File Payment Multiple Authorisation state model guidance (opens new window) to use correct status codes.
Corrected both the Domestic (opens new window) and International (opens new window) Scheduled Payment state diagrams.
Updated ISO 20022 text (opens new window) to replace references to draft standards with final standards such as the Regulatory Technical Standards on strong customer authentication
Replaced 'ReceivedCreditTransfer' and 'DomesticCreditTransfer' with 'RCDT' and 'DMCT' in usage examples (Transactions - v4.0.1 (opens new window))
Replaced AWAU with AWAF for Multiple Authorisation in File Payments (File Payments - v4.0.1 (opens new window))
Added clarification to PointInTime in the Data Dictionary to note that negative numbers are permitted (Payment Initiation API Profile - v4.0.1 (opens new window))

# Removed

Removed incorrect OBInternalPermissions1Code codeset references from the following locations:
Removed invalid reference to OBExternalConsentProprietaryCode codeset in GET /domestic-standing-order-consents/{ConsentId} (opens new window)
Removed Signed Response from the Endpoints Table (opens new window) for POST /file-payment-consents/{ConsentId}/file.
The Release Management section has been removed from both Callback URL API Profile (opens new window) and Event Notification Subscription API Profile (opens new window). The top level Event Notification API Profile Release Management (opens new window) should be used instead.
Removed Risk from the DomesticConsent Data Dictionary (Domestic Payments Consents - v4.0.1 (opens new window))

# Fixed

Fixed incorrect codeset reference for StatusReasonCode from OBInternalPermissions1Code to OBExternalStatusReason1Code in the response data dictionaries for the following locations:
OBActiveCurrencyAndAmount_SimpleType regex pattern was not displaying correctly for the following fields on Payment Initiation API Profile (opens new window) and Variable Recurring Payments API Profile (opens new window).
- OBCharge2/Amount/Amount
- OBRemittanceInformation2/Structured/ReferredDocumentAmount
- OBRegulatoryReporting1/Details/Amount/Amount
Corrected the dates shown in the Examples of Periodic Limits (Examples 2 and 3) VRP Example 2 (opens new window) and VRP Example 3 (opens new window)
Addressed various typos:
- Added \ to the Pattern for Phone and Mobile in the Data Dictionary (opens new window)
- Added text to Overview re conditional Parties endpoints and fields, explaining what ASPSPs must do if they have implemented the /accounts/{AccountId}/parties' endpoint Overview (opens new window)
- Corrected typo in Release Management from 'create don' to 'created on' Release Management (opens new window)
- Corrected typo (missing a 'with') on Release Management (opens new window)
- Corrected class from OBWritePaymentDetailsResponse1 to OBWritePaymentDetails1 (opens new window)
- Corrected Codeset for ExternalPaymentTransactionStatus1Code from ISO_External_CodeSet to OB_Internal_CodeSet Data Dictionary (opens new window)
Fixed PaymentContextCode in 2 examples from 'TransferToSell' to 'TransferToSelf' Usage Examples (opens new window)
Fixed the link to Permissions information across Transactions (opens new window), Accounts (opens new window) and Accounts & Transactions (opens new window) (AISP Resources and Data Models - v4.0.1 (opens new window))
Corrected the wording in the Permissions table re ReadPAN Permissions Table (opens new window)
Added additional text to POST/domestic-payments to clarify the approach to status changes (applied to Domestic Payments, Domestic Scheduled Payments, Domestic Standing Orders, International Payments, International Scheduled Payments, International Standing Orders) Example wording from Post/domestic-payments (opens new window) with same wording used for each of the payment types.
Corrected MandateRelatedInformation to be 1..1 and confirm that frequency detail is mandatory Data Dictionary (opens new window)

← Namespaced Enumerations Account Access Consents→