Versions Compared

Old Version 13

changes.mady.by.user Gareth Turney

Saved on

compared with

New Version Current

changes.mady.by.user Gareth Turney

Saved on

Key

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

...

RefAreaFieldAvailable (Y/N)Exception/Notes (inc details on classification codes, field limits, and field formats)


Tbd – see swagger spec











Standing Orders

As per the OBIE API standards for Standing orders, and in line with our direct channels, our APIs offer the opportunities for customers to choose the number of payments or the last payment date they would like when setting up a Standing Order via a Payment Initiation Service Provider. The latest date for a final payment is 31st December 2059. If customers require a long term standing order then this can be achieved by selecting a high number of payments or a last payment date that keeps the standing order in place till 31st December 2059 at the latest. In coming months we will add an option of ‘until further notice’ for a standing order as an additional way to set up long term standing orders up to 31st December 2059.

App 2 App Information

Prerequisites for testing

...

RBS (National Westminster Bank Plc.) implementation of Redirection Journey Improvement as agreed with OB Trustee

ItemActions for RBSDue date
1Display of data clusters in tile format and alignment of terminology to OBIE’s Customer Experience Guidelines

Completed

14 December 2018

2Refine the position on the screen that user accounts appear when selecting accounts to be shared with an AISP

Completed

14 December 2018

3

Other direct enhancements resulting from the CEG:

AISP

  • Clearer display of when consent expires
  • Two step consent – additional step removed which used to show details of what data is being shared automatically; now users can choose to click ‘What am I sharing?’
  • Implementation of quick links e.g. select all accounts
  • Explanation of which accounts are and are not available for selection up front rather than as a link
  • Sticky footer once account is selected which also shows total number of accounts being shared

PISP

  • Two step consent journey – select account and review steps merged into one screen
    Payment information shown to reflect research findings on what information PSU’s use to identify their preferred payment account
    Fully responsive solution for consistent experience regardless of device

Completed

14 December 2018

4Refinement to the wording regarding the purpose of connecting to Online Banking on each authentication screen and highlighting that credentials will not be shared with TPPs

Due

26 February 2019

5Display of data at ASPSP as a PSU selected option to avoid replaying consent – user has option to click ‘What am I sharing?’ link on each screen post-authentication

Completed

14 December 2018