Bank branch codes: verify the payment details
Use the beneficiary’s verified banking details and the bank’s official instructions. Do not copy a branch code from an unverified search result or replace it with a code used by another bank. Account number, bank and reference each need their own check.
Read the whole set of details
Obtain an account confirmation or another authenticated instruction for the beneficiary. Check the account holder, account number, bank, code type and payment reference as a complete set. A universal code, branch-specific code and international routing instruction should not be assumed interchangeable. Ask the sending bank which fields the intended payment requires.
Verify a changed instruction independently
If an invoice suddenly gives new account details, contact the established organisation through a previously verified route. Capitec’s fraud guidance warns against being instructed to move money to a safe account [1]. Use that caution when a caller supplies banking details, rather than trusting urgency or a familiar-looking message alone.
Keep the purpose of the reference clear
A correct bank destination does not ensure the recipient can allocate the payment. Copy the agreed reference and save the receipt. For a high-impact payment, use the bank’s available verification tools and ask the beneficiary to confirm allocation. Do not publish the beneficiary’s full account details in a public forum for checking.
Verify recipient details through a separate channel
Keep the recipient name, bank name, account number and branch-code source together. Where an invoice changes payment details, contact the organisation using a number or address already obtained independently. Do not use the same unexpected message as both the payment instruction and its verification. Check that the bank’s published code belongs to the named bank, then ask about any remaining account-detail uncertainty. A correct branch code does not prove that the account belongs to the intended recipient. Save confirmation and the invoice version used so a later payment query has a clear evidence trail.
A calculation you can check
Fictional invoice R800 with reference INV-104 needs both a verified destination and the correct allocation reference. Changing the reference to INV-140 does not change R800, but can create an allocation question.
Questions about this decision
Can I use any universal code?
Use only the code and instructions appropriate to the bank and payment type. Confirm uncertain fields with the sending bank.
Does a branch code verify the recipient?
It does not replace checking the beneficiary’s identity, account number and authenticated payment instruction.
Where should I obtain the code?
Use the beneficiary’s official account confirmation and the bank’s own information, not a copied third-party table.
What if invoice details change?
Verify through an established contact channel before paying. Keep the confirmation with the changed instruction.
Is an international code the same?
Ask which routing fields your bank requires for the cross-border payment. Do not substitute a domestic field by guesswork.
Does the payment reference matter?
Use the reference agreed with the recipient so the payment can be matched to the right invoice or account.
What if I already sent incorrect details?
Contact your bank with the transaction reference promptly. Do not assume the transfer can be recalled or corrected automatically.
Should I share details publicly for help?
Use authenticated support and redact unnecessary personal information. A public post is not an account-verification service.