.jpg)
Quick Answer
The Four Stages of Every Cross Border Payment
A transfer is not one action. It is four, and each one has its own clock.
Instruction. The sender authorises the payment. This is instant in an app and slower in a branch, where a clerk has to key the details and a supervisor may need to approve anything above a threshold.
Message. The sending bank builds the payment message. On SWIFT that means a formatted instruction with the beneficiary's name, account, bank identifier and purpose. On a domestic scheme such as Faster Payments or SEPA it means a structured credit transfer message. A missing or mismatched field stops the process here, before any money moves.
Settlement. Funds move between banks. On a domestic real time scheme this happens in seconds. On SWIFT it happens when the correspondent banks in the chain each debit and credit their own accounts, which is why the same payment can take one day on one corridor and four on another.
Credit. The beneficiary bank receives the funds and posts them to the customer account. Some banks credit immediately. Others hold incoming foreign currency payments for a manual check, particularly on first payments or amounts far outside the account's normal pattern.
Understanding these four stages explains most of the frustration people feel. The money is not lost. It is sitting at a specific stage, and each stage answers to a different institution.
Transfer Times by Rail
Different rails are built for different jobs. The table below shows what to expect on a normal business day, before any review or error.
| Rail | Typical timing | Usual use | Notes |
|---|---|---|---|
| UK Faster Payments | Seconds to minutes | UK domestic, up to scheme limits | Works 24 hours a day, every day |
| SEPA Credit Transfer | Same day to next business day | Euro payments across the EU and EEA | The scheme requires arrival by the end of the next business day |
| SEPA Instant | Under 20 seconds | Euro payments between participating banks | Participant coverage still varies by country |
| US ACH | One to three business days | US domestic batches and payroll | Same day ACH exists but is not universal |
| Fedwire and CHAPS | Same day | High value domestic payments | Cut off times are strict and fees are high |
| SWIFT | One to five business days | Cross border payments in most currencies | Each correspondent hop adds time |
| Card funded transfer | Minutes, sometimes hours | Small urgent amounts | Treated as a card transaction, with card rules |
The European Payments Council publishes the SEPA rulebooks behind those timings, and the scheme deadlines are firm rather than aspirational. The comparison with retail banking is blunt: a branch initiated international wire on the same corridor rarely matches a scheme payment for speed, and it costs more. DapsyPay routes payments on these conventional schemes instead of sending everything through one legacy pipe.
The pattern is consistent. The closer the sender and receiver are to the same payment scheme, the faster the payment. Speed falls as the chain lengthens, because every additional institution applies its own cut off, screening and processing routine.
Why SWIFT Payments Take Longer
SWIFT is a messaging network, not a settlement system. It carries the instruction between banks. The actual money moves through correspondent accounts, and that is where the time goes.
A payment from a small bank in one country to a small bank in another may pass through two intermediaries before it reaches the beneficiary. Each intermediary receives the funds, checks them against sanctions and anti money laundering rules, applies its own charges and forwards the balance. If the payment arrives after that bank's cut off, it waits until the next business day.
There are three practical consequences.
- Each hop adds between a few hours and a full business day. A two hop payment can easily take three days even when nothing is wrong.
- Charges are deducted along the way when the sender chooses the shared charge option, so the beneficiary receives less than the amount on the instruction.
- Screening can pause a payment without notice. A name that matches a watchlist entry, even loosely, sends the payment to a manual queue.
SWIFT's own data shows that most payments on its network reach the beneficiary bank within 24 hours, but a long tail remains, and that tail is what people remember. The Bank of England's payment and settlement guidance makes the same point from the settlement side: finality depends on the scheme and the institutions involved, not on the message alone. A provider that owns more of the chain, as DapsyPay does on its supported corridors, has fewer institutions to wait on.
For businesses, the useful number is not the average. It is the worst realistic case on your specific corridor.
Cut Off Times, Weekends and Public Holidays
Cut off times are the single most misunderstood part of transfer timing.
A payment instructed at 4pm on a Friday is not a Friday payment. On most rails it enters the queue and starts processing on Monday, and if Monday is a public holiday in the sending country, on Tuesday. Currency specific schemes add another layer, because the sending and receiving countries rarely share a holiday calendar.
Three rules cover most situations.
- The sending cut off decides the value date. Ask your provider for the exact local time, not a general description.
- The receiving country's business day decides credit. A payment that settles on Friday afternoon in London may not be credited until Monday in a market that has already closed.
- Weekend work is the exception, not the rule. Faster Payments, SEPA Instant and some card rails run continuously. ACH, Fedwire, CHAPS and most SWIFT corridors do not.
This is why two transfers sent minutes apart can land days apart. One crossed a cut off and the other did not.
Where Delays Actually Come From
When a transfer is late, the cause is usually one of six things. The table below is the checklist worth running before you call anyone.
| Cause | Typical added time | How to spot it |
|---|---|---|
| Sent after cut off | One business day | Value date is later than the instruction date |
| Missing or wrong beneficiary detail | One to five days, sometimes a return | Payment status shows held or rejected |
| Name mismatch on the account | One to three days | Beneficiary bank requests clarification |
| Compliance or sanctions review | Two to ten days | Status shows under review with no further detail |
| Intermediary bank charges or routing query | One to two days | Amount received is short, or funds sit at a correspondent |
| Public holiday in either country | One to two days | Timing lines up with a known holiday |
The most expensive delays are the ones caused by details. A transposed digit in an account number, a missing sort code, a beneficiary name that does not match the account exactly, or an IBAN that belongs to a different branch will all stop a payment. Recovery is possible but slow, and on some rails the funds have to come back before they can be sent again.
How to Make an International Transfer Land Faster
Speed is mostly a design decision, not a negotiation.
Match the rail to the corridor. If both sides hold euro accounts, use SEPA rather than SWIFT. If both sides are in the UK, Faster Payments beats an international wire. If the payment is to a country with a strong local scheme and your provider supports local delivery, use that.
Send before the cut off, in the receiving country's time zone. This sounds obvious and is missed constantly by finance teams working across time zones.
Give complete, verified details. Confirm the beneficiary name, account number, bank identifier and, where relevant, the purpose code. Send a small test payment first when the relationship is new or the amount is large.
Avoid the shared charge option for supplier payments. If the invoice must be settled in full, choose the charge option that guarantees the full amount arrives, and budget for the fee instead of discovering a shortfall later.
Keep documents ready before you send. A payment that triggers a review without supporting documents loses days. A payment that arrives with a contract, invoice and clear purpose description usually does not.
Use a provider that delivers directly. Every intermediary in the chain is another queue. Direct delivery to the beneficiary bank removes hops and removes the deductions that come with them.
What the Receiving Side Sees
Senders often assume the beneficiary can see the same status they can. Usually they cannot.
The beneficiary sees either funds in the account or nothing. They cannot see that the payment cleared the sending bank, that it is sitting with a correspondent, or that it is waiting for a name check. This information gap is why so many supplier relationships become tense over a payment that is genuinely in progress.
Two habits fix it. Send the payment reference and the expected value date to the beneficiary as soon as the payment is authorised. Then send the confirmation or receipt once the sending bank has accepted it. A supplier who knows the expected date asks fewer questions, and a supplier who can see a reference can match the payment when it lands.
Bulk and Business Payments
Single payments are only half the problem. A business paying thirty suppliers, a payroll run across four countries or a tuition batch for a cohort of students faces the same timing rules multiplied by the number of beneficiaries, and one failed line can delay an entire run.
Most banks handle this by batching, which improves cost but can push every payment to the slowest common denominator. A single missing detail in a batch often holds the whole file rather than one line.
DapsyPay is built for this pattern. Payments run on conventional rails such as SEPA and ACH, deliver directly to beneficiary bank accounts, and carry no limits on amount, which matters when a supplier balance or a property completion sits outside a retail transfer cap. Fees are shown before the payment is confirmed, so the amount that leaves is the amount the recipient receives, and bulk runs move as one instruction rather than thirty separate branch requests.
The comparison is worth making explicitly. The World Bank's work on payment systems and remittances has documented for years how much of the cost of a cross border payment is hidden in the exchange rate margin and intermediary deductions rather than the headline fee. A provider that quotes the all in cost before you send removes that uncertainty. Banks and traditional operators are improving, but the gap between a quoted fee and a received amount remains the most common complaint in business payments.
Where speed is the priority, direct rail delivery and a clean instruction do more than any escalation. Where cost is the priority, comparing the amount that actually arrives is the only comparison that matters.
Common Mistakes That Add Days
- Sending to an account name that does not match the bank record. The beneficiary bank will query it, and the query process is slow.
- Using the wrong identifier. IBAN, account number, sort code, routing number and SWIFT code are not interchangeable.
- Ignoring the purpose code. Some corridors require it, and a missing code sends the payment to a manual queue.
- Assuming a weekend counts as a business day. It does not, on most rails.
- Splitting a payment to avoid a limit. This creates multiple reviews and can look like structuring, which is a compliance red flag.
- Not telling the beneficiary what to expect. The payment may land while they are convinced it has failed.
FAQ
Conclusion
Transfer timing is not a mystery once you separate the four stages: instruction, message, settlement and credit. Each rail has a normal range, each provider has a cut off, and each intermediary adds a queue. The payments that arrive on time are the ones with complete details, correct identifiers, a realistic rail choice and a sender who understands the receiving country's calendar.
Choose the rail that matches the corridor, send before the cut off, verify the beneficiary before the first payment, and keep the documents ready. Those four habits remove most of the delay that businesses blame on banks.
Related Guides
- What Is a Shipping Bill and Why Do Exporters Need One
- How to Apply for a Medical Visa
- Is It Better to Exchange Currency Abroad
Move Business Payments Without a Cap
Send supplier balances, tuition and invoices on conventional rails such as SEPA and ACH, with no limits, the fee shown before you confirm and direct delivery to the beneficiary account.
Visit dapsypay.com