A calculator that shows its work
Most "how long does a transfer take" pages give you a range and a shrug. Transfereta computes your specific window from the rules the networks actually publish, and tells you exactly which assumptions it made.
Cutoffs in the rail's own time zone
ACH cutoffs live in US Eastern time. SEPA's live in CET. CHAPS' in London. Your send time is converted to the rail's home zone (DST handled by your browser's own IANA time-zone database) before any cutoff comparison happens. Sending from Vilnius, Sydney or São Paulo changes the math, and we do that math.
→ 09:30 EDT (rail time)
→ before 5:00 PM ET cutoff ✓
→ enters today's processing
Holiday calendars that never go stale
US Federal Reserve holidays, Eurosystem TARGET closing days and UK bank holidays are computed algorithmically for any year: nth-weekday rules, observance shifts, and Easter via the Meeus algorithm. No hardcoded tables to expire. One-off proclamation holidays (a royal funeral, say) are the single known exception.
Good Friday → Mar 26
TARGET closed → settlement
slides to Tue Mar 30
Windows, not wishful numbers
Every estimate gives you three anchors: earliest (everything goes right), typical (the posting pattern most banks follow), and latest-normal (the point past which something is actually wrong and worth a phone call). Plus the step-by-step timeline of where your money is between those anchors.
typical · Tue 9:00 AM
latest · Wed 5:00 PM
past that? → call the bank
The rail status board
The board on the homepage answers the question behind the question: is this rail even open right now? Batch rails show OPEN with today's cutoff, or CLOSED with the next processing cycle. Instant rails show 24/7, because they are. All of it is computed locally from published operating schedules, not from live bank data.
SEPA Instant ● 24/7
Bacs ● CLOSED · next Mon
Share links and calendar files
Every estimate has a copyable link: the whole calculation is encoded in the URL fragment, which never reaches any server. And "Add to calendar" downloads a standard .ics file with the arrival window and a 30-minute heads-up alarm, generated entirely in your browser.
↳ opens to this exact estimate
eta.ics → any calendar app
Advanced: your bank's real cutoff
Network cutoffs are ceilings; your bank's own deadline is what actually gates your payment. If you know it, set it in the advanced options and the whole timeline recalculates around it.
sent 2:15 PM
→ tomorrow's batch, honestly
What we model, and what we don't
Modelled: network cutoffs and settlement windows (in rail-native time zones), weekend rules, US Federal Reserve / TARGET / UK bank holiday calendars, business-day settlement lags, typical receiving-bank posting windows, Same Day ACH's three windows and availability deadlines, the Bacs 3-day cycle, and SWIFT routing-quality tiers.
Not modelled, by honest necessity:
- Your bank's private risk rules: first-transfer holds and manual compliance reviews are invisible from outside; the delay factors on each estimate tell you when they're likely.
- Destination-country holidays on SWIFT routes: with 190+ national calendars, we'd rather flag it than fake it.
- One-off proclamation holidays: algorithmic calendars can't predict a state funeral.
Where routing genuinely varies (SWIFT, card refunds), the estimate carries a medium confidence tag instead of pretending precision. Sources for the underlying rules: Nacha's published Same Day ACH schedule, the Federal Reserve's Fedwire operating hours, the EU Instant Payments Regulation, the EPC SEPA rulebooks, Pay.UK scheme documentation, and SWIFT's gpi speed reports. Every rule ships in engine.js, readable and unminified. If we've got something wrong, tell us and we'll fix it.
Every rail at a glance
Cutoffs shown are typical bank cutoffs in the rail's home time zone; your bank may be earlier.
| Rail | Typical speed | Cutoff(s) | Calendar |
|---|---|---|---|
| Enable JavaScript to render the live cheat sheet. | |||