Frequently asked questions

They're built from the rules the networks publish: cutoffs, settlement windows, weekend rules and holiday calendars, evaluated in each rail's home time zone. What no outside tool can see are your bank's private risk holds and manual compliance reviews, so every estimate is a window (earliest, typical, latest-normal) rather than a single promise, and lists the factors that could push it later. The methodology spells out every assumption.

You never enter any: no amounts, no account numbers, no names. And there's no server to send anything to: the entire engine runs in your browser. Estimates are encoded in the URL fragment (the part after #), which browsers never transmit to servers. The privacy policy is four paragraphs because that's all there is to say.

ACH & Same Day ACH, RTP, FedNow, Fedwire wires, push-to-card and card refunds (US); SEPA Credit Transfer, SEPA Instant and SEPA Direct Debit (EU); Faster Payments, CHAPS and Bacs (UK); SWIFT priority and economy (international); PIX, UPI, Interac e-Transfer, NPP/Osko; and same-app wallet transfers. Each has a guide.

Batch rails settle only on weekdays that aren't holidays on that rail's calendar: Federal Reserve holidays for US rails, TARGET closing days for SEPA, UK bank holidays for UK rails. The calculator computes those calendars algorithmically for any year, so a transfer sent before Easter or Thanksgiving gets the right, longer answer automatically.

Usually one of three things: the receiving bank isn't on the instant rail, so your payment silently fell back to ACH; a real-time fraud check flagged it for review; or the app's own limit forced slower routing. Instant rails themselves settle in seconds, so if it's been more than a few hours, contact the sending institution. More in the RTP/FedNow guide.

Free, no account, no paywall. Five of our guide pages carry a clearly-labelled partner link to a money-transfer service, Remitly, and we may earn a commission if you use it to send money, at no extra cost to you. We tell you to compare it against your own bank; we are not paid to place it. Partner links never appear inside the calculator, never affect the math, and never change which rail a guide describes. Neutral guidance always sits above them, including telling you to use a free option where one exists: the SEPA guide says plainly that inside the euro area SEPA Instant is free and nothing will beat it. The engine's rules sit unminified in the page source for anyone to audit.

"Add to calendar" generates a standard .ics file in your browser and downloads it. Nothing is uploaded anywhere. Import it into Google Calendar, Apple Calendar, Outlook or anything else: you get an event spanning the arrival window, with a 30-minute heads-up alarm.

No, and be wary of any site claiming it can; only the banks in the chain can see your payment. What we give you is the realistic schedule it should follow, and the escalation route if it doesn't: for SWIFT, ask your bank to trace the UETR; for card refunds, ask the merchant for the ARN.

Use the latest (normal) edge of your estimate. Before it, waiting is normal and checking hourly changes nothing. Past it: contact the sending bank first. They own the payment until it lands. Have the exact amount, date and reference ready and ask for a trace. Domestic transfers 2+ business days past the window, or international 5+, deserve a formal trace request.

Because an exact time would be a lie. Settlement is predictable; the final posting to your account depends on the receiving bank's internal schedule. A window with a typical anchor is the most honest answer that's still useful, and it's how treasury teams think about payment timing too.