---
updatedAt: 2026-01-16T01:10:43.000Z
agentTools:
  projectIndex: https://docs.truelayer.com/llms.txt
---

# Character limitations in payments

You must consider certain character limitations when creating payments.

[block:html]
{
  "html": "<style>\n   /* Style for the closed details element */\n    details {\n      border: 1px solid #1f1f25; /* 1px stroke around the edge */\n      border-radius: 16px; /* 16px rounded corners */\n      padding: 8px; /* Optional: Add padding for better visual appeal */\n    }\n\n/* Style for the summary within the details element */\n    details summary {\n      outline: none; /* Remove default focus outline */\n    }\n\n/* Style for the open details element */\n    details[open] {\n      border: 1px solid #1f1f25; /* 1px stroke around the edge */\n      border-radius: 16px; /* 16px rounded corners */\n      padding: 8px; /* Optional: Add padding for better visual appeal */\n    }\n  </style>"
}
[/block]

Different banks support and disallow different characters when you create a payment request.

Banks most often place limits on:

* Maximum character lengths.
* Special characters.

## Character limits

Different banks have different character limits for payment references and beneficiary names.

Typically, the character limit for payment references is **18 characters**.

Some banks support up to 35 or 40 characters for beneficiary names. For remitter names, we support up to **80 characters**. However, as some banks only support up to **18 characters** for names, you should consider this in your integration.

## Special characters in payments

All banks support basic Latin characters in payment references and beneficiary names. Many banks support some special characters such as colons, dashes, or apostrophes.

We do not support the special characters `(`, `)` or `^` in any payment (UK or EU). We also do not support any Unicode control characters.

Special character handling varies from bank to bank, so there's no consistent rule for special characters. Because of this, we recommend that your payment references and beneficiary names don't include special characters at all.

The table below displays the special characters supported by some popular UK banks.

| Banking provider | Supported special characters |
| :--------------- | :--------------------------- |
| Bank of Scotland | ` / ' : . , -`               |
| Barclays         | ` _ , . - _`                 |
| Danske           | `/ ' : . , - _`              |
| First Direct     | ` / ' : . , -`               |
| Halifax          | ` / ' : . , - _`             |
| HSBC             | `. -`                        |
| Lloyds           | `/ ' : . , - _`              |
| M\&S Bank        | `/ ' : . , -`                |
| Monzo            | ` / ' : . , - _`             |
| N26              | `' ; . , -`                  |
| Nationwide       | ` : . , -`                   |
| NatWest          | `/ . - ' "`                  |
| RBS              | `/ . - ' "`                  |
| Revolut          | ` / ' " \\ \| : ; . , \_`    |
| Santander        | `/ : . , -`                  |
| Starling         | ` / ' : . , - _`             |
| Tesco            | `. ' : . , - _`              |
| TSB              | `/ . , -`                    |
| Ulster           | `/ . - , "`                  |

<details>
  <summary><b>Additional restrictions for Nationwide</b></summary><hr>

Nationwide has additional rules for payment references, which mean you can't use words that are associated with command injection exploits. This is a list of example terms that you can't use in Nationwide references:

* `echo`
* `delete`
* `config`
* `exec`
* `system`
* `shell_exec`
* `passthru`

</details>