How long cross-border payments actually take to settle
Your customer's card is authorised in about two seconds. The money can still take the better part of a week to arrive. The gap is not the payment network being slow — it is the number of companies that have to agree before anyone moves funds.
If you sell software to customers in other countries, you have probably noticed that your dashboard and your bank statement disagree. The dashboard says a payment succeeded on Tuesday. The bank shows it the following Monday. Nothing failed in between. That week is normal, and understanding where it goes is the difference between accepting it and fixing it.
Authorisation is not settlement
Two different things happen when someone pays you, and they are often confused.
Authorisation is a question: does this customer have the funds, and does the issuer approve this charge? That round trip takes a couple of seconds. When your checkout shows a green tick, authorisation is what succeeded.
Settlement is the movement of actual money from the customer's bank, through a chain of intermediaries, into your account. That is the part measured in days.
Most merchants build their mental model around the first and plan their cash around the second, which is where the frustration comes from.
Where each day goes
The acquirer's batch window
Card payments are not sent one at a time. Your acquirer collects the day's authorisations and submits them as a batch, usually once daily at a fixed cut-off. A payment that arrives just after the cut-off waits for tomorrow's batch. This alone explains why two payments made hours apart can settle a day apart.
The correspondent banking hop
If the money has to cross a border as fiat, it usually travels through a correspondent bank — an institution that holds accounts for both sides. Correspondent banking is a relationship business running on business days and cut-off times. It does not work weekends. It does not work through either country's public holidays.
This is the single largest source of variance. A payment made on a Thursday before a long weekend in either country can sit untouched for four days before anyone looks at it.
Foreign exchange
Somewhere in the chain the currency converts. Depending on the provider this happens at capture, at payout, or on a schedule. If conversion is batched daily and the payout file runs after conversion, you have added another cycle.
Risk holds
New merchants, unusual volume patterns, or a spike in a market you have not sold to before can all trigger a hold. These are not announced in advance and they are the reason settlement timelines that normally look predictable occasionally do not.
Worth measuring in your own data: take 90 days of payments, calculate the hours between authorisation and the credit appearing in your bank, and look at the distribution rather than the average. The average will look tolerable. The tail is what breaks your cash planning.
What this costs
There is a simple way to size it. A gateway that settles in five days is holding roughly a sixth of a month's international revenue at any given moment — your monthly volume divided by thirty, multiplied by the settlement days.
For a business doing $250,000 a month from abroad on five-day settlement, that is around $41,000 permanently in transit. Not lost, but never available. It cannot pay for ad spend, contractor invoices or payroll. If you are growing, the amount in transit grows with you, so the drag never goes away.
The cost is not the fee you can see on the invoice. It is the working capital you never have.
Why some routes are genuinely faster
Two things actually compress the timeline.
Collecting locally. If the payment is collected by a licensed entity inside your customer's country, it never crosses a border as a card transaction. It becomes a domestic payment — Pix in Brazil, UPI in India, an instant bank transfer in Europe — which clears in seconds on rails that run continuously.
Removing the correspondent hop. The remaining problem is moving value from that country to yours. Doing this over rails that settle continuously, rather than through correspondent banking, removes the business-day constraint. This is the practical reason stablecoin settlement exists in payments infrastructure: not ideology, but the fact that the rails do not close on Saturday.
Put together, the payment is collected domestically, converted at a known rate, and paid out domestically on your side. The cross-border part never touches a system that only runs business hours.
Questions worth asking any provider
- Is settlement time quoted in business days or calendar days? The difference is substantial over a year.
- What is the daily cut-off, and in which time zone?
- Does the quoted time include or exclude the hold period for a new merchant?
- Is the exchange rate fixed at authorisation or at payout? If at payout, you carry the currency risk for the whole settlement window.
- What happens to timelines during public holidays in the customer's country?
- Can you see, per payment, the rate used and the bank reference it settled under?
That last one matters more than it sounds. If you cannot trace a bank credit back to the individual payments inside it, reconciliation becomes manual work that scales with your growth.
The short version
Cross-border settlement is slow because of the number of parties involved and the business hours they keep, not because moving money is technically difficult. Any approach that reduces the number of hops, or moves the cross-border leg onto rails that run continuously, compresses the timeline. Everything else is a negotiation about whose batch window you are waiting on.
Next: why the payment did not go through in the first place.
Why foreign cards get declined