OBIE Functional Conformance Tool Roadmap

The OBIE conformance team has analysed over 400 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 sprints. This is OBIE’s plan for delivering this additional functionality and 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

Type

Version

Resource

Comment

Release

Type

Version

Resource

Comment

Release

1

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.

v1.6.2

2

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

3

Errors

>=3.1.5

Payments

{payment-order} consent / resource received after CutOffDateTime

v1.6.3

4

Errors

>=3.1.5

CBPII

A Duplicate reference has been used for a CBPII confirmation of funds request

v1.6.3

5

Errors

>=3.1.5

Accounts

The BookingDateTime field returned by the Transactions endpoint doesn't include any time component

v1.6.3

6

Discovery

>=3.1.5

Discovery

Add check for well-known "authorisation" URL

 

7

Payload

>=3.1.5

Accounts

Add test to check correct balance types returned in account listings

 

8

Payload

>=3.1.5

Accounts

Add test to check AIS pagination if multiple pages are returned.

 

9

Payload

>=3.1.5

Payments

Add test PIS pagination check if multiple pages are returned

 

10

Dates

>=3.1.5

Accounts

Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05-07:00

v1.6.0

11

Dates

>=3.1.5

Accounts

Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05Z07:00

v1.6.0

12

Dates

>=3.1.5

Accounts

Query parameters (fromBookingTime & toBookingTime) are accepted in ISO8601 format 2006-01-02T15:04:05-0700

v1.6.0

13

Dates

>=3.1.5

Accounts

Query parameters (fromBookingTime & toBookingTime) are rejected in ISO8601 format 2006-01-02T15:04:05.999Z07:00

v1.6.0

14

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

15

Dates

>=3.1.5

Payments

Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T15:04:05.999Z)

v1.6.0

16

Dates

>=3.1.5

Payments

Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T15:04:05-0700)

v1.6.0

17

Dates

>=3.1.5

Payments

Domestic Scheduled Payment consents accepts 'RequestedExecutionDateTime' formatted as ISO8601 datetime (2006-01-02T150405-07)

v1.6.0

18

Dates

>=3.1.5

CBPII

Creates Funds Confirmation Consent with expirationDateTime formatted as '2006-01-02T15:04:05.999Z

v1.6.1

19

Dates

>=3.1.5

CBPII

Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05.999-07:00'

v1.6.1

20

Dates

>=3.1.5

CBPII

Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05Z'

v1.6.1

21

Dates

>=3.1.5

CBPII

Creates Funds Confirmation Consent with expirationDate formatted as '2006-01-02T15:04:05-07:00'

v1.6.1

22

Refunds

>=3.1.6

Payments

TBD - Additional 3.1.6 Refund tests (max 4 tests)

 

23

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)

v1.6.3