Status | Ref | Type | Issue | Details | Impact/Mitigation |
---|
Open | OD-803 | Enhancement | Products: Need to split ServicingAccessChannel by individual services. | A request was made that AccessChannel be split in to:- I) SalesAccessChannel - channel(s) by which a product may be sold to a customer ii) ServicingAccessChannel - channel(s) by which an existing customer may obtain 1 or more services for a particular product. | Minor impact. Will be updated in v2.2. |
Closed | OD-826 | Minor bug | Regular Expressions (Regex), that are required to constrain values entered in to fields to a certain pattern, should be in the data dictionary as well as the Swagger. | Regex in Swagger is hard coded and there are a number of discrepancies (amount and rate fields) where these are limited to 2DP. They should be 3DP. | ASPSPs will only be able to specify amount and rates to 2 decimal places. Has been fixed in v2.2.0-rc1. |
Closed | OD-845 | Minor bug | OverdraftFeeApplicableRange section is a modelling error and should be removed from the PCA design. | OverdraftFeeApplicableRange doesn't appear in the Design at all but does appear in the swagger. | This is an optional field, so no impact. Has been fixed in v2.2.0-rc1. |
Open | OD-855 | Enhancement | PCA, BCA: Minimum Arranged Overdraft Amount. | Some banking products require an account holder to take an Arranged Overdraft of at least £x, or else a bank will not process an Arranged Overdraft request. This is potentially useful information. If, for example, an accountholder has an Arranged Overdraft of £100 currently, and a banking product that they're interested in taking requires a minimum Arranged Overdraft of £200, then they would not be able to switch their current account. | Minor impact. Will be updated in v2.2. |
Closed | OD-856 | Minor bug | All Notes fields should have a consistent cardinality 0..* | In some places cardinality is 0..1 and these should all be 0..n to allow multiple notes. | ASPSPs will have to combine notes into one field rather than separate fields. Has been fixed in v2.2.0-rc1 |
Closed | OD-857 | Minor bug | The Max256Type datatype was not correctly generated in the Swagger files. | Swagger is a string but GFEG defines 256 characters. Swagger should be changes to 256. | No impact. Has been fixed in v2.2.0-rc1 |
Closed | OD-883 | Minor bug | 3 missing fee category codes. | FeeCategoryType1Code list is missing the following fields 'Auto', 'FX' , 'Investigation' | ASPSP can select other and chose one of these for now. No impact. Has been fixed in v2.2.0-rc1 |
Closed | OD-884 | Bug | Fix the way that mandatory field restrictions are generated by the Swagger generation script. | Swagger contains required tag in the wrong place, which makes the Java Json Validator https://www.jsonschemavalidator.net/ fail. | ASPSPs cannot validate using Java Json Validator, but will have to use OB Json Validation tool instead. Has been fixed in v2.2.0-rc1 |
Open | OD-973 | Minor bug | PCA, BCA, SMELoan and CCC amend spelling mistake in the codelist | There are a number of spelling mistakes in code lists (e.g. CoreProduct/ LoanApplicationFeeChargeType enumeration "NoLoanApplicationFee" is incorrectly spelt "NoLoanApplicatioFee" in swagger). | TPPs may see some values with spelling mistakes. Will be fixed in v2.2. |
Open | OD-978 | Enhancement | Enhance the Fee and charges Cap so that it can be linked with the any Fee Type. | Where there are tiered fees and charges, the current design only allows the ASPSP to use one cap across the tiers. ../OtherFeesAndCharges/FeeChargeCap unable to explicitly link to a ../OtherFeesAndCharges/FeeCharge Detail
| ASPSPs can use notes field to specify complex caps. This item requires a decision as to whether it may be included in a future release. |
Open | OD-979 | Minor bug | Make the identification field optional for all section except Product ID | Some ID fields in PCA (e.g. <Product>MarketingState/Identification) are mandatory and should be optional to be consistent with BCA, SMELoans, CCC.
| ASPSPs will have to populate with some value (e.g. 0). Will be fixed in v2.2. |
Open | OD-980 | Minor bug | Restriction on regular expression for Residency Included field should be removed. | For specifying the countries for which the PCA products are available/restricted to use the field ResidencyIncluded, current specification specifies it's DataType as OB_CodeMnemonic with a fixed length of 4. However, to correctly specify data values in this field, the correct DataType restriction should allow length of up to 4 and NOT fixed at 4. e.g. The value on this is expected to be 'UK' or 'EU', which would error out with the specification supplied. | ASPSPs will have to pad out the field (e.g. with spaces). Will be fixed in v2.2. |
Open | OD-981 | Minor bug | Check the possibility of changing the optional or mandatory fields as an array rather than objects. | For any fields where cardinality is 0..1, the swagger defines this as an object. For 1..1 and 1..n the swagged defines this as an array. Ideally these should all be arrays. | No impact. Will be fixed in v2.2. |
Open | OD-986 | Minor bug | Missing 'Other' code from Fee Type under overdraft fee charge details and cap section. | In PCA and BCA schema the FeeType Enum in the OverDraftFeesCharges of overdraftTierSet and OverDraftTierBand are missing the "Other" value in both OverdraftFeeChargeCap and OverdraftFeeChargeDetail. | ASPSPs can only specify fee types using the standard code list. Minor impact, as code lists are fairly comprehensive. Will be fixed in v2.2. |
Open | OD-997 | Enhancement | Add "Academic Term" in period code list. | The current code list options for: OpenBankingPCA/Brand/PCA/PCAMarketingState/StateTenurePeriod should be extended to include: AcademicTerm. | Some ASPSPs may have to use Monthly, Quarterly, Yearly for now. Minor impact. Will be updated in v2.2. |
Open | OD-1010 | Minor bug | Remove the example reference url link from the base of the API URI | Current URLs for V1.2 and the Swagger which implies a different configuration. Current example: https://openapi.nationwide.co.uk/open-banking/v1.2/atms Our assumption is we would just change the version number however Swagger suggests a new part of the URL is being added: “/reference-implementation/open-banking/v2.1” | ASPSPs should remove/replace 'reference-implementation' with their own URI. Minor impact. Will be fixed in 2.2. |