Known Specification Issues

Known Specification Issues

Known issues with the latest versions of Open Banking specifications are detailed here. For each release, we have included a table that shows the issue and also any impact and/or mitigation.

This page is NOT concerned with issues relating to the implementation of the specifications (either by an ASPSP or a TPP) or for documentation and guides, but ONLY for the actual specifications. In many cases, these issues have already been fixed in a release candidate for the next version, which is available to all registered users in the Open Banking Collaboration Space

To report any other issues, please log via the Open Banking Service Desk.

 

Ref_No

 

Status

Details

Impact/Mitigation

Fix in Version

Area

Reporter

Reported

Reported

Service Desk Ticket Number

(OBL access only)

Work Item Ticket Number

(OBL Access Only)

Ref_No

 

Status

Details

Impact/Mitigation

Fix in Version

Area

Reporter

Reported

Reported

Service Desk Ticket Number

(OBL access only)

Work Item Ticket Number

(OBL Access Only)

v40_KI1

Open

Spec pages have OBCashAccountDebtor4 listed against Debtor and DebtorAccount in OBDomestic2

https://openbankinguk.github.io/read-write-api-site3/v4.0/resources-and-data-models/pisp/domestic-payment-consents.html#data-dictionary

In v3 the these objects contained the same fields and shared a base object (OBCashAccountDebtor4).

In v4:

  • DebtorAccount includes the new Proxy object

  • Debtor includes the new LEI field.

 

The initial release still referenced OBCashAccountDebtor4 for both these objects.

We will address this in a future release, the swaggers contain in-line definitions for some objects so payloads are unaffected.

Specs in future release

Swagger - update in future release (to remove in-line definitions)

Internal External repo- no change

Specs

ASPSP

Jul 2024

00049617

00049681

00049811

 

https://openbanking.atlassian.net/browse/CDRW-4870

v40_KI2

Closed

OBDomesticVRPInitiation and OBDomesticVRPInstruction contain CreditorAgent

CreditorAgent was removed in v319_KI9 and should not be present in VRP payloads. 

Specs - updated 19th September 2024

Swagger - updated 19th September 2024

Internal External repo- no change

VRP 

APSPS

Jul 2024

00049809

 

v40_KI3

Closed

The OBRemittanceInformation2/Unstructured data dictionary has the correct cardinality but the class column does not clearly indicate this is an array of Max140Text values. 

JSON examples show as a single entity rather than an array and Swagger has a length of 256 for the strings

OBRemittanceInformation2/Unstructured is an array of strings with Max140Text length each, as shown by the cardinality. The Data Dictionary class column will be updated in future release to further clarify this.

JSON examples will be updated in a future release and swagger will be updated in due course

Specs - updated 19th September 2024

Swagger - updated 19th September 2024

Internal External repo- no change

Spec

APSPS

Jul 2024

00049781

 

v40_KI4

Closed

CreditorAgent is listed in the OBDomesticVRPInstruction data dictionary but is not present in the UML or swagger

Duplicate of v40_KI2

CreditorAgent was removed in v319_KI9 and should not be listed in the Data Dictionary

N/A

VRP

APSPS

Jul 2024

00049747

 

v40_KI5

Closed

VRP spec pages list OBCashAccountDebtorWithName length as Max70Text but swagger lists it as Max350Text  

https://openbankinguk.github.io/read-write-api-site3/v4.0/resources-and-data-models/vrp/domestic-vrp-consents.html#obcashaccountdebtorwithname

Spec page is correct, swagger will be updated

Swagger - updated 19th September 2024

Internal External repo- no change

Swagger

TSP

Jul 2024

00049681

 

v40_KI6

Closed

OBWritePaymentDetails1 data dictionary is missing and UML shows wrong cardinality for Data and PaymentDetails.

VRP Payment details have been rolled back to v3 schema with ISO20022 values but table still shows the v4 changes

The data dictionary will be restored.

Swagger cardinality will be updated to show that Data is a singular mandatory field and PaymentStatus is an unbounded array of payment status details.

VRP swagger will be updated to match correct schema

UML diagrams will be updated when the spec pages are updated.

Specs - updated 19th September 2024

Swagger -updated 19th September 2024

Internal External repo- no change

PISP

TSP

Jul 2024

00049708

 

v40_KI7

Open

VRP & PISP Class name for the 'refund' object is misaligned between the data dictionary and swaggers

The data dictionary assigns the refund object class as "OBDomesticRefundAccount1" and in the swaggers this is defined inline without a class (PISP) or as OBCashAccountDebtorWithName (VRP).

Object definitions in the swaggers are correct and class names will be aligned in a future release

Specs/Swaggers - aligned in a future release

Internal External repo- no change

PISP & VRP

TSP

Jul 2024

00049811

https://openbanking.atlassian.net/browse/CDRW-4609

v40_KI8

Closed

Reference information missing from OBReadStandingOrder6

https://openbankinguk.github.io/read-write-api-site3/v4.0/resources-and-data-models/aisp/standing-orders.html#data-dictionary

This was replaced by RemittanceInformation but is missing from the payload.

Data Dictionary, UML and swaggers will be updated to include this object

Specs - updated 19th September 2024

Swagger - updated 19th September 2024

Internal External repo- no change

AISP

ASPSP

Jul 2024

00050015

 

v40_KI9

Open

ExternalPaymentTransactionStatus1Code was originally listed in ISO_External_CodeSet, this has been moved to OB_Internal_CodeSet

Codeset name is unchanged and can be found in the OB file.

Swaggers will be updated with the correct location.

Spec pages will be updated in next release to reference updated file.

 

Spec pages - updated in next release

Swaggers - updated updated 19th September 2024

Internal External repo in v4.0 onwards

PISP, VRP, AISP

Internal review

September 2024

 

https://openbanking.atlassian.net/browse/CDRW-4871

v40_KI10

Open

PISP Standing Order payload requires frequency to be provided.  This object is mandatory but is contained in an optional parent object.

 

The parent object, MandateRelatedInformation, will be mandatory in a future update.

Spec pages - next release

Swaggers - updated 19th September 2024

Internal External repo- no change

PISP

ASPSP

September 2024

 

https://openbanking.atlassian.net/browse/CDRW-4872

v40_KI11

Open

v4 File Payments status codes do not represent both the status of both file processing and subsequent payments within the file itself.

The codes will be rolled back to v3 alignment but with ISO 20022 values.  This ensures file status and payment details payloads can be returned successfully as per v3 implementations.

Spec page shows original codes from v4 release, participants should refer to the swagger file.

File payments will be reviewed at TDA in due course to determine what changes, if any, are appropriate.

Spec pages - next release

 

Swaggers - updated 19th September 2024

Internal External repo- no change

PISP

Interval Review

September 2024

 

https://openbanking.atlassian.net/browse/CDRW-4756

v40_KI12

Closed

Codeset updates

Codeset listings have been updated on the GitHub repository. Change-log available here

 

 

Spec pages – primarily aligned on 19th September 2024

v40_KI9 will be addressed in a future release

Swagger in refresh

Internal External repo in v4.0 onwards

All

Internal Review

September 2024

 

 

v40_KI13

Closed

Swagger updates - a number of misalignments have been identified and addressed in the swagger files.

Updated swaggers have been issued, change-log available here

Swaggers updated 19th September 2024

Internal External repo- no change

All

Internal Review

September 2024

 

 

v40_KI14

Closed

Spec page updates

In TDA decisions 268 and 269 it was agreed to publish a refreshed set of pages addressing minor issues.  The change log is available here

Spec Pages in refresh

Internal External repo- no change

All

Internal Review

September 2024

 

 

v40_KI15

Open

OBMultiAuthorisation1/Status is listed as as using the  OBExternalStatus2Code enum in  the top level data dictionary

The correct enumeration is OBInternalStatus2Code - searching the codeset repo for OBExternalStatus2Code will return the correct enumeration.

Spec pages in a future update

Swagger - no change required

Internal External repo- no change

PISP

ASPSP

October 2024

00053089

https://openbanking.atlassian.net/browse/CDRW-4672

v40_KI16

Open

International Payments Multi Authorisation table lists AWAU instead of AWAF

File Payments status table lists AWAU instead of AWAF

The correct value to return is AWAF

Spec pages - in a future update

Swaggers - updated in due course

Internal External repo- no change

PISP

ASPSP

October 2024

00053089

https://openbanking.atlassian.net/browse/CDRW-4669

https://openbanking.atlassian.net/browse/CDRW-4668

v40_KI17

Closed

OBWritePaymentDetailsResponse1 listing should be called OBWritePaymentDetails1 in both the heading and data dictionary

OBWritePaymentDetailsResponse1 contains OBWritePaymentDetails1 as part of the payload.  UML and swagger files show correct class name

 

Spec pages - primarily aligned on 19th September 2024

Swagger - no change required

Internal External repo- no change

PISP

ASPSP

October 2024

N/A

https://openbanking.atlassian.net/browse/CDRW-4673

v40_KI18

Closed

OBWriteDomesticResponse5 is missing the RCVD enum value in the swagger file

RCVD is listed on the spec pages and Codeset repository.  Swagger will be updated in due course

Spec pages - no change

Swagger - addressed in v4.0 Swagger update 3

Internal External repo- no change

PISP

ASPSP

October 2024

N/A

https://openbanking.atlassian.net/browse/CDRW-4667

v40_KI19

Open

OBParty2/Phone and OBParty2/Mobile data dictionary regex listing is missing the preceding slash.

One of the JSON examples phone numbers on the page is missing the dash.

Examples for PhoneNumber_0 (Phone) and PhoneNumber_1 (Mobile) in the OBParty2 swagger are missing the dash.

Correct regex is \+[0-9]{1,3}-[0-9()+\-]{1,30}

Phone number examples should contain a dash: +44-5556541109

Spec pages - in a future update

Swagger - addressed in v4.0 Swagger update 3

Internal External repo- no change

AISP

Internal Review

October 2024

N/A

https://openbanking.atlassian.net/browse/CDRW-4671

v40_KI20

Open

OBReadTransaction6/Data/Transaction/BankTransactionCode/Code uses ExternalBankTransactionFamily1Code which is defined as a 4 character code in ISO 20022 but JSON examples use the longer Code Names.

OBReadTransaction6/Data/Transaction/BankTransactionCode/SubCode uses ExternalBankTransactionSubFamily1Code which is defined as a 4 character code in ISO 20022 but JSON examples use the longer Code Names.

Examples will be updated with correct codes

Spec pages - in a future update

Internal External repo- no change

 

AISP

ASPSP

October 2024

00051935

https://openbanking.atlassian.net/browse/CDRW-4657

v40_KI21

Open

Balance Transfer example in reference page needs updating

Examples in that section will be reviewed and updated for a future release.

Spec pages - in a future update

Internal External repo- no change

PISP

ASPSP

October 2024

00052502

https://openbanking.atlassian.net/browse/CDRW-4658

v40_KI22

Closed

File Payments payload is missing UK.OBIE.PaymentInitiation.4.0 from the FileType enum

Swagger will be updated: UK.OBIE.PaymentInitiation.4.0 will replace UK.OBIE.PaymentInitiation.3.1

Specs - no change

Swagger - addressed in v4.0 Swagger update 3

Internal External repo- no change

PISP

ASPSP/Internal review

November 2024

00053447

https://openbanking.atlassian.net/browse/CDRW-4675

v40_KI23

Open

Item 2 of the Access Revocation description is misaligned to CEG wording:

The status of the account-access-consent must be changed to CANC and the AISP must be allowed to request PSU to re-authenticate the same account-access-consent resource.

The text will be aligned to the language used in the CEG:

 

The status of the account-access-consent should be changed to CANC. If the status of the consent is updated then an appropriate reason must be provided in StatusReason. The AISP must be allowed to request PSU to re-authenticate the same account-access-consent resource.

Specs - in a future updated

Swagger/FCS - no change

Internal External repo- no change

AISP

ASPSP

November 2024

00053437

https://openbanking.atlassian.net/browse/CDRW-4693

v40_KI24

Closed

File Payments swagger is missing CreditorAgent in the initiation block of OBWriteFile2 and UltimateDebtor field reference points to the UltimateCreditor schema