On Friday morning, Mira finishes the final screens for a mobile app redesign and sends the files to her client in Austin. Three weeks of work, clean delivery, good feedback. The client replies within the hour: payment sent. By Tuesday afternoon the money has not arrived. By Wednesday it lands — minus a wire fee neither of them knew was coming, and at an exchange rate that was not the one on the screen when the client pressed confirm.
That gap between "payment sent" and "payment received" is where a meaningful share of freelance earnings disappears every week, in every country, for every freelancer who invoices across a border. The money is not lost. It is sitting in a correspondent-banking chain that was designed in a world before the internet and has not fundamentally changed since.
This article is about what the payment flow looks like when that chain is removed — and what a freelancer in Manila, Cebu, Davao, or anywhere else in the world actually needs to set up to start receiving client payments in seconds rather than business days.
Why international payments still take days in 2026
A wire transfer from Austin to Manila does not travel in a straight line. The payment enters a SWIFT messaging chain that typically passes through one, two, or three correspondent banks before it reaches the recipient's local bank. Each institution along the chain runs its own compliance screening, its own cut-off times, and its own fee — visible to the bank, invisible to the freelancer watching the status sit unchanged.
A standard international wire takes between one and five business days to settle (industry analyses of SWIFT processing flows, 2026). On a Friday send, "one to five business days" means the earliest the freelancer sees anything is Monday — if everything clears first time, if no bank along the chain has a public holiday, and if the correspondent relationship between the sending and receiving banks is direct. When it is not direct, the timeline extends. When a holiday falls in the middle, the timeline extends again.
The freelancer, meanwhile, has already started the next project. The client, for their part, has already moved on. The payment sits in transit as a structural feature of the system, not as an error by either party.
For a Filipino freelancer supporting a household, the delay compounds in a specific way. The payment arrives late. The exchange rate on the day of arrival is not the rate quoted when the client sent. The wire transfer fee — deducted somewhere in the chain — only becomes visible after the fact, in the difference between what was sent and what landed. The sum that arrives is not the sum that was agreed, and finding out which part of the chain took how much requires a call to a bank that cannot always answer the question.
What the five-day wait actually costs a freelancer
Five days is not just inconvenient. For a freelancer running a household on invoice income, five days of float is five days of planning around uncertainty: whether to pay a bill now or wait, whether to take on the next project or hold, whether to send money home this week or next. It is also five days in which the exchange rate moves — sometimes in the freelancer's favour, more often not.
The wire fee compounds the calculation. A fixed transfer charge of anywhere from USD 15 to USD 45 — deducted regardless of the invoice amount — is a meaningful percentage of a USD 150 invoice and a negligible one on a USD 5,000 project. Freelancers who do high-volume, smaller-invoice work absorb the most damage. A content writer sending eight invoices a month at USD 120 each is paying a wire fee on every one of them. The annual cost of the correspondent-banking chain is a number that is worth calculating once and then never forgetting.
A standard international wire transfer typically takes one to five business days to settle — with each correspondent-bank hop adding roughly one business day for compliance screening and booking.
— Industry analyses of SWIFT processing flows, 2026
There is also a softer cost that does not appear on any invoice: the time spent chasing. The follow-up email on day three. The check-in on day four. The bank reference request on day five. For a freelancer whose working time is their income, every hour spent on payment administration is an hour not spent on the next project.
A payment that arrives before the call ends
On the Spondula network, a payment from a client in Austin to a freelancer in Manila settles in seconds. The client pays to the freelancer's Shandle — a short, memorable identifier that replaces the bank account number, routing code, and SWIFT details the traditional wire requires — and the balance appears in the freelancer's wallet before the next email in the thread has been opened.
There is no banking holiday that can pause a Spondula send. There is no cut-off time that pushes a Friday payment into Monday. There is no correspondent bank standing between the client and the freelancer adding a day and a fee. The payment travels directly from one wallet to the other, on a peer-to-peer network that does not observe the working hours of the institutions it replaces.
For a freelancer in Cebu working for a client in London, the gap closes the same way. For a developer in Davao invoicing a startup in Amsterdam, the same. For a virtual assistant in Quezon City on a monthly retainer with a company in Toronto, the same. The speed is not conditional on the corridor — it is a property of how the network is built, not of where the sender and receiver happen to be.
Your Shandle: the invoice detail that works everywhere
The first thing to set up is an Shandle — a personal identifier on the network that replaces every account number, sort code, IBAN, and SWIFT code that clients in different countries currently need to send a wire to the same freelancer.
An Shandle looks like Smira, Scarlo, Sjanice. It goes on the invoice where the bank account details used to go. The client copies it, opens Spondula, types it in, and pays. The payment resolves to the wallet in seconds.
For a freelancer managing clients across multiple countries — a copywriter in Manila with clients in New York, Sydney, Toronto, Berlin, and Singapore — the Shandle is the single payment address that works for every one of them. No routing number for the US client. No BSB for the Australian one. No IBAN for the German one. No SWIFT code for the Singaporean one. One handle, every client, every corridor.
The handle is also stable by design. A 90-day cooldown sits between changes, so it is safe to print on an invoice template, add to a LinkedIn profile, or put in an email signature and know it will still resolve months later. A client who has paid once has the handle saved; the next invoice is three taps for them, zero admin for the freelancer.
There is a secondary benefit that does not appear in any feature list: the Shandle does not leak account information. A bank account number and sort code, handed to enough clients over enough years, is a security surface. An Shandle resolves to a wallet and reveals nothing about the underlying account. For a freelancer who invoices widely, that distinction is worth something.
Send a payment link, get paid the same hour
Alongside the Shandle, the Spondula payment link is the tool that changes the invoice cycle. A link is generated from the wallet — tied to the freelancer's handle — and set to the exact invoice amount. It goes out as a line on the invoice PDF, a button in the email body, or a message in the client's Slack channel. The client clicks, opens the payment screen, and pays. The balance arrives in the freelancer's wallet before the project retrospective has started.
For a virtual assistant in Manila managing retainer clients in the US and the UK, a payment link on a recurring invoice is the same link every month. The client bookmarks it, pays on the first of the month, and the assistant sees the balance land without a follow-up, a reminder, or a check-in. The payment becomes as automatic as a direct debit — without requiring a bank mandate, a signed agreement, or a recurring billing system.
For a web developer in Davao invoicing a startup in Düsseldorf for a project milestone, the link goes out with the code delivery and the payment clears the same afternoon. The client does not need to navigate international banking. They click, they pay, they move on. The friction that causes freelancers to lose hours chasing invoices is removed at the point the invoice is sent.
Join the conversation.
0 comments · Be respectful, be specific, be useful.
Be the first to comment.