A driver in Manila finishes a shift late on Friday. The work is done. The payout has been approved. On the sender's dashboard, the money may already look as if it has left.

For the driver, none of that answers the question: When will I actually get it?

Cross-border payments take so long because the instruction and the money often pass through several institutions, operating schedules, data checks, and local banking windows before reaching the recipient. A transfer can be moving exactly as designed and still take days. That may be normal for the system. It isn't normal for the person waiting.

‍

Why do cross-border payments take so long?

‍

Most delays come from the way the payment is assembled, not from the distance the money travels. The internet can carry an instruction around the world almost instantly. The banking process behind that instruction may still depend on intermediaries, batches, manual review, and operating hours that stop at borders.

A payout can be released on Monday, checked on Tuesday, passed onward Wednesday, and delivered after a local bank's next processing window. Each step may be reasonable on its own. Together, they create a relay race where nobody owns the finish time.

The Bank for International Settlements identifies limited operating hours, legacy technology, long transaction chains, and fragmented data as recurring cross-border payment frictions.[3]

The problem isn't that money cannot move quickly across borders. It is that too many payout systems are designed without anyone being accountable for how quickly it reaches the person who earned it.

‍

Why do correspondent banks slow a payment down?

‍

Correspondent banking slows a payment when the sender's bank cannot reach the recipient's bank directly and must pass the transfer through one or more intermediaries. Each institution receives an instruction, runs its own controls, updates its own ledger, and sends the payment onward.

The chain can be short. It can also involve several banks, especially when a currency or destination market is less directly connected. The sender sees one payment. Operationally, there may be several handoffs underneath it.

Those handoffs create waiting time. One bank may need clarification. Another may hold the payment for review. A third may process the incoming instruction in its next window. No single institution necessarily controls the whole route or the final delivery time.

‍

Why does batch processing delay payouts?

‍

Batch processing delays payouts because transactions wait for a scheduled processing run instead of moving as soon as they are ready. Many older payment systems were built to collect instructions and release them together at set times.

That made sense when moving large files at predictable intervals was the practical way to operate. It still suits a sender that wants to approve thousands of payouts in one run. The recipient experiences something else: money earned now, held until the next file closes.

Miss one processing window and the delay may be measured in hours. Miss a Friday window and the wait can spill into Monday. Add a public holiday in either country and the calendar stretches again.

‍

How do bad account details make a payout slower?

‍

Bad account details make a payout slower when the error is discovered only after the transfer has entered the payment chain. A mistyped account number, a name that doesn't match, or a routing detail formatted for the wrong market can travel surprisingly far before the receiving institution rejects it.

Then the money has to come back. Someone must identify the problem, contact the sender or recipient, correct the data, and try again. A small input error becomes a multi-day round trip.

This is one of the most avoidable causes of payout delay. The useful check is the one that happens before release, while the information can still be corrected without moving money anywhere.

‍

How do time zones and cutoff times add days?

‍

Time zones and cutoff times add days when one institution releases a payment after the next institution has stopped processing for the day. A transfer sent during business hours in Los Angeles may arrive after the relevant window has closed in Manila.

The instruction waits until the next local business day. If another intermediary is involved, the same thing can happen again. Weekends and holidays don't line up neatly across markets, either. A route that crosses several operating calendars can accumulate a day at a time without anything technically going wrong.

This is why estimates such as "two to three business days" can feel slippery. Whose business day? Which cutoff? Which holiday calendar? The payee is given a range, while the payment is governed by a sequence of clocks they cannot see.

‍

What does a three-day payout delay cost a worker?

‍

For a worker without a financial cushion, a three-day payout delay can mean borrowing, postponing a bill, or declining the next job because today's expenses cannot wait. Commonwealth found that more than 40% of gig workers in its Financial Benefits Project pre-pilot had no savings at all, while roughly 70% to 80% had $1,000 or less.[1]

That changes the meaning of "in transit." The driver in Manila may need fuel before the next shift. Rent doesn't move because an intermediary missed a cutoff. Neither does a school payment or a grocery run.

The demand for speed is not subtle. Visa reported that 80% of more than 2,500 online gig workers surveyed across 13 countries would be willing to pay a small fee for instant cross-border payouts.[2] They are offering to buy back access to money they have already earned.

For the platform making the payout, the same delay becomes a trust problem. Workers ask support where the money is. Some turn down more work until the first payment lands. The operational delay reaches back into retention and growth.

‍

How can cross-border payouts move faster?

‍

Cross-border payouts move faster when the provider prevents avoidable failures, chooses the quickest workable route for the corridor, and manages delivery as one continuous outcome. That starts before release.

Account details should be checked against the requirements of the destination market while they can still be corrected. Routing should reflect the rail that is actually fast for that currency and corridor, rather than sending every payment through the same default chain. Both sender and recipient should be able to see enough progress to resolve an exception before it turns into days of silence.

MassPay applies that model through a direct global payout network. We validate account details before money moves, then route each payout toward the appropriate last-mile connection for the destination. Direct relationships with banks and delivery partners reduce the number of parties standing between release and receipt.

That doesn't mean every cross-border payout is instant. Corridor rules, compliance reviews, destination institutions, and local operating hours still matter. It does mean speed is treated as an end-to-end responsibility, not a promise handed from one intermediary to the next.

‍

As we wrote in Built for the Person Getting Paid, a payee should not be treated as a delivery address. The work starts with the person who earned the money. The obligation is to get it to them on time.

‍

Speed is only one question a payee asks. The others deserve their own answers. But this one is simple: if the work is complete, the payment system should not add days merely because its handoffs, files, and clocks were designed around someone else.

‍