Versions Compared

Old Version 85

changes.mady.by.user Glorria D

Saved on

compared with

New Version 86

changes.mady.by.user Glorria D

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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
titleRead/Write API v3.1.10


Ref_No
Status
Details
Impact/Mitigation
Fix in VersionAreaReporterReported

Service Desk Ticket Number

(OBIE access only)

Work Item Ticket Number

(OBIE Access Only)

v3110_KI1Open
  1. VRPType is missing in OBDomesticVRPRequest

2. Usage examples are not showing VRPType selected

  1. Errata fix to  OBDomesticVRPRequest - UML Diagram and Table to add field VRPType (1..1)
    https://openbankinguk.github.io/read-write-api-site3/v3.1.10/resources-and-data-models/vrp/domestic-vrps.html#obdomesticvrprequest
  2. Errata fix to usage examples to add VRPType in Data block
    https://openbankinguk.github.io/read-write-api-site3/v3.1.10/references/usage-examples/vrp-usage-examples.html#post-domestic-vrps



Specs, Swagger, FCS in v3.1.11VRPOBIE Internal reviewMay-2022N/A
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4134
v3110_KI2Open

Errata fix to change VRPType from string to array in usage examples for domestic-vrp-consents

Errata fix to usage examples 
https://openbankinguk.github.io/read-write-api-site3/v3.1.10/references/usage-examples/vrp-usage-examples.html#post-domestic-vrp-consents

Specs, Swagger, FCS in v3.1.11VRPASPSPMay-2022Case 00022980
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4133
v3110_KI3Open

Errata fix where the field is incorrectly named as BeneficiaryPaymentDetailsPrepopulatedIndicator

 

Errata fix to change field BeneficiaryPaymentDetailsPrepopulatedIndicator to BeneficiaryPrepopulatedIndicator 

https://openbankinguk.github.io/read-write-api-site3/v3.1.10/profiles/read-write-data-api-profile.html#json-error-response


Specs in v3.1.11

Swagger, FCS-No change

TRIASPSPApr-2022Case - 00022753
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4152
v3110_KI4Open

Errata fix where the field is incorrectly named as ContractPresentInidicator

Errata fix to change field ContractPresentInidicator to ContractPresentIndicator

https://openbankinguk.github.io/read-write-api-site3/v3.1.10/profiles/payment-initiation-api-profile.html#obrisk1

Specs, Swagger, FCS in v3.1.11TRIASPSPJune 2022

Case-00024791


Case-00025004

Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4154
v3110_KI5Open

Errata fix to regular expression pattern in the specs. One example below

https://openbankinguk.github.io/read-write-api-site3/v3.1.10/resources-and-data-models/aisp/Balances.html#data-dictionary

Errata fix to change pattern from 

^\d{1,13}$\|^\d{1,13}\.\d{1,5}$ to ^\d{1,13}$|^\d{1,13}\.\d{1,5}$

for all of the below APIs

Balances

  • OBReadBalance1/Data/Balance/Amount/Amount
  • OBReadBalance1/Data/Balance/CreditLine/Amount/Amount

Transactions

  • OBReadTransaction6/Data/Transaction/Amount/Amount
  • OBReadTransaction6/Data/Transaction/ChargeAmount/Amount
  • OBReadTransaction6/Data/Transaction/CurrencyExchange/InstructedAmount/Amount
  • OBReadTransaction6/Data/Transaction/Balance/Amount/Amount

Direct-debits

  • OBReadDirectDebit2/Data/DirectDebit/PreviousPaymentAmount/Amount

https://openbankinguk.github.io/read-write-api-site3/v3.1.10/resources-and-data-models/aisp/standing-orders.html

  • OBReadStandingOrder6/Data/StandingOrder/FirstPaymentAmount/Amount
  • OBReadStandingOrder6/Data/StandingOrder/NextPaymentAmount/Amount
  • OBReadStandingOrder6/Data/StandingOrder/LastPaymentAmount/Amount
  • OBReadStandingOrder6/Data/StandingOrder/FinalPaymentAmount/Amount

Scheduled-payments

  • OBReadScheduledPayment3/Data/ScheduledPayment/InstructedAmount/Amount

Statements

  • OBReadStatement2/Data/Statement/StatementBenefit/Amount/Amount
  • OBReadStatement2/Data/Statement/StatementFee/Amount/Amount
  • OBReadStatement2/Data/Statement/StatementInterest/Amount/Amount
  • OBReadStatement2/Data/Statement/StatementAmount/Amount/Amount

Specs in v3.1.11

SwaggerFunds Confirmation

  • OBFundsConfirmation1/Data/InstructedAmount/Amount
  • OBFundsConfirmationResponse1/Data/InstructedAmount/Amount

Specs in v3.1.11

Swagger, FCS-No change

AISASPSP

July 2022



Oct 2022

Case-00025529

&

OB Internal review

Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4155
v3110_KI6Open

Add missing 409 in payload containing "UK.OBIE.Rules.ResourceAlreadyExists" in VRP


Swagger, FCS in v3.1.10

Specs-No change

VRPTPPJul-22Case 00025699CDRW-4156
v3110_KI7Open

Update usage examples of "GET /accounts/{AccountId}/balances" to fit OBReadBalance1 object definition.

Errata fix to usage examples → 

Specs in v3.1.11

Swagger, FCS-No change

AISASPSPJul-22

CDRW-4158


v3110_KI8Open

Add missing OBVRPStatusReasonCode enumeration under 

https://openbankinguk.github.io/read-write-api-site3/v3.1.10/references/namespaced-enumerations.html#variable-recurring-payments-namespaced-enumerations

Add OBVRPStatusReasonCode 

  • UK.OBIE.ExemptionNotApplied
  • UK.OBIE.OtherReason

Note: ASPSPs may define enumerations that are more appropriate and use the OtherReason only in scenarios where the actual reason cannot be determined or disclosed.

Specs in v3.1.11

Swagger, FCS-No change

VRPTPPSep-22Case-27439CDRW-4165
v3110_KI9Open

Update FCS test case: OB-301-VRP-100650 - Check VRP Funds Confirmation (POST /domestic-vrp-consents/{ConsentId}/funds-confirmation)

Respond with status code 200 instead of 201.

To align to PISP CoF

Response with status code 200 

FCS(v1.7.1), Swagger in v3.1.10 onwards

Specs- No change

VRPASPSPSep-22Case 00027526CDRW-4164
v3110_KI10OpenUpdate FCS tool
  1. Add missing test cases for GET /accounts/{AccountId}/parties
  2. Update test cases GET "/party" - a condition from "optional" to "conditional" 
  3. Add test case for Idempotency
  4. Add test case for validation - not specified FinalPaymentAmount (Standing orders – Domestic & International both)

FCS in v1.7.2

Specs, Swagger- No change

AISPASPSPNov-22

REFAPP-1306

REFAPP-1310

REFAPP-1307

REFAPP-1309



Expand
titleDynamic Client Registration v3.3


Status
Details
Impact/Mitigation
AreaReporterReported

Service Desk Ticket Number

(OBIE access only)

Work Item Ticket Number

(OBIE Access Only)

Open

The enumeration for application_type has incorrect values

This will be fixed in a forthcoming release.

GeneralTPPAug-2020
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-17624
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-3518
Open

The endpoint should be GET not POST

https://openbankinguk.github.io/dcr-docs-pub/v3.3/dynamic-client-registration.html#endpoints

"POST /register/{ClientId}" should be "GET /register/{ClientId}"

This will be fixed in a forthcoming release.

GeneralTPPAug-2020
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-17490
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-3519


...

Expand
titleRead/Write API v3.1.9


Ref_No
Status
Details
Impact/Mitigation
AreaReporterReported

Service Desk Ticket Number

(OBIE access only)

Work Item Ticket Number

(OBIE Access Only)

v319_KI1Closed

For AISP: OBReadConsent1:

UML diagrams are incorrectly showing the Permissions field as 0..1 in version 3.1.7 onwards

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


VRPASPSPOct-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26532

v319_KI2Closed

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

Following objects will be fixed

  1. 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

  1. Fix UML diagram to reflect  Instructed amount field as 1..1 in below objects

    1. OBDomesticVRPInstruction

    2. OBDomesticVRPRequest

    3. OBDomesticVRPResponse

  2. Update swagger


VRPASPSPSep-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26140

v319_KI3Closed

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

  1. Update state model diagram to remove the status.
  2. 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

VRPASPSPSep-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26142

v319_KI4Closed

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_KI5Closed

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-access-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_KI5aClosed

Fix to enums for event notifications related to revocation

https://openbankinguk.github.io/read-write-api-site3/v3.1.9/references/namespaced-enumerations.html#obeventtype1code

Introduce a new enum UK.OBIE.Consent-Access-Revoked for access revoked at ASPSP keeping UK.OBIE.Consent-Authorization-Revoked for backward compatibility

EventsOBIE Internal reviewFeb-2022
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4114
v319_KI6Closed

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.


VRPASPSPSep-2021

Jira Legacy
serverSystem JIRA
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26403



v319_KI7Closed

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

  1. 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

  2. Update swagger
VRPASPSPSep-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26188

v319_KI8Closed

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

VRPASPSPOct-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26664

v319_KI9Closed
  1. 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

  1. Update OBDomesticVRPInstruction to remove CreditorAgent block and move PostalAddress under OBDomesticVRPInstruction as CreditorPostalAddress
  2. 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
VRPASPSPOct-2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-26669

v319_KI10Closed

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

VRPASPSP

Oct-2021

& 

Nov 2021

Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-27535

v319_KI11Closed

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 currencyVRPASPSPNov 2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-27653

v319_KI12Closed

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

Fix to include Payments in the scope of event notificationVRPASPSPNov 2021
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-27921

v319_KI13Closed

Link to Event Notification is broken

Fix links in v319 and v318

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

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

GeneralOB InternalJan 2022

v319_KI14Closed

Errata fix to include this attribute for non-sweeping only and hence optional field for sweeping 

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

Add an array PSUInteractionTypes to enable the PISP to capture 'Customer not in an active session' and 'Customer in an active session' at the consent level.

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

Add PSUInteractionTypes to enable the PISP to specify the specific value from the PSUInteractionTypes defined at the consent level

Add missing attributes to capture PSUInteractionTypes as per VRP requirement

  • Change to UML

  • Change to Data dictionary table

  • Change to Swagger


//Consent
{ PSUInteractionTypes: ['InSession','OffSession'] }

//payment
{ PSUInteractionType: 'InSession' }

VRPASPSPJan 2022
Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-28494

v319_KI15ClosedChange resource group of VRP endpoints to existing PISP resource group 
  • Changes to the Open API specification for VRP (update server URI path)
  • Changes to the URLs in usage examples
  • Changes to Functional Conformance Suite (FCS)
  • Changes to Model Bank
VRPASPSPJan 2022

/wiki/spaces/WOR/pages/2302083154

Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyCDRW-4126


...

Expand
titleDynamic 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
titleRead/Write API Ver 3.0


Status
Ref
Type
Issue
Details
Impact/Mitigation
Fixed

Jira Legacy
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-4642

ErrataR/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.

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 BugThe 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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-4752
Minor BugOBActiveCurrencyAndAmount_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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-4786

Minor BugFunds Confirmation Usage Examples missing meta elementMeta 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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-4785

ErrataTypo 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.

FixedRaised by OB R/W API TeamMinor BugIncorrect 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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-2303
Minor BugV3 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

FixedRaised by OB R/W API TeamMinor BugDetails 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.

FixedRaised by OB R/W API TeamErrata'Process for verifying a signature' mislabels Step 2 as Step 1.

It will be fixed in V3.1 specification.

FixedRaised by OB R/W API TeamMinor BugIn 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.

FixedCDRW-2373Minor BugIncorrect Usage ExamplesSelf Links in Usage Examples don’t Contain NamespaceIt will be fixed in V3.1 specification.
FixedCDRW-2372Minor BugIncorrect Usage ExamplesMissing idempotency key on Standing Order ExamplesIt will be fixed in V3.1 specification.
FixedCDRW-2583Minor BugIncorrect Usage ExamplesIncorrect Usage Example for Bulk TransactionsIt will be fixed in V3.1 specification.
FixedCDRW-2408ErrataSwagger files  - ProductType field missingThe ProductType field was inadvertently left out of the swagger files for the product end-pointsProductType re-introduced. Will be fixed. v3.1
FixedCDRW-2423ErrataIncorrect field size for PurposeCodeThe 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.
FixedCDRW-2409Minor BugGrammar FixFixed multiple instances of poor grammar and lapses of typographical diligence.It will fix be in v3.1 specification.
FixedCDRW-2582ErrataTransaction permissions not specifiedTransaction Permissions Errata (Debtor/Creditor Agent Inconsistency)It will be fixed in V3.1 specification.
FixedCDRW-2585ClarificationCommon base-url for all resourcesState that the base-url must be the same for all resourcesIt will be fixed in V3.1 specification.
FixedCDRW-2584ClarificationImprove definition of CurrencyOfTransfer
It will be fixed in V3.1 specification.
FixedCDRW-2671ErrataIncorrect data type for iat and toe claimsThe 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
serverSystem JIRA
serverIdea8dba46-d77f-39e1-b936-d18d8cee7939
keyOBSD-15311
Errata

Incorrect multiplicity for OBRisk1/DeliveryAddress/CountrySubDivision

The occurence is specified as 0..2 instead of 0..1This will be fixed in v3.1.6


...

Expand
titleRead/Write API v2.0

Read/Write API v2.0

References:

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
ClosedOBSD-4103ErrataOB 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

ClosedTBCBugOB 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

ClosedTBCErrata

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

ClosedTBCBug

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

ClosedTBCErrata

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

ClosedTBCRequested 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

ClosedOBSD-3833Bug/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


...