Skip to main content
What this is. OpenFX submission cut-offs for fiat withdrawals, broken down by currency and rail. Use this page to figure out when a withdrawal needs to be in by, and which rail your withdrawal account targets. When it matters. Treasury operations, end-of-day reconciliation, batching withdrawals, or anywhere you need to know whether a submission will land “today” or roll to the next banking day. What you’ll learn. Cut-off times per rail, the rail-to-account binding, and how the cut-off interacts with the withdrawal lifecycle. The rail a withdrawal travels through is bound to the verified withdrawal account and reported as WithdrawalAccount.rail (e.g. FEDWIRE, SWIFT, ACH, SEPA, PIX, SPEI, FPS for fiat; a chain name for stablecoin). The cut-off tables below are organized by the rail’s display name; the rail value is noted alongside where it differs.
This page is informational and not an SLA. Submissions after the cut-off are processed the next banking day. Counterparty bank processing depends on the receiving bank’s hours, cut-offs, and holidays, which are outside OpenFX’s control. The cut-offs below describe OpenFX’s submission window only.

​
How to read these tables

  • Submission cut-off is the latest time OpenFX will dispatch a withdrawal to the rail on the same banking day. Submissions after this cut-off are queued and dispatched on the next banking day.
  • 24/7 means there is no cut-off. Submissions are dispatched continuously, including weekends and holidays unless a row says otherwise.
  • Notes call out per-rail constraints (transaction-size thresholds, holiday exclusions, etc.).

​
Fiat rails by currency

​
Stablecoin rails

Stablecoin withdrawals settle on-chain in minutes rather than against banking-hour cut-offs. Confirmation count and network congestion drive the wall-clock time. See Supported networks for the per-stablecoin chain matrix.
The required confirmation threshold varies by network; the prose below describes the practical wall-clock impact rather than fixing a per-network number.
Submission is 24/7. Settlement window is typically 1–5 minutes once OpenFX broadcasts the transaction; the exact time depends on network congestion and OpenFX’s required confirmation count per chain. Gas spikes on Ethereum can push confirmation past 10 minutes.
Submission is 24/7. Settlement typically completes within seconds of OpenFX broadcasting the transaction. Network-level outages are rare but reflected as an unsettled status until the cluster recovers.
Submission is 24/7. Settlement typically completes within 1–3 minutes once OpenFX broadcasts the transaction, after the required confirmation count. Stays unsettled until the confirmation threshold is reached.
Submission is 24/7. Settlement typically completes within seconds to a minute of OpenFX broadcasting the transaction. Stays unsettled until the network finalizes the transaction.
You don’t pick a rail on the request. The rail is bound to the verified withdrawal account. Pull GET /v3/fx/withdrawal-accounts to see which withdrawalAccountId targets which rail; the same currency (e.g. USD) can map to either Fedwire or SWIFT depending on how the account was set up.

​
What’s next

Withdrawal lifecycle

State machine + polling pattern.

Supported networks

Stablecoin × chain matrix for crypto withdrawals.

Trade Settlement

The full deposit / balance / withdrawal model.

Idempotency

7-day TTL on withdrawal keys (carried forward from v2).