Notice of Change – Open Banking Improvements: CMA9 v4 API – First Trust Bank

Issued: 27th February 2026 | TB-1634

AIS/PIS

What's Changing?

First Trust Bank will migrate to CMA9 v4.

As part of this migration:

Bank raw responses are changing
PCC codes are changing
Improved error messaging
Changes to Balance Type Identifiers

All changes are available in the Sandbox for testing.

Does This Change Affect You?

Payment Initiation Services (PIS)

You may be impacted if:

You are initiating payments with First Trust Bank 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 First Trust Bank 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 standard payment status codes.

❗ Note: Token's own status codes will remain unchanged.

If you have designed your integration to rely on raw bank statuses, you must decide how to handle the ISO 20022 mappings.

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, ACWP, ACSC
SUCCESS	ACCC
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, ACWP, ACSC
INITIATION_COMPLETED	ACCC
INITIATION_DECLINED	BLCK, RJCT
INITIATION_DECLINED	CANC (domestic scheduled payments)

Consistent Error Messaging

Bank error messages will be updated to match the CMA9 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}

Handling of PCC Codes

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

If you would like to include a PCC, you must provide one as part of your request.

You can find more information on the new PCCs here:

Affected Endpoints

V1 API

POST /token-request

V2 API

POST /v2/payments

❗ Note:
If you do not send a PCC or send an incorrect PCC, your request will not fail. Token will ignore invalid PCC values and the field will be empty.
While PCC is not mandatory in CMA9 v4, it is recommended, as the Payment Context Code is a key transaction indicator and may be validated by the receiving bank.

Account Information Services

Changes to Balance Type

Existing Balance Type – v3	New Balance Type – 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:

Review your implementation for payment statuses, PCC handling, and balance type identifiers.
Test your integration in the Sandbox environment.
Speak with your implementation manager, or
Contact us at support@token.io

When Will This Change Apply to All Impacted Customers?

16 March 2026

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