Versions Compared

Version Old Version 95 New Version 96
Changes made by

Simon Massey

Simon Massey

Saved on

Key

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


Panel
titleColorBlack
borderStyledashed
titleOB Standards

This Section applies to ASPSPs that have implemented OB Standards


Page Properties
iconfalse
idTC-OB Standards


-Have you Implemented OB Standards?
  •  Yes
  •  No

Open Data - Which version have you Implemented?
  •  None
  •  V2.2
  •  V2.3
  •  V2.4

Read/Write API Specification Implemented or planning to implement

(Lowest version = Current, Highest version = Planned)

  •  V3.0
  •  V3.1
  •  V3.1.1
  •  V3.1.2
  •  V3.1.3
  •  V3.1.4
  •  V3.1.5
  •  V3.1.6
  •  V3.1.7
  •  V3.1.8
  •  V3.1.9
  •  V3.1.10
  •  V3.1.11
  •  V4.0

We are on v3.1.11 and currently working on uplifting to 4.0.

Following our implementation of V4.0, we will still accept requests to our v3.1.11 endpoints for a minimum of 6 months. We will provide further notification as to when our v3 services will stop at an appropriate time.

Read/Write API - Which date are you planning to implement your latest version?

In line with the latest notification from the OBL we are planning to complete our uplift to the v4 specification by the end of June 2025. This will be a phased roll out as per below:

By end of April 2025

   - AIS – All endpoints uplifted to v4.0

   - CHAPs – Consent and submission uplifted to v4.0       

By end of May 2025

  - DIP – Consent and submission uplifted to v4.0

  - VRP – Consent and submission uplifted to v4.0

By end of June 2025

   - DSO – Consent and submission uplifted to v4.0

   - DSP – Consent and submission uplifted to v4.0

   - CBPII – Consent and confirmation uplifted to v4.0

   - Event Notification API – uplifted to v4.0

Following this change, we will still accept requests to our v3.1.11 endpoints. Full roll out of the remaining endpoints will continue until the end of June.

Our Sandbox environment will be uplifted in line with the release of the uplifted  v4 API’s into production. 

Have you implemented v4.0 information flows, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 
We continue to evaluate the non-mandatory changes relating to information flows. Details of any changes made as part of our V4 uplift will be provided via our developer portal once confirmed

Dynamic Client Registration - Which version have you Implemented or planning to implement?

(Lowest version = Current, Highest version = Planned)

  •  None
  •  V3.1
  •  V3.2
  •  V3.3

DCR - Which date are you planning to implement your latest version?

Have you implemented Trusted beneficiaries, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented Reverse Payments, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented ECA Standard?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

ECA Implementation details



Have you implemented Bulk/File Payments?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented VRP – Sweeping, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Have you implemented VRP non-Sweeping, if not date planned to Implement?

  •  Already Implemented
  •  Planning to implement
  •  Not planning to implement 

Reviewing potential to offer non-sweeping VRP

Contact: nationwideopenbanking@nationwide.co.uk

PISP - Single Payment Limit

New Payee - £25,000

Existing Payee - £25,000

Established Payee - £100,000

Low Risk - £100,000

High Risk (i.e Crypto) - £5,000


PISP - Daily Payment Limit

New Payee - £25,000

Existing Payee - £100,000

Established Payee - £100,000

Low Risk - £100,000

High Risk (i.e Crypto) - £5,000

There is an aggregate payment limit of £100,000 per day from a single account


How many months of transaction do you provide?15months at initial authorisation, after that it is 90 days with additional data available via our statements APICC data is limited to 90 days.
Have you implemented TRIs (Transactional Risk Indicators), if not, date planned to Implement?We have plans to but no date confirmed just yet
What is your approach to Implementing TRIs?
  •  Accept payload with TRI fields – Process all fields
  •  Accept payload with TRI fields – Ignore all fields
  •  Reject payload with TRI fields – Error back to TPP
  •  Accept payload with TRI fields – Process few fields (Provide list of accepted fields)  



...

Panel
borderStyledashed
titleSCA-RTS 90-day reauth Implementation


Page Properties
idSCA-RTS


Which date are you planning on implementing the SCA reauthentication exemption?


20th September 2022

What is your approach to token management to enable application of the reauthentication exemption? (see link to FCA guidance)


AIS consents created after the implementation of the changes will remain valid until the Consent Expiry Date, if set. They will not normally need to be reauthenticated.


Existing AIS consents will require a final reauthentication, at which point they will remain valid until the Consent Expiry Date, if set. No further reauthentication will normally be required.


There are scenarios where a reauthentication may be necessary, including but not limited to:

  • Suspected fraud or unauthorised access
  • Where a Nationwide Member has revoked the access via our digital and/or mediated channels
Article 10A - Endpoints exempt of SCA-RTS
  •  

    Accounts

  •  

    Transactions (90days)

  •  

    Balances

  •  

    Standing orders

  •  

    Direct debits

  •  

    Beneficiaries

  •  

    Products

  •  

    Offers

  •  

    Parties

  •  

    Scheduled Payments

  •  

    Statements


Article 10A - Endpoints not exempt of SCA-RTS
  •  

    Transactions (more than 90days)

  •  

    Standing orders

  •  

    Direct debits

  •  

    Beneficiaries

  •  

    Products

  •  

    Offers

  •  

    Parties

  •  

    Scheduled Payments

  •  

    Statements


Article 10A - Maximum time period after authentication
Please specify the time period in minutes
SCA-RTS implementation status (updated by OBL PS team only)

Status
colourGreen
titleImplemented




...

Panel
titleColorBlack
borderStyledashed
titlePSD2


Page Properties
idTC-PSD2


-Which Directory are you using as your Trust Framework?Open Banking
Are you caching the Directory?Yes, 24hrs
Transaction IDs SupportedMarch 2019 - Option 1 SupportedASPSPs provide a Unique, Immutable TransactionID from their core system

Are you Seeking Fallback Exemption?

  •  Yes
  •  No


Article 10 - Maximum time period after authentication1 HourWhen 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 SCA

14th September 2019

  • 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
  • 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
Major Milestones



Brand(s)



...