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.

...

Expand

title	Read/Write API v3.1.9

Ref_No

Status

Details

Impact/Mitigation

Area

Reporter

Reported

Service Desk Ticket Number

(OBIE access only)

Work Item Ticket Number

(OBIE Access Only)

v319_KI1

Open

For AISP: OBReadConsent1:

UML diagrams are incorrectly showing the Permissions field as 0..1 in version 3.1.7 and v3.1.8

Fix UML diagram in v3.1.8 and v3.1.7 to reflect Permissions 1..1
Update to swagger

VRP

ASPSP

Oct-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26532

v319_KI2

Open

UML diagram is incorrectly showing Instructed amount field as 0..1

Following objects will be fixed

VRP Domestic VRP Instruction,

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrps.html#obdomesticvrpinstruction

2. VRP Domestic VRP Request.

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrps.html#obdomesticvrprequest

3. VRP Domestic VRP Response

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrps.html#obdomesticvrpresponse

Fix UML diagram to reflect Instructed amount field as 1..1 in below objects
1. OBDomesticVRPInstruction
2. OBDomesticVRPRequest
3. OBDomesticVRPResponse
Update swagger

VRP

ASPSP

Sep-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26140

v319_KI3

Open

Fix in section to remove 'Revoked' status

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#state-model-vrp-consents

Changes removed are ~~struck out~~ and added are in blue

Update state model diagram to remove the status.
Update below table under state model - vrp consents section

	Status	Status Description
1	AwaitingAuthorisation	The consent resource is awaiting PSU authorisation.
2	Rejected	The consent resource has been rejected.
3	Authorised	The consent resource has been successfully authorised.
4	~~Revoked~~	~~The consent resource has been revoked by the PSU, via ASPSP's online channel~~.

3. Update swagger

VRP

ASPSP

Sep-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26142

v319_KI4

Open

Fix in section to remove 'Revoked' status

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpconsentresponse

Changes removed are ~~struck out~~ and added are in blue

Name	Path	Definition	Type
Data (1..1)	Data
ConsentId (1..1)	Data. ConsentId	Unique identification as assigned by the ASPSP to uniquely identify the consent resource.	Max128Text
Data. ReadRefundAccount (0..1)	Data. ReadRefundAccount	Indicates whether the RefundAccount object should be included in the response	Yes No
CreationDateTime (1..1)	Data. CreationDateTime	Date and time at which the resource was created.	ISODateTime
Status (1..1)	Data. Status	Specifies the status of the resource in code form.	Authorised AwaitingAuthorisation Rejected ~~Revoked~~ ~~Expired~~
StatusUpdateDateTime (1..1)	Data. StatusUpdateDateTime	Date and time at which the resource status was updated.	ISODateTime
ControlParameters (1..1)	Data. ControlParameters	The control parameters under which this VRP must operate	OBDomesticVRPControlParameters
Initiation (1..1)	Data. Initiation	The parameters of the VRP consent that should remain unchanged for each payment under this VRP	OBDomesticVRPInitiation
DebtorAccount (0..1)	Data.DebtorAccount	The approved DebtorAccount that the payment can be made from. THhe value must be populated for GET responses once the consent is approved.	OBCashAccountDebtorWithName
Risk (1..1)	Risk	The consent payload is sent by the initiating party to the ASPSP. It is used to request a consent to move funds from the debtor account to a creditor.	OBRisk

v319_KI5

Open

Fix to section - Consent revocation

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/profiles/vrp-profile.html#consent-revocation

A PSU may revoke consent for initiation of any future payment orders, by revoking the authorisation of VRP Consent, at any point in time.

The PSU may request the TPP to revoke the consent that it has authorised. If consent is revoked with the TPP:

The TPP must cease to initiate any future payment orders or Funds Confirmations using the VRP Consent.
The TPP must call the DELETE operation on the VRP Consent resource to indicate to the ASPSP that the PSU has revoked consent.

The PSU may revoke the VRP ~~Consent~~ access via ASPSP's online channel. If the ~~consent~~ access is revoked via ASPSP:

~~The ASPSP must immediately update the VRP Consent resource status to Revoked.~~
The ASPSP must fail any future payment order request using the ConsentId, ~~with the Status Revoked.~~
The ASPSP must make a Notification Event available for the TPP to poll/deliver Real-Time Event Notification for the event - consent-authorization-revoked.
The ASPSP must take the necessary action to revoke access e.g. by revoking/expiring the access token provided to the PISP.
The status of the domestic-vrp-consents must remain unchanged and the PISP must be allowed to request PSU to re-authenticate the same domestic-vrp-consents resource.
Upon successful re-authentication by PSU, an ASPSP may issue new authorization code and subsequently new access token to the PISP.

v319_KI6

Open

Fix to UML on Debtor Account

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpconsentresponse

Note: The field is marked as optional to address the scenario when a/c selection happens at ASPSP. The debtor account must be provided in the GET response after the PSU has selected the a/c at the ASPSP and the consent is approved.

Update UML diagram to make DebtorAccount block option in OBDomesticVRPConsentResponse block.
Update to swagger.

VRP

ASPSP

Sep-2021

Jira Legacy

server	System JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26403

v319_KI7

Open

Fix to UML and table

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpcontrolparameters

Fix to UML

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpconsentrequest

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpconsentresponse

Fix UML diagram & table (where relevant) to reflect MaximumIndividualAmount as 1..1 and PeriodicLimits field as 1..* in below objects
1. OBDomesticVRPControlParameters
2. OBDomesticVRPConsentRequest
3. OBDomesticVRPConsentResponse
Update swagger

VRP

ASPSP

Sep-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26188

v319_KI8

Open

Clarification on Additional control parameters-

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/profiles/vrp-profile.html#payment-restrictions

Changes removed are ~~struck out~~ and added are in blue

Payment Restrictions

The standard provides a set of control parameters that may be specified as part of the VRP Consent. These control parameters set limits for the payment orders that can be created by the TPP for a given VRP.

In addition to the control parameters defined in this standard ASPSPs may implement additional control parameters, limits and restrictions for non-sweeping VRPs.

These restrictions should be documented on ASPSP's developer portal

VRP

ASPSP

Oct-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26664

v319_KI9

Open

Change to remove CreditorAgent as it is not applicable to domestic payments and move PostalAddress block under OBDomesticVRPInstruction block as CreditorPostalAddress

2. Change to remove CreditorAgent from OBDomesticVRPInitiation as it is not applicable to domestic payments and move PostalAddress block under OBDomesticVRPInitiation block as CreditorPostalAddress

Update OBDomesticVRPInstruction to remove CreditorAgent block and move PostalAddress under OBDomesticVRPInstruction as CreditorPostalAddress
Update OBDomesticVRPInitiation to remove CreditorAgent block and move PostalAddress under OBDomesticVRPInitiation as CreditorPostalAddress

CreditorPostalAddress (0..1)

0..1

CreditorPostalAddress

Information that locates and identifies a specific address, as defined by postal services.

OBPostalAddress6

Change to UML
Change to Data dictionary table
Change to Swagger

VRP

ASPSP

Oct-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26669

v319_KI10

Open

Change to make Reference field optional in CoF check as it is optional in the VRP consent request

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/resources-and-data-models/vrp/domestic-vrp-consents.html#obvrpfundsconfirmationrequest

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/resources-and-data-models/vrp/domestic-vrp-consents.html#obvrpfundsconfirmationresponse

Change 1) Update

OBVRPFundsConfirmationRequest to make Reference field optional

OBVRPFundsConfirmationResponse to make Reference field optional

Change to UML
Change to Data dictionary table
Change to Swagger

Change 2) Update

OBVRPFundsConfirmationRequest to make Data block mandatory

OBVRPFundsConfirmationResponse to make Data block mandatory

Change to UML
Change to Swagger

VRP

ASPSP

Oct-2021

&

Nov 2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-27535

v319_KI11

Open

Amount object in examples to be corrected

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/resources-and-data-models/vrp/domestic-vrp-consents.html#examples-of-periodic-limits

Fix to examples -Example 1, 2,3,4 to flatten Amount and currency

VRP

ASPSP

Nov 2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-27653

v319_KI12

Open

Update scope of event notification to include payments

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/profiles/aggregated-polling-api-profile.html#scopes

Image Added

Fix to include Payments in the scope of event notification

VRP

ASPSP

Nov 2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-27921

Expand

title	Read/Write API v3.1.8

Status

Details

Impact/Mitigation

Area

Reporter

Reported

Service Desk Ticket Number

(OBIE access only)

Work Item Ticket Number

(OBIE Access Only)

Fixed

For VRPs, the section on Events (https://openbankinguk.github.io/read-write-api-site3/v3.1.8/profiles/vrp-profile.html#event-notifications) states that

In any such situation where an account linked to avrp-consentcan no longer be used, temporarily or permanently, to make payments, the ASPSP must inform the TPP using events.

The specification should be modified to read:

In any such situation where an account linked to a vrp-consent can no longer be used, temporarily or permanently, to make payments, the ASPSP should inform the TPP using events.

VRP

ASPSP

Apr-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25276

Reported in TDA

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	CDRW-3937

Fixed

In the Domestic VRPs - v3.1.8 spec data model it says:

Reference (0..1)
RemittanceInformation. Reference
Unique reference, as assigned by the creditor, to unambiguously refer to the payment transaction. The PISP must populate this with the same value as specified in the ControlParameters.Reference field of the consent.

The field does not exist

Spec should be updated to read "The PISP must populate this with the same value as specified in the `Data.Initiation.RemittanceInformation.Reference`"

VRP

ASPSP

May-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-23244

Fixed

Rejected code is not listed in https://openbankinguk.github.io/read-write-api-site3/v3.1.8/profiles/account-and-transaction-api-profile.html#static-enumerations for rejected

Code to be added

AIS

ASPSP

May-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-23512

Fixed

The action to be taken for Access Revocation (See https://openbankinguk.github.io/read-write-api-site3/v3.1.8/profiles/account-and-transaction-api-profile.html#access-revocation) is not clear due to the use of the term "may"

Change the statement:

A PSU may revoke AISP's access directly with the ASPSP, via the access dashboard. In such a situation:
The ASPSPs may revoke/expire the access token provided to the AISP.

to read:

...
The ASPSP must take the necessary action to revoke access e.g. by revoking/expiring the access token provided to the AISP.

AIS

ASPSP

June-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-23823

Fixed

The response object specified for the payment details endpoint is incorrect

Change the Endpoints table Response Object entry for payment-details

OBDomesticVRPRequestDetailResponse

to read

OBDomesticVRPDetails

VRP

ASPSP

July-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-24689

Fixed

Errata fixes to VRP example 2 and example 3

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#examples-of-periodic-limits

Change Example 2 from

to

Change Example 3 from

to

VRP

TPP

July-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-24907

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	CDRW-4036

Fixed

Errata fix to update resources and data models page for VRP - https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/

Update VRP Resources and Data Models page to include all VRP endpoints including resource compatibility with version 3.1.8 and 3.1.9

VRP

TPP

Aug-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25460

Jira Legacy

server	System JIRA
columns	key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-26172

Fixed

Errata fix to update enumerations for VRP - https://openbankinguk.github.io/read-write-api-site3/v3.1.8/references/namespaced-enumerations.html

VRP

TPP

ASPSP

Aug-2021

Jul-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25446

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25088

Fixed

Errata fix to update State model table to remove "Expired" status

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#state-model---vrp-consents

VRP

ASPSP

Aug-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25600

Fixed

Errata fix to update permissions in Transactions API

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/aisp/Transactions.html#permission-codes

Update Permissions section to include ReadTransactionsCredits and ReadTransactionsDebits

AISP

TPP

Aug-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25715

Fixed

Clarification on

PeriodType=Fortnight
PeriodAlignment=Calendar
ValidToDateTime

https://openbankinguk.github.io/read-write-api-site3/v3.1.8/resources-and-data-models/vrp/domestic-vrp-consents.html#obdomesticvrpcontrolparameters

Clarification on the below combination -

PeriodType=Fortnight
PeriodAlignment=Calendar

To refrain from implementing this combination, as the ISO calendar does not support or provide any guidance on when a fortnight should start.

Clarification on time part in the consent -

ValidFromDateTime
ValidToDateTime

The consent period starts and ends at midnight - effectively the time element of the date should be disregarded in computing the date range and pro-rating.

VRP

ASPSP

Aug-2021

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-25599

...

Expand

title	Dynamic Client Registration v3.2

Status

Ref

Type

Issue

Details

Impact/Mitigation

Open

Minor Bug

The regex pattern for uuidv4 specified for the jti field is incorrect in the specification.

As per the UUID specification (https://tools.ietf.org/html/rfc4122#section-3):

1 The hexadecimal values "a" through "f" are output as lower case characters and are case insensitive on input.

This has been fixed in the swagger file for v3.2.

The specification will be corrected in the next version.

...

Expand

title	Read/Write API Ver 3.0

Status

Ref

Type

Issue

Details

Impact/Mitigation

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-4642

Errata

R/W Spec Parent Page mentions application/json as the only permitted value for Content-Type

The swagger definitions for each of the APIs is correct.

The statement will be corrected in v3.1 to be accurate.

Fixed

Minor Bug

v3.0-rc3 Swagger has incorrect length for Path field in the OBError1 object.

This should be Max500Text instead of Max40Text.

To be fixed in v3.0-rc4 of the Swagger spec.

Fixed

Minor Bug

The status model for the Domestic and International Payments (Immediate) does not contain a transition from AcceptedSettlementInProcess that handles error cases.

A transition from AcceptedSettlementInProcess to Rejected should be included on the status model diagram. This would bring it back in line with the current status model in v1.1

Amend the specification in v3.1 to include a transition from AcceptedSettlementInProcess to Rejected.

Fixed

Errata

v3 RC3 International Standing Orders page - Reusable Class UML Diagram is incorrect.

v3 RC3 International Standing Orders page.

The Reusable Class describes OBInternationalStandingOrder1 but the UML diagram represents OBWriteInternationalStandingOrder1 (the consent request object).

UML DIagram for OBInternationalStandingOrder1 isn't provided in the specification.

Amend the specification in V3.1 to include the correct UML Diagram.

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-4752

Minor Bug

OBActiveCurrencyAndAmount_SimpleType in the specifications is missing the Pattern:
'^\d{1,13}\.\d{1,5}$'.

Account, Payment and COF Data Dictionary in the specification does not have the pattern for OBActiveCurrencyAndAmount_SimpleType defined.

The swagger definition has the correct regex pattern.

For Consistency of the specs with swagger, it will be fixed in V3.1 specification.

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-4787

Minor Bug

"Meta" and "Links" tag in response are shown in examples but not in swagger.

To be fixed in v3.0-rc4 of the Swagger spec.

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-4786

Minor Bug

Funds Confirmation Usage Examples missing meta element

Meta is a mandatory data element in the JSON response, but is missing in the example.

Specification and Swagger spec are accurate.

Example will be fixed in V3.1 specification.

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-4785

Errata

Typo on Products/PCA Data Model and Products/BCA Data Model pages

Fix gramattical error:

FeaturesAndBenefits: Further analysis is required to check whether feature and benefits sections is needed ~~are not~~.

Changes required in PCA Product Data Model & BCA Product Data Model.

Will be fixed in V3.1 specification.

Fixed

Raised by OB R/W API Team

Minor Bug

Incorrect type (length) for DomesticStandingOrderId and InternationalStandingOrderId.

Payment Order Ids for Standing Orders (DomesticStandingOrderId and InternationalStandingOrderId) is of the type Max128Text, while other Payment Order Ids are of type Max40Text.

The Ids should be standardised to Max40Text for consistenc

This will be fixed in v3.0-rc4 of the Swagger spec.

The specification will be updated in v3.1

Fixed

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-2303

Minor Bug

V3 Specification specifies that Error Codes in Authorisation flow must be aligned to OAuth Error codes.

Section 3.6 of the V3 RC3 specification incorrectly specifies following:

ASPSPs must respond with error response in the OAuth/OIDC flow with mandatory alignment of error codes to those specified in RFC 6749 Section 4.1.2.1

However, ASPSPs may extend the error response codes to include OIDC error responses as well.

The sentence should read:

It must be changed to the following, to include a reference to OIDC Error Codes:

ASPSPs must respond with error response in the Authorisation flow with mandatory alignment of error codes to those specified in Section 3.1.2.6 Authentication Error Response of OIDC Core specification.

This will be updated in v3.1

Fixed

Raised by OB R/W API Team

Minor Bug

Details for PUT operations are not provided in Request Headers and HTTP Status codes sections.

The R/W Ver 3.0 specifications introduced a PUT operation for ASPSP Event Notification specification.

The Request Headers and HTTP Status Codes for PUT operations should be explicity defined.

The Request Headers for PUT operations are the same as those for POST operations.

The HTTP Codes for PUT operations are the same as those for DELETE operations.

The tables will be updated in v3.1 to reflect the above.

Fixed

Raised by OB R/W API Team

Errata

'Process for verifying a signature' mislabels Step 2 as Step 1.

It will be fixed in V3.1 specification.

Fixed

Raised by OB R/W API Team

Minor Bug

In The 'Steps' section on the Payments specification, the description for Step 4 should be generalised for redirect as well as decoupled journeys

It should be made clear that step 4 occurs when authorisation is complete. This would apply in both the redirect and decoupled flows.

It will be fixed in V3.1 specification.

Fixed CDRW-2373 Minor Bug Incorrect Usage Examples Self Links in Usage Examples don’t Contain Namespace It will be fixed in V3.1 specification.

Fixed CDRW-2372 Minor Bug Incorrect Usage Examples Missing idempotency key on Standing Order Examples It will be fixed in V3.1 specification.

Fixed CDRW-2583 Minor Bug Incorrect Usage Examples Incorrect Usage Example for Bulk Transactions It will be fixed in V3.1 specification.

Fixed CDRW-2408 Errata Swagger files - ProductType field missing The ProductType field was inadvertently left out of the swagger files for the product end-points ProductType re-introduced. Will be fixed. v3.1

Fixed CDRW-2423 Errata Incorrect field size for PurposeCode The PurposeCode field for international payments is of the incorrect length (35 chars rather than the ISO enum size of 4 chars) It will be fixed in V3.1 specification.

Fixed CDRW-2409 Minor Bug Grammar Fix Fixed multiple instances of poor grammar and lapses of typographical diligence. It will fix be in v3.1 specification.

Fixed CDRW-2582 Errata Transaction permissions not specified Transaction Permissions Errata (Debtor/Creditor Agent Inconsistency) It will be fixed in V3.1 specification.

Fixed CDRW-2585 Clarification Common base-url for all resources State that the base-url must be the same for all resources It will be fixed in V3.1 specification.

Fixed CDRW-2584 Clarification Improve definition of CurrencyOfTransfer It will be fixed in V3.1 specification.

Fixed CDRW-2671 Errata Incorrect data type for iat and toe claims The iat and toe claims are specified as strings.These should be numeric (in keeping with the defintion of iat in the JWT RFC) It will be fixed in V3.1 specification.

Open

Jira Legacy

server	System JIRA
serverId	ea8dba46-d77f-39e1-b936-d18d8cee7939
key	OBSD-15311

Errata

Incorrect multiplicity for OBRisk1/DeliveryAddress/CountrySubDivision

The occurence is specified as 0..2 instead of 0..1

This will be fixed in v3.1.6

...

Expand

title	Read/Write API v2.0

Read/Write API v2.0

References:

Read/Write Data API Specification - v2.0.0

This version of the Read/Write API Specification will be supported by all CMA9 ASPSPs from 7 September 2018 for CMA Order in-scope accounts. The following table details known issues with this version of the specification.

Status	Ref	Type	Issue	Details	Impact/Mitigation
Closed	OBSD-4103	Errata	OB Statements - Endpoint section specifies Filtering for wrong endpoints	Filtering word should be removed from the Endpoints table for: GET /accounts/{AccountId}/statements/{StatementId} (Row#2) GET /accounts/{AccountId}/statements/{StatementId}/transactions (Row#4)	Non-breaking change. The Swagger is correct for this issue, but the documentation has specified filtering on endpoints that should not apply filtering. Will be fixed in v2.1 Has been fixed in v3.0
Closed	TBC	Bug	OB Statements - filters missing in Swagger spec.	Filtering on statement dates is in the specification for: GET /accounts/{AccountId}/statements GET /statements However - these are missing from the Swagger spec.	Non-breaking change. TPPs may expect the ability to filter on dates to identify statements. However, this functionality is missing from the Swagger spec. Will be fixed in v2.1 Has been fixed in v3.0
Closed	TBC	Errata	Usage Guidance Errata	For Party Endpoint: Usage Examples for Account Owner and Authorised User - have been documented incorrectly.	Errata. Non-breaking change. Will be fixed in v2.1. Has been fixed in v3.0
Closed	TBC	Bug	Transactions Object Bug	Transactions object using the wrong currency exchange object. In v3, we have fixed this with the CurrencyExchange object replacing the EquivalentAmount object to describe currency exchange.	Breaking change to replace the CurrencyExchange object. ASPSPs cannot represent currency exchange information until this fix is applied. Will be fixed in v2.1 Has been fixed in v3.0
Closed	TBC	Errata	Address Code-LIst Errata	Updated ISO 20022 OBAddressTypeCode code from "DeliverTo" to "DeliveryTo"	Errata. Non-breaking change. Will be fixed in v2.1 Has been fixed in v3.0
Closed	TBC	Requested enhancements	Requested Enumerations for Use Cases	Enumeration definitions updated for: Balance/Type - InterimCleared, OpeningCleared, ClosingCleared StatementAmount/Type - PendingTransactionsBalance StatementFee/Type - ForeignCashTransaction CardInstrument/AuthorisationType - ConsumerDevice	Will not be included in v2.1 as fix. Has been fixed in v3.0
Closed	OBSD-3833	Bug	/party endpoint AddressLine - mismatch between spec and Swagger	AddressLine in Swagger is specified as a string. However - in the data dictionary is 0..5	Non-breaking change. Will be fixed in v2.1 Has been fixed in v3.0

...

Versions Compared

Old Version 71

New Version 72

Key

`OBDomesticVRPControlParameters`

`OBDomesticVRPConsentRequest`

`OBDomesticVRPConsentResponse`

Payment Restrictions

Read/Write API v2.0

Page Comparison

Versions Compared

Old Version 71

New Version 72

Key

OBDomesticVRPControlParameters

OBDomesticVRPConsentRequest

OBDomesticVRPConsentResponse

Payment Restrictions

Read/Write API v2.0

`OBDomesticVRPControlParameters`

`OBDomesticVRPConsentRequest`

`OBDomesticVRPConsentResponse`