Nationwide's Open Banking developer portal

Breaking Change : Implementation of FAPI Security Profile 1.0 Advanced Final Specification

We would like to inform TPPs that we have changed to the FAPI Security Profile 1.0 Advanced Final specification in our Sandbox environment.

Following this change, requests to any of our Read/Write endpoints meeting any of the following criteria will be rejected:

- Requests submitted without an nbf claim in the request object

- Requests submitted with an nbf claim in the request object that is greater than 60 minutes in the past 

- Requests submitted with an exp claim in the request object that has a lifetime of greater than 60 minutes

Variable Recurring Payments (VRP) & Sweeping

VRP sweeping service is now available for testing in the sandbox environment within the Nationwide Developer Portal. To sign up for access to the Portal, click here.

Get Party

We have removed Get Party URL from the Developer Portal and the Sandbox.

Addition of Loans and Mortgages APIs

We have added Loans API and Mortgages API documentation on our Portal for trusted partners.

Open Banking Standard version 3.1.11

We have moved to the OBIE Specification Version 3.1.11. This version includes updates on:

 - New parameter “VRPType” to VRPRequest for all VRP submissions, to determine the types of payment. As of now, only “sweeping” is set as response.

 - Update OBReadStatement2, OBReadBalance1 for AIS APIs to include new scheme name "Wallet" & "Currency". The requirement is to enable TPPs to be able to access currency wallet products supported by ASPSPs to provide AIS services to the PSU. Swagger to be updated for OBReadStatement2 and OBReadBalance1 to add ‘Wallet' and ‘Currency’ details.

Breaking: Changes to Sandbox Environment Domains

The domains for our Open Banking Sandbox environment have changed. Further information can be found in our FAQs.

Breaking Change : Provision of DebtorAccount object in GET/ accounts/ {AccountId}/ transactions call response

In August 2024 we implemented a change to the response to calls to our GET/ accounts/ {AccountId}/ transactions  endpoint.

Previously, when we received a call to the GET/ accounts/ {AccountId}/ transactions endpoint with CreditDebitIndicator set to Credit, we provided the CreditorAccount object in the response.

Following the change, when we receive a call to the GET/ accounts/ {AccountId}/ transactions endpoint with CreditDebitIndicator set to Credit, we instead provide the DebtorAccount object in the response.

Review of Personas

We will be carrying out a review of our Personas so that they provide better information to TPPs.

Breaking Change : Implementation of FAPI Security Profile 1.0 Advanced Final Specification

We would like to inform TPPs that in November 2024 we will be changing to the FAPI Security Profile 1.0 Advanced Final specification.

Following this change, requests to any of our Read/Write endpoints meeting any of the following criteria will be rejected:

   - Requests submitted without an nbf claim in the request object
   - Requests submitted with an nbf claim in the request object that is greater than 60 minutes in the past
   - Requests submitted with an exp claim in the request object that has a lifetime of greater than 60 minutes

We are planning to implement this change on the following dates:
   - 27th November 2024 in our Production environment

TPPs are welcome to adhere to the FAPI 1.0 standard for calls to our OB service in advance of these dates, but following the implementation it will be mandatory.

Addition of Non-OB APIs

We are looking to add Credit Card API documentation on our Portal for trusted partners.