Every week, hundreds of millions of people send money across a border. Most of them do not think of it as finance. They think of it as a message: something to a parent who needs it for Tuesday's market, a client who owes it for a project delivered on Friday, a family fund that everyone contributes to and no one should have to chase. The money is supposed to feel like a message. It rarely does.
What follows is one week. Four people. Four corridors. Four ordinary payment moments — the kind that happen every week for millions of people — and what each one looks like when the infrastructure actually works.
Monday: the designer in Manila
Janice finishes the last set of brand assets on Monday morning and sends the delivery email to her client in New York at 8 a.m. Philippine Standard Time. The project has taken three weeks: a full identity system, a type treatment, a set of social templates. The client has been responsive. The invoice has been sitting in the thread since last Thursday.
On the old flow, Monday morning in Manila is Sunday evening in New York, which means the wire transfer will not be initiated until Tuesday at the earliest, will route through a correspondent bank in the US, and will arrive sometime between Wednesday and Friday depending on whether any institution in the chain has a clearing backlog. By the time the money lands, Janice has already bought materials for the next project on credit, spent a day wondering whether to follow up, and lost four days of the float she needed to cover the studio's running costs.
On Monday at 8.04 a.m., she adds the payment link to the delivery email. The client opens the email in New York at 7.12 p.m. Sunday, clicks the link, and pays. The balance appears in Janice's wallet at 8.07 a.m. Monday. She is on a call with her next client by 9.
The three minutes it takes the payment to travel from a laptop in New York to a wallet in Manila is not the impressive part. The impressive part is that Janice does not spend Monday chasing it. She does not have to. The payment was always going to arrive — it just arrived when it was supposed to.
Tuesday: the trader in Accra
Kofi runs a small import business in Accra. He sources fabric from suppliers in Turkey and Indonesia, sells it across West Africa, and manages a payment flow that spans three continents and at least four currencies on any given month. Tuesday is when the Turkish supplier expects the deposit for the next shipment.
The old flow: Kofi visits his bank, initiates a SWIFT wire to Istanbul, pays the transfer fee, accepts the exchange rate on the bank's screen, and waits. The supplier receives the payment between three and five business days later. Both sides of the transaction have to plan around a week of uncertainty. The supplier holds the goods. Kofi holds the invoice. The goods do not ship until the bank in Istanbul confirms the funds.
On Tuesday, Kofi opens the app. He has the supplier's Shandle, shared over WhatsApp when they set up the arrangement last month. He types the amount, confirms the rate — flat 0.2% on the USD-S-to-TRY-S conversion, shown before he hits send — and pays. The supplier in Istanbul sees the balance land six seconds later. The shipment is confirmed before the end of the business day in Turkey, which is still Tuesday afternoon.
The supplier's bank is not involved. Neither is Kofi's. The goods leave Istanbul on Wednesday. By the old timeline, they would still be waiting for the transfer to clear.
Wednesday: the nurse in Manchester
Priya has been sending money home to her parents in Kerala since she started working at the hospital in Manchester seven years ago. The amount changes depending on the month; the timing does not. Wednesday is payday; her parents plan around Thursday, which is when the transfer usually arrives after the bank processes it and the correspondent chain routes it through a clearing house and into the Indian banking system.
Seven years of Thursdays. Seven years of her mother calling on Wednesday evening to confirm it was sent, calling again Thursday morning to check whether it had arrived, and occasionally calling Thursday afternoon to say the balance had not updated yet and she was not sure whether to go to the market.
Remittances to low- and middle-income countries reached an estimated USD 685 billion in 2024 — more than foreign direct investment and official development assistance combined. The average cost of sending USD 200 was still 6.49% in Q1 2025.
— World Bank, Migration and Development Brief 2024; Remittance Prices Worldwide Issue 53, Q1 2025
On Wednesday at 4.30 p.m. — the end of the day shift — Priya opens the app and sends to her mother's Shandle. Her mother, in Ernakulam, gets a notification at 9 p.m. local time. She calls Priya at 9.02 p.m. Not to ask whether it arrived. To say thank you.
The Thursday morning call does not happen. Neither does the Thursday afternoon one. The money arrived the same day it was sent, and the week in Kerala can be planned around Tuesday rather than organised around the uncertainty of when the bank will clear a transfer that was already supposed to have happened.
This is not a story about technology. It is a story about a daughter and her mother not spending a day in a state of low-grade anxiety about whether a payment is going to arrive. That is what "instant" means in practice — not milliseconds, but a Wednesday that ends without the Thursday uncertainty attached to it.
Thursday: the restaurant owner in Mexico City
Carlos runs a small restaurant in Coyoacán. Most of his customers are local; on weekends, a significant share are tourists — Americans from Chicago and Houston, Europeans from Madrid and Amsterdam, visitors from across Latin America. Thursday is when he reconciles the week and pays his suppliers.
Two of his suppliers are in the United States. One sends him specialty chillies from New Mexico; the other supplies a non-alcoholic spirits brand that his weekend crowd has started asking for. Both suppliers invoice in US dollars. Carlos has been paying by wire transfer — a process that costs him a transfer fee per send, takes two to three business days to settle, and means he has to initiate the payment early in the week to guarantee the suppliers confirm receipt by Friday.
On Thursday, Carlos opens the app, generates two payment links — one for the New Mexico supplier, one for the spirits brand — and sends them in the same email he uses to confirm the next week's order. Both suppliers receive them, pay within the hour, and confirm the orders before Thursday afternoon in Texas and California. The goods ship on Friday. Carlos has the confirmation before the lunch service ends.
The suppliers do not ask when the wire will arrive. Carlos does not initiate a transfer on Tuesday to make sure it clears by Friday. The payment is the confirmation — sent, received, and acted on, inside the same Thursday morning.
Friday: the whole picture
Four people. Four corridors. Manila to New York, Accra to Istanbul, Manchester to Ernakulam, Mexico City to New Mexico. None of them think of their payment as a cross-border financial transaction. Janice thinks of it as getting paid for work she delivered. Kofi thinks of it as ordering inventory. Priya thinks of it as calling her mother. Carlos thinks of it as placing next week's order.
The payment infrastructure is invisible when it works. It becomes visible only when it fails — when the wire takes five days instead of one, when the fee is larger than expected, when the correspondent chain takes a cut nobody disclosed, when the call on Thursday morning is about whether the money arrived rather than about anything else.
The network Spondula is building is designed to make the infrastructure invisible again — not by solving a technical problem, but by making the payment feel like the message it was always supposed to be. Fast enough that the sender and the receiver do not have to plan around the gap. Cheap enough that the amount that arrives matches the amount that was sent. Simple enough that the payment is not its own administrative task, separate from the work or the relationship it is attached to.
Anyone. Anywhere. Anytime. Those three words are not a marketing claim. They are the description of a payment infrastructure that does not ask you to adjust your week around it.
What comes next for all four of them
Janice refers her studio partner in Cebu. Kofi refers his Istanbul supplier. Priya's mother in Ernakulam tells a neighbour whose daughter also works in the UK. Carlos mentions Spondula to the restaurant next door, whose owner serves the same American and European tourists and has the same supplier-payment problem.
The network grows because the payment arrived the same day. Not because of a referral incentive, not because of a marketing campaign — because one person had a payment experience that was different from the one they were used to, and the next conversation they had was about it.
That is how a network becomes a network. Not infrastructure first, then users. Users first, then infrastructure that is dense enough to make every new user's first experience as good as the one that brought them in.
Frequently asked questions
Can I really send money from the UK to India the same day?
Yes. Payments on the Spondula network settle in seconds, not business days. A send from Manchester to Ernakulam, or from London to Hyderabad, arrives in the recipient's wallet before the call confirming the send has ended. There are no cut-off times, no correspondent-bank windows, and no clearing delays. The balance is in the wallet the moment the sender confirms.
How does a business use Spondula to pay international suppliers?
Generate a payment link from the wallet — set to the invoice amount — and send it to the supplier in the same email as the order confirmation. The supplier clicks, pays from their Spondula wallet, and the balance lands instantly. No wire transfer form, no SWIFT code, no three-day wait for the payment to clear before the goods ship. The payment is the confirmation.
Is Spondula only for large amounts or specific corridors?
Spondula is built for everyday amounts on everyday corridors. A USD 120 invoice payment from New York to Manila, a GBP 80 family send from Manchester to Kerala, a USD 300 supplier deposit from Accra to Istanbul — these are the payments the network is designed around. There is no minimum send amount and no corridor-specific surcharge. The flat 0.2% spread applies to every send, at every scale.
What happens when the recipient does not have a Spondula wallet yet?
During the pre-launch period, both sender and recipient need a Spondula wallet to transact. The invitation flow is built into the network — sharing your Shandle or a payment link prompts the recipient to set up a wallet before the payment resolves. After the network opens for general access, onboarding takes minutes and the first payment can follow immediately after.
How is this different from existing transfer apps?
Spondula is a global money network — not a transfer app, a remittance service, or a digital wallet in the conventional sense. The distinction in practice: the sender and the recipient are on the same network, holding value in the same wallet infrastructure, able to pay and receive from any other user on the network without a separate "cash out" step for every transaction. A freelancer in Manila who receives a client payment can use that balance to pay a supplier, send money home, or hold it in a stable currency — all from the same wallet, without converting out and back in through a bank.
Spondula is pre-launch. The stories above describe what the network is built to make possible — not a future state, but the design intent, tested against real payment moments that real people navigate every week. If any of those moments describe your week, the waitlist is where the payment infrastructure gets better. One handle. Every corridor. The money arrives the same day.
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.
