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.
Digital providers have reduced the friction: many now let you enter a phone number or email address and resolve the banking details on the backend. But the underlying infrastructure is the same — the identifiers still need to exist, the correspondent-bank chain still needs the SWIFT code, the compliance fields still get submitted. The smoother interface is a layer on top of the same six-step system.
What the S-handle replaces
An Shandle is a single identifier that resolves everything the six-field system resolves — without asking the sender to know any of those six things. It identifies a specific wallet on the Spondula network. That wallet belongs to a specific person. A payment sent to the handle arrives in that wallet in seconds, regardless of what country either party is in.
There is no country code embedded in the handle. No bank code. No format that changes depending on the destination. A UK sender does not need a different kind of identifier to send to Nigeria than to Germany than to the Philippines. The handle is the handle, everywhere the network operates.
The sender does not need to know the recipient's bank. The sender does not need to know the recipient's country. The sender does not need to know whether the recipient uses a bank account at all. The Shandle resolves to a wallet — and the wallet is what receives the payment, regardless of the financial infrastructure on the recipient's end.
One identifier, any country, instant settlement
The closest analogy is the $cashtag on Cash App — except Cash App stops at the US border. An Shandle does not stop anywhere. A user who created their handle in London and moved to Lagos uses the same one. A freelancer in Manila who receives from clients in Toronto, Amsterdam, and Dubai gives all three of them the same handle. The sender in Toronto does not need a different piece of information than the sender in Amsterdam. One handle. Any corridor. Same settlement speed.
The handle also does not expire or change when someone moves, changes banks, or changes phone numbers. A sort code changes when a bank branch closes. An account number changes when someone moves their account. A wallet address in cryptocurrency must be regenerated and re-shared constantly for best security practice. An Shandle is attached to the person — to their wallet, their identity on the network — and stays the same as long as the user wants it to.
Six fields, twenty minutes, and a WhatsApp photograph of an account summary — or one handle, ten seconds, and the same outcome. The S-handle is not a better version of the IBAN. It is a different approach to the same question: how do I send value to this specific person?
Spondula is pre-launch. If you have ever spent more time finding the right account details than you spent deciding to send the money, the waitlist is where one thing replaces six.
Frequently asked questions
What is an S-handle?
An Shandle is a unique personal identifier on the Spondula network — similar in concept to a $cashtag or a @username, but designed for global payments rather than a single domestic market. It identifies a specific wallet. Anyone who knows your Shandle can send to you instantly, from any country the network supports, without needing your bank account details, IBAN, SWIFT code, or any other banking identifier.
Does an S-handle work differently depending on which country I'm sending to?
No. The same handle works whether the sender is in the UK, the UAE, the US, or anywhere else on the network. The format does not change by destination. The sender does not need a different piece of information for different countries.
What if I change banks — does my S-handle change?
No. The Shandle is attached to your Spondula wallet, not to your bank account. Changing banks, moving countries, or switching phone numbers does not change the handle. Anyone who has already saved your handle can still send to you after you move.
Can the recipient receive without a bank account?
Yes. The Shandle resolves to a Spondula wallet, not a bank account. The recipient holds the received balance in their wallet, which can be used at a Spondula Partner Location or converted to local cash at a Local Operator. No bank account is required on the receiving end.
Is an S-handle the same as a cryptocurrency wallet address?
No. A cryptocurrency wallet address is a long, generated string — typically 26–35 characters of letters and numbers — that changes with each transaction for security. An Shandle is a short, human-readable identifier chosen by the user, permanent, and designed to be shared and remembered the way a username is. You give your Shandle to people the same way you give your phone number — once, and it stays the same.
Spondula is a global payments network. It is not a bank, exchange, investment platform, or broker. Availability, pricing, and Operator coverage vary by country. Bitcoin rewards depend on real network activity and are not guaranteed. See our terms and conditions for full details.
