The OBIE conformance team has analysed over 400 500 ASPSP/TPP tickets (since April 2020) to identify areas where additional tests would improve the quality of certified ASPSP implementations and speed up the resolution of issues between ASPSPs and TPPs.
Please see below a summary of the additional tests the conformance team will be adding over the next four sprintsall the releases. This is OBIE’s plan for delivering this additional functionality or fixing any issues and is not a firm commitment by OBIE. Please watch this page and/or the release notes for each version of the tool for further updates.
...
Releases
Release v1.6.0 (16th September 2020): https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.0.md
Release v1.6.1 (23rd September 2020): https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.1.md
Release v1.6.2 (9th October 2020): https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.2.md
Release v1.6.3 (27th October 2020) https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.3.md
Release v1.6.4 (8th December 2020) https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.4.md
Release v1.6.5 (16th December 2020) https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.5.md
Release v1.6.6 (21st January 2021) https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.6.md
Release v1.6.7 (24th February 2021) https://bitbucket.org/openbankingteam/conformance-suite/src/v1.6.7/docs/releases/v1.6.7.md
Release v1.6.8 (14th June 2021) https://bitbucket.org/openbankingteam/conformance-suite/src/develop/docs/releases/v1.6.8.md
Release v1.76.0 9 (July 24th August 2021) v3.1.8 v1.6.9.md
Release v1.76.1 10 (October 2021) v3.1.9
...
Type
...
Version
...
Resource
...
Comment
...
Release
...
Errors
...
>=3.1.5
...
Payments
...
Add a test that checks the correct UK.OBIE.Signature. The missing message is returned when a payment signature is missing.
16th November 2021) v1.6.
...
Errors
...
>=3.1.5
...
Payments
...
{payment-order-consent} and {payment-order} resource mismatch. For example, if an element in the resource’s Initiation or Risk section does not match the consent section.
...
v1.6.3
...
Errors
...
>=3.1.5
...
Payments
...
{payment-order} consent / resource received after CutOffDateTime
...
v1.6.3
...
Errors
...
>=3.1.5
...
CBPII
...
A Duplicate reference has been used for a CBPII confirmation of funds request
...
v1.6.3
...
Errors
...
>=3.1.5
...
Accounts
...
The BookingDateTime field returned by the Transactions endpoint doesn't include any time component
...
v1.6.3
...
Discovery
...
>=3.1.5
...
Discovery
...
Add check for well-known "authorisation" URL
...
Payload
...
>=3.1.5
...
Accounts
...
Add test to check correct balance types returned in account listings
...
Payload
...
>=3.1.5
...
Accounts
...
Add test to check AIS pagination if multiple pages are returned.
...
Payload
...
>=3.1.5
...
Payments
...
Add test PIS pagination check if multiple pages are returned
...
Dates
...
>=3.1.5
...
Accounts
...
Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05-07:00
...
v1.6.0
...
Dates
...
>=3.1.5
...
Accounts
...
Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05Z07:00
...
v1.6.0
...
Dates
...
>=3.1.5
...
Accounts
...
Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05-0700
...
v1.6.0
...
Dates
...
>=3.1.5
...
Accounts
...
Query parameters (fromBookingTime & toBookingTime) are rejected in ISO8601 format 2006-01-02T15:04:05.999Z07:00
...
v1.6.0
...
Dates
...
>=3.1.5
...
Payments
...
Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T15:04:05-07:00)
...
v1.6.0
...
Dates
...
>=3.1.5
...
Payments
...
Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T15:04:05.999Z)
...
v1.6.0
...
Dates
...
>=3.1.5
...
Payments
...
Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T15:04:05-0700)
...
v1.6.0
...
Dates
...
>=3.1.5
...
Payments
...
Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T150405-07)
...
v1.6.0
...
Dates
...
>=3.1.5
...
CBPII
...
Creates Funds Confirmation Consent with expirationDateTime formatted as '2006-01-02T15:04:05.999Z
...
v1.6.1
...
Dates
...
>=3.1.5
...
CBPII
...
Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05.999-07:00'
...
v1.6.1
...
Dates
...
>=3.1.5
...
CBPII
...
Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05Z'
...
v1.6.1
...
Dates
...
>=3.1.5
...
CBPII
...
Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05-07:00'
...
v1.6.1
...
Refunds
...
>=3.1.6
...
Payments
...
TBD - Additional 3.1.6 Refund tests (max 4 tests)
...
General
...
>=3.1.6
...
General
...
Additional 3.1.6 specific tests - that target differences between 3.1.5 and 3.1.6 (max 4 tests)
...
Release v1.6.11 (6th December 2021) v1.6.11.md
Release v1.6.12 (21st February 2022) v1.6.12.md
Release v1.7.0 (14th June 2022) v1.7.0.md
Release v1.7.1 (October 2021) TBC
Release notes: here
What is changed in each release: here