Formatting of Belgian IBANs

NicolasV

Hello,

I have two suggestions regarding payments to Belgian IBAN accounts.

The field starts with BE__ in my case, BUT the way the numbers are separated is confusing (BE12 345 6789 0123 4 instead of BE12 3456 7890 1234).

Furthermore, structured communications (such as +++123/1234/12345+++) are very common on invoices. It includes a verification to avoid errors. Typing it without the + and / signs works, but could lead to errors.

It would be great to add this features added for the Belgian market 😬

Greetings,
Nicolas

Sander

Nicolas The field starts with BE__ in my case, BUT the way the numbers are separated is confusing (BE12 345 6789 0123 4 instead of BE12 3456 7890 1234).

Are you using Android or iOS (or do you see it on both in case you have both types of devices)?

Nicolas Furthermore, structured communications (such as +++123/1234/12345+++) are very common on invoices. It includes a verification to avoid errors. Typing it without the + and / signs works, but could lead to errors.

See ➡️ https://together.bunq.com/d/5983-structured-communication-for-belgian-transfer for an existing topic about this. 😁

I've renamed this topic so we can focus on the formatting of Belgian IBANs here. 👍

Andreas

Nicolas The first 3 numbers after the check digit in Belgian IBANs are actually the "bank identifier", so each Belgian bank has its own unique number there.

NicolasV

Bonsoir Sander,

Merci pour vos réponses et le lien vers l'autre discussion 😃

J'utilise Android et je n'ai pas la possibilité de vérifier sur iOS.

On ne détaille plus la structure des comptes belges. On les formate par blocs de 4 caractères maintenant. Je viens de vérifier et dans l'historique des transactions par exemple, le format est correct. Mais pas quand on encode un virement.

MoFi

I would also like bunq to Formate the card number or the iban on the cards in 4-Number Blocks ✌🏼 would make it easier to read it 😉