Notice of change - sub-TPP id now mandatory in payment initiation requests

Issued: 3rd March 2025 | TB-1549

What's changing?

We're adding validation to ensure that if a TPP is processing payment requests under Token.io's license, the payment request must contain a valid sub-TPP id.

This change will affect Payment requests for:

• Payments v1

• Payments v2

What problem will this solve?

This will ensure that TPPs processing payment requests under Token.io's licence will comply with KYC and monitoring requirements under the Money Laundering Regulations for the UK and Germany. In line with these requirements, TPP's need to identify the sub-TPP on whose behalf they're transacting.

Does this change affect you?

This change will affect you if you're a TPP under a reseller using Token.io's licence and you send payment requests on behalf of sub-TPPs.

If you're already using sub-TPP ids in your payment requests, then you don’t need to change anything.

What action do I need to take?

For users of Token.io’s Payment v1 API:

You'll need to include the actingAs object in all POST /token-requests requests. If this object is omitted, Token.io will reject the request.

For users of Token.io’s Payment v2 API:

You'll need to include the onBehalfOfId field in all POST /v2/payments requests. If this field is omitted, Token.io will reject the request.

Please check for any backward compatibility issues to ensure that making the sub-TPP id mandatory doesn't break your integration.

When will this change apply to all impacted customers?

This change will become effective from 9th June 2025

Where can I get further information?

For assistance with the above and other operational aspects of the Token.io Account-to-Account Infrastructure, please contact Token.io Support.