# Notice of Change – Open Banking Improvements: OBL v4 API – Nationwide

Issued: 19th November 2025 | TB-1628

![AIS/PIS](/assets/ais-pis.cae356edcd7b630129229253e3a0506c39dcffc674bb5faf5e999e6c348f1e84.25996077.png)

### What's Changing?

Nationwide will migrate to OBL v4.

Changes associated with OBL v4:

PIS:

- Bank raw responses are changing
- PCC codes are changing
- Improved error messaging


AIS:

- Changes to Balance Type Identifiers


All changes are available on Sandbox for testing.

### Does This Change Affect You?

#### Payment Initiation Services (PIS)

You **may be impacted** if:

- You are initiating payments with banks using the UK Open Banking API standard, and your PIS integration relies on raw bank statuses.
- You depend on specific bank error messages in your processes.


You are **not impacted** if:

- You do not rely on raw bank responses.


#### Account Information Services (AIS)

You **may be impacted** if:

- You are making AIS calls to banks using the UK Open Banking API standard, and you validate balance types in your AIS integration.


You are **not impacted** if:

- You do not validate balance types in your AIS integration.


### Changes in Detail

#### Payment Initiation Services

##### Standardised Payment Statuses

The `bankPaymentStatus` field will now return [ISO 20022](https://www.iso20022.org/) standard payment status codes.

> **Note:** Token’s own status codes will remain unchanged.


If you have designed your implementation for raw bank statuses, you must decide how to handle the ISO 20022 version.

- [V4 Status Repository and Diagram](https://openbankinguk.github.io/read-write-api-site3/v4.0/resources-and-data-models/pisp/domestic-payments.html#state-model)


**How Token handles v4 statuses for APIv1:**

| Token Payment Status | ISO 20022 Raw Bank Payment Statuses |
|  --- | --- |
| `PROCESSING` | `PDNG`, `RCVD`, `ACTC`, `PATC`, `ACCP`, `ACFC`, `ACSP`, `ACWC`, `ACSC` |
| `SUCCESS` | `ACCC`, `ACWP` |
| `DECLINED` | `BLCK`, `RJCT` |
| `CANCELLED` | `CANC` (domestic scheduled payments) |


**How Token handles v4 statuses for APIv2:**

| Existing Payment Statuses – v3 | New Payment Statuses – v4 |
|  --- | --- |
| `INITIATION_PROCESSING` | `PDNG`, `RCVD`, `ACTC`, `PATC`, `ACCP`, `ACFC`, `ACSP`, `ACWC`,`ACSC` |
| `INITIATION_COMPLETED` | `ACCC`, `ACWP` |
| `INITIATION_DECLINED` | `BLCK`, `RJCT` |
| `INITIATION_DECLINED` | `CANC` (domestic scheduled payments) |


##### Consistent Error Messaging

Bank error messages will be updated to match the **OBL v4 specification** for improved clarity and consistency.

**Affected Endpoints:**

**V1 API**

- `providerDetails.status`
  - `POST /transfers`
  - `GET /transfers/{transferId}`
  - `GET /transfers`


**V2 API**

- `bankPaymentStatus`
  - `GET /v2/payments`
  - `GET /v2/payments/{paymentId}`


**VRP API**

- `bankVrpConsentStatus`
  - `POST /vrp-consents`
  - `GET /vrp-consents`
  - `GET /vrp-consents/{id}`
  - `DELETE /vrp-consents/{id}`
- `bankVrpStatus`
  - `GET /vrp-consents/{id}/payments`
  - `POST /vrps`
  - `GET /vrps`
  - `GET /vrps/{id}`


##### Handling of PCC Codes

Token.io currently populates the `PCC` field with a default value when none is provided. However, with **v4**, this will no longer occur.

If you would like to include a PCC, you must provide one as part of your request.
More information on PCCs can be found in our documentation for [v1](../../api/reference/Requests-for-Payments-v1-or-AIS#operation/GatewayService.StoreTokenRequest) and [v2](../../api/reference/Payments-v2#operation/InitiatePayment).

**Affected Endpoints:**

**V1 API**

- `POST /token-request`


**V2 API**

- `POST /v2/payments`


> **Note:**
If you decide not to send a PCC or send an incorrect PCC, your request will not fail. Token will ignore any incorrect PCC, and the field will be empty.
While PCC is not mandatory currently or in OBL v4, it is **recommended** to include it, as the Payment Context Code is a key transaction indicator that may be validated by the receiving bank.


#### Account Information Services

##### Changes to Balance Type Identifiers

| Existing Balance Type Identifier – v3 | New Balance Type Identifier – v4 |
|  --- | --- |
| `ClosingAvailable` | `CLAV` |
| `ClosingBooked` | `CLBD` |
| `ForwardAvailable` | `FWAV` |
| `Information` | `INFO` |
| `InterimAvailable` | `ITAV` |
| `InterimBooked` | `ITBD` |
| `OpeningAvailable` | `OPAV` |
| `OpeningBooked` | `OPBD` |
| `PreviouslyClosedBooked` | `PRCD` |
| `Expected` | `XPCD` |


### What Action Do I Need to Take?

If you are impacted, to ensure a smooth transition we strongly recommend that you:

- **Speak with your implementation manager**, or
- **Contact us at:** [support@token.io](mailto:support@token.io)


### When Will This Change Apply to All Impacted Customers?

Token will go live with Nationwide OBL v4 on Wednesday 3rd December 2025.

### Where Can I Get Further Information?

For any questions, concerns, or to discuss your integration, please speak with your implementation manager or contact:
[support@token.io](mailto:support@token.io)