Versions Compared

Key

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


Panel
borderStyledashed
titleOB Standards


Page Properties
idStandards-Production


Implement Open Data v2.2Live
Implement Read/Write API Specification v3.1 
Implement Customer Experience Guidelines v1.1

Mobile  

Browser  


Implement App-to-App Redirection 
Implement OB Security Profile Implementer's Draft v1.1.2 
Implement FAPI Profile Implementers Draft 2

Implement CIBA Profile Implementers Draft 1N/A
Implement Dynamic Client Registration v1.1Live
Implement Dynamic Client Registration v3.1 
Decommission Read/Write API Specification v1.x/2.x

AIS v1.1 31st October 2019

Planning to decommission v1 APIs in end of October once TPPs have completed migration.  
Decommission OB Security Profile Implementer's Draft v1.xComplete



...

Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


Dispute Management System?

Yes
FCA Adjustment Period - Maintaining Screen Scraping?Yes

Seeking Fallback Exemption?

Exemption Granted -   - Granted Exemption

Adjusted or Fallback Interface?

None at present
Adjusted or Fallback URL?

Contact Email or Phone Number?
Dev Portal URL?www.nationwidedeveloper.co.uk

Test Facility Implementation Date?

 
Production Interface Implementation Date? 
Contingency Measures
N/a as Nationwide has obtained its exemption
Article 10 - Maximum time period after authentication?
When Strong Customer Authentication  (SCA) is completed, you will be able to access all account information the customer has agreed they can access during the initial session (1 hour duration). For subsequent requests we will support requests for accounts, balances and for up to 90 days history of transactions data for 90 days following the authentication (provided the customer has allowed access for this period to the TPP)
Article 10 - Endpoints exempt of SCA14th September 2019
    • Once initial SCA has been completed you will be able to access the following account information endpoints without SCA (provided the customer has allowed access on an enduring basis to the TPP)
      • GET /Accounts
      • GET /accounts/{AccountId}
      • GET /accounts/{AccountId}/balances
      • GET /accounts/{AccountId}/transactions
      • Access to accounts endpoints allows retrieval of the AccountId to call balance and transaction endpoints

Authentication Method - Open Banking Channel (Browser)?

Redirect auth using SCA method that aligns with digital channels.

Authentication Method - Open Banking Channel (APP)?

App to App auth using SCA method that aligns with digital channels.

Authentication Method - Private Channel (Browser)?

As they stand today with further auth methods that may be delivered in the future

Authentication Method - Private Channel (APP)?

As they stand today with further auth methods that may be delivered in the future

Authentication Method Implementation Date (Open Banking Channel)?

Methods detailed are currently live in production

Authentication Method Implementation Date (Private Channel)?

Methods detailed are currently live in production

SCA Implementation Date?

TBC (See Notes)

We are planning to implement updated IB authentication screens w/c 9th September. These will provide members the choice to authenticate using SCA access methods (Card Readeror IB Passnumber and OTP) or maintain access (including via screenscrapers) by continuing to use non-SCA methods of authentication (memorable data). The new log-in screens will also now require members to enter their date of birth. In line with the FCA’s six-month adjustment period we intend to gradually remove the ability of our members to utilise non-SCA methods over this time period as TPPs make the transition to open banking APIs. These changes will also be reflected in our OB browser authentication screens.

SCA Scope? (will it inhibit non PSD2 accounts)

SCA will be delivered to cover the requirements of Reg 100 PSRs



...