A worker in Dubai finishes his shift at 11 p.m. on a Friday. He wants to send money to his family in Kerala before the weekend — the school fees are due on Monday and he told his wife it would be there before the weekend. He opens his bank app and initiates the transfer. The confirmation message tells him the transfer will be processed on the next available business day. In the UAE, Friday is a working day. In India, Sunday is not. The money will be processed Monday, arrive Tuesday at the earliest.
The school fees were due on Monday. The money arrives Tuesday. The family borrows from a neighbour to cover Sunday evening, and pays the school on Monday morning with an apology.
This is not a technology problem. The technology to move a payment from Dubai to Kerala exists and has existed for years. It is an infrastructure problem — the legacy scheduling of a payments system built around banking hours and clearing windows, applied unchanged to a world where the people sending money work nights, weekends, and hours that do not align with any single country's business calendar.
Why cut-off times exist — and why they do not have to
SWIFT cut-off times exist because SWIFT is a messaging network, not a settlement network. The message that a payment has been initiated travels instantly. The actual movement of value between institutions happens during specific windows, coordinated between correspondent banks, each operating on the schedule of its own central clearing infrastructure. A payment initiated at 4 p.m. in London on a Thursday may not clear in Lagos until Monday because the correspondent chain includes at least one institution that closes for the weekend and does not process inbound instructions until the next business day.
As of the BIS CPMI's 2024 monitoring survey, only 35% of global cross-border retail payments are credited within one hour of initiation, against a G20 target of 75% (BIS, 2024 cross-border payments monitoring survey, 2025). That 35% is not randomly distributed — it reflects corridors with modern bilateral infrastructure between well-connected banking systems. The corridors that matter most for remittance senders — Gulf to South Asia, UK to West Africa, US to Latin America — are disproportionately in the other 65%.
The Spondula network does not have clearing windows. It does not have correspondent-bank schedules. It does not have cut-off times. A payment initiated at 11 p.m. on a Friday settles in the recipient's wallet at 11 p.m. on a Friday. Not on Monday. Not the next business day. Now.
Only 35% of global cross-border retail payments are credited within one hour of initiation — against a G20 target of 75%. The gap is not a technology failure. It is the persistence of legacy scheduling in an infrastructure that was built for institutions, not for the people sending money on Friday nights.
— BIS, 2024 cross-border payments monitoring survey, 2025
What "anytime" means for the people who actually send
The people who send money across borders are not sending during business hours in the sending country. They are sending when they have a moment — after a shift, on a lunch break, on a Sunday when the family back home has called with something urgent. The gap between when a sender can initiate a transfer and when a traditional bank will process it is not a minor scheduling inconvenience. It is the design flaw that turns a Friday evening decision into a Tuesday arrival.
A nurse in Manchester finishes her night shift at 7 a.m. on Saturday and opens the app to send her monthly contribution to her parents in Chennai. On the traditional rail, a Saturday morning initiation may not clear until Tuesday in India. On Spondula, the GBP-S she sends is in her parents' wallet before she has made herself breakfast. Not because the network is clever. Because the network does not have a concept of business hours. Every hour is a banking hour.
A Kenyan worker in Qatar who sends money on the 1st of every month regardless of what day it falls on does not have to calculate whether the 1st is a Friday (processing Monday, arrival Wednesday) or a Tuesday (processing same day, arrival Thursday). The Spondula send arrives the same way on the 1st of January as it does on the 1st of August. The calendar is irrelevant to the network.
Bank holidays, weekends, and the week's worst timing
The moments when money is most urgently needed are rarely Tuesday at 2 p.m. They are Sunday evenings before a school week starts. They are bank-holiday weekends when something has gone wrong at home. They are the evening before a payment is due, when the sender realises the transfer initiated on Friday will not land until after the deadline.
Bank holidays in the sending country do not delay a Spondula payment. Bank holidays in the receiving country do not delay a Spondula payment. The network settles peer-to-peer, without routing through an institution that closes for national holidays in either country. A sender in the UK sending on Boxing Day is not waiting for the British banking system to reopen. The recipient in Lagos does not wait for the next Nigerian clearing window.
This is not a niche use case. It is the normal timing of the people who most rely on cross-border payments — shift workers, gig economy workers, overseas workers on fixed send schedules that do not adjust for public holidays. The "anytime" in Spondula's design brief is not a marketing claim. It is a design specification derived from the reality of when those people actually send.
The same speed, every corridor
The speed is not corridor-dependent. A payment from the UK to Kenya is not faster than a payment from the UK to Pakistan. A payment from the UAE to India is not slower than a payment from the UAE to the Philippines. The peer-to-peer settlement happens at the network level, at the same speed, on every corridor the network supports.
The worker in Dubai who initiates a payment at 11 p.m. on a Friday is not asking for a special service. He is asking for the school fees to arrive before Monday. On the Spondula network, they do. That is what "anytime" is for.
Spondula is pre-launch. If your sending schedule does not align with traditional banking hours — because you work nights, because you send at the weekend, because you live in a different time zone from your family — the waitlist is where the sending infrastructure catches up to your life, not the other way around.
Frequently asked questions
Can I really send money at midnight on a Sunday and have it arrive the same night?
Yes. Spondula payments settle in seconds regardless of the time of day or day of the week. There are no cut-off times, no weekend holds, and no next-business-day processing windows. A payment initiated at midnight on a Sunday arrives in the recipient's wallet at midnight on a Sunday.
Does a bank holiday in the sending country delay the payment?
No. Spondula settles peer-to-peer on the network — it does not route through national clearing systems that observe public holidays in either the sending or receiving country. A bank holiday in the UK does not affect a payment from London. A public holiday in Nigeria does not delay a payment arriving in Lagos.
Is the settlement speed the same on all corridors?
Yes. Payments settle in seconds across every corridor the Spondula network supports. The destination country does not affect the speed — a payment from Manchester to Nairobi settles in the same time as a payment from Manchester to Mumbai or Manchester to Manila.
What if the recipient is asleep when the money arrives?
The balance waits in their wallet. A payment that arrives at 3 a.m. local time in the receiving country is in the recipient's wallet when they wake up — not pending, not processing, already settled. They receive a notification when it lands; if they are asleep, they see it in the morning with the full amount already there.
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.
