One thing instead of six — the S-handle vs IBAN, SWIFT, and sort codes

The wire transfer that asked for six things you did not have

You want to send £200 to your brother in Lagos. You open your bank's international transfer form. Field one: beneficiary account number. Field two: sort code or routing number. Field three: SWIFT or BIC code. Field four: IBAN. Field five: beneficiary address. Field six: reason for payment. You have your brother's phone number. You have his name. You do not have any of the other six things, and neither does he know them off the top of his head. He has to log into his bank, find his account details, photograph them, WhatsApp them to you, and by the time all of this is done you have spent twenty minutes on a task that should take twenty seconds.

Then consider Cash App. You type a $cashtag. You send. Done. Ten seconds, one piece of information, no form.

Both of these are payment systems. Only one of them was designed around the person sending, not the institution processing.

What each of those six things actually is

Every identifier in the international wire form exists because the banking infrastructure was built for a world of institutions routing value between themselves — not for a person sending money to another person. Each one is a solution to a problem the infrastructure created for itself.

The account number identifies a specific account at a specific bank within a specific country. It means nothing outside that country. A UK account number is not the same format as a US routing number, which is not the same format as an Indian account number.

The sort code (UK) or routing number (US) identifies the specific bank branch. It is needed because account numbers alone are not unique across the banking system — two people at two different banks can have the same account number. The sort code disambiguates. It is a fix for a problem the numbering system created.

The SWIFT code (also called BIC — Bank Identifier Code) identifies the institution at the international level. It is what correspondent banks use to route a payment from one country's banking system to another. Without it, the international rail does not know where to deliver the message that a payment is coming.

The IBAN (International Bank Account Number) is a standardised format that combines country code, check digits, bank code, and account number into a single string — up to 34 characters long depending on the country. It was created to reduce errors in cross-border transfers. It has not been adopted universally: the US does not use IBANs. Many African and Asian countries do not use IBANs. So whether you need one depends on where the recipient's bank is.

The beneficiary address and reason for payment are compliance fields — required by anti-money-laundering frameworks in many jurisdictions. They do not move the money. They exist so the institution processing the transfer can meet its regulatory obligations.

Six fields. Four different systems that evolved in parallel, never designed to work together, each solving a different piece of a problem the infrastructure created when it was built around institutions rather than people.

Why they are six different answers to the same question

The question is simple: how do I send value to this specific person? Every one of those six fields is an attempt to answer it within a system that was not designed to answer it directly. The SWIFT code routes the payment to the right country. The IBAN routes it to the right bank. The account number routes it to the right account. The sort code makes sure the account number is unambiguous. The address and reason satisfy the compliance layer. Six steps where one should exist.