# Notice of change -  Norisbank & Deutsche Bank Customer ID changes

Issued: 26th August 2025| TB-1627

### What's changing?

As part of improvements by Deutsche Bank, both Norisbank and Deutsche Bank customers have the option to define a new Customer ID.

### Does this change affect you?

This change will affect Payment requests for:

Payments v1

Payments v2

### Changes in detail

This change will impact any PSU providing additional credentials using the following API calls:

Payments v1:

[POST /token-requests/{tokenRequestId}/authorization](../../api/reference/Requests-for-Payments-v1-or-AIS#operation/GatewayService.InitiateBankAuthorization)

Payments v2:

[POST v2/payments](../../api/reference/Payments-v2#operation/InitiatePayment)

[POST v2/payments/{paymentId}/embedded-auth](../../api/reference/Payments-v2#operation/ProvideEmbeddedFields)

Clients using Token Hosted Pages to collect credentials will not be impacted.

#### What problem will this solve?

For PSUs who have changed their Customer ID, they will now provide this in a single field rather than branch number and account number.

### What action do I need to take?

For clients providing additional credentials via API, please ensure that you support providing both formats:

Legacy Format

- 10 numerical characters: 3 digits for the branch number and 7 for the account number
- Spaces are **not** allowed


New Format

- 2–50 characters
- Allowed characters: a-z, A-Z, 0-9, < > , . : ; _ - ! § $ % & = ? @ #
- Spaces are **not** allowed


`"credentialFields": [``{``"id": "psuID",``"displayName": "Customer ID"``}``]`

### When will this change apply to all impacted customers?

This change will become effective from **26th November 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).