> ## Documentation Index
> Fetch the complete documentation index at: https://api-docs-v3.openfx.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Settlement Times

> Submission cut-offs per fiat rail. Withdrawals submitted after the cut-off are processed the next banking day.

**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](/v3/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.

<Warning>
  **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.
</Warning>

## 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

<AccordionGroup>
  <Accordion title="USD — Fedwire, SWIFT" id="usd">
    | Rail    | `rail`    | Submission cut-off   | Notes                                            |
    | ------- | --------- | -------------------- | ------------------------------------------------ |
    | Fedwire | `FEDWIRE` | 4:30 PM ET (Mon–Fri) | US banking days only                             |
    | SWIFT   | `SWIFT`   | 5:00 PM ET (Mon–Fri) | Counterparty bank determines onward routing time |
  </Accordion>

  <Accordion title="EUR — SEPA, SEPA Instant, SWIFT" id="eur">
    | Rail         | `rail`  | Submission cut-off             | Notes                                            |
    | ------------ | ------- | ------------------------------ | ------------------------------------------------ |
    | SEPA         | `SEPA`  | 12:30 PM London time (Mon–Fri) |                                                  |
    | SEPA Instant | `SEPA`  | 24/7                           | Under €1M per transaction                        |
    | SWIFT        | `SWIFT` | 9:30 AM London time (Mon–Fri)  | Counterparty bank determines onward routing time |
  </Accordion>

  <Accordion title="GBP — FPS, CHAPS, SWIFT" id="gbp">
    | Rail           | `rail`  | Submission cut-off            | Notes                                                |
    | -------------- | ------- | ----------------------------- | ---------------------------------------------------- |
    | FPS (domestic) | `FPS`   | 24/7                          | Under £1M per transaction                            |
    | CHAPS          | `CHAPS` | 4:00 PM London time (Mon–Fri) | Used for higher-value or scheme-restricted transfers |
    | SWIFT          | `SWIFT` | 4:00 PM London time (Mon–Fri) | Counterparty bank determines onward routing time     |
  </Accordion>

  <Accordion title="MXN — SPEI" id="mxn">
    | Rail | `rail` | Submission cut-off | Notes |
    | ---- | ------ | ------------------ | ----- |
    | SPEI | `SPEI` | 24/7               |       |
  </Accordion>

  <Accordion title="AED — UAEFTS, SWIFT" id="aed">
    | Rail   | `rail`   | Submission cut-off     | Notes                                            |
    | ------ | -------- | ---------------------- | ------------------------------------------------ |
    | UAEFTS | `UAEFTS` | 24/7                   | under AED 50,000                                 |
    | UAEFTS | `UAEFTS` | 4:00 PM GST (Mon–Fri)  | AED 50,000 and above                             |
    | SWIFT  | `SWIFT`  | 10:30 AM GST (Mon–Fri) | Counterparty bank determines onward routing time |
  </Accordion>

  <Accordion title="AUD — NPP" id="aud">
    | Rail | `rail` | Submission cut-off | Notes |
    | ---- | ------ | ------------------ | ----- |
    | NPP  | `NPP`  | 24/7               |       |
  </Accordion>

  <Accordion title="BRL — PIX" id="brl">
    | Rail | `rail` | Submission cut-off | Notes |
    | ---- | ------ | ------------------ | ----- |
    | PIX  | `PIX`  | 24/7               |       |
  </Accordion>
</AccordionGroup>

## 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](/v3/supported-networks) for the per-stablecoin chain matrix.

<Note>
  The required confirmation threshold varies by network; the prose below
  describes the practical wall-clock impact rather than fixing a per-network
  number.
</Note>

<AccordionGroup>
  <Accordion title="EVM chains (Ethereum, Polygon, Arbitrum, Base, Optimism, Avalanche, BSC)">
    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.
  </Accordion>

  <Accordion title="Solana">
    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.
  </Accordion>

  <Accordion title="Tron">
    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.
  </Accordion>

  <Accordion title="Aptos">
    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.
  </Accordion>
</AccordionGroup>

<Tip>
  **You don't pick a rail on the request.** The rail is bound to the verified
  [withdrawal account](/v3/setup/verified-accounts). 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.
</Tip>

## What's next

<CardGroup cols={2}>
  <Card title="Withdrawal lifecycle" icon="arrow-up-from-bracket" href="/v3/withdrawal-lifecycle">
    State machine + polling pattern.
  </Card>

  <Card title="Supported networks" icon="network-wired" href="/v3/supported-networks">
    Stablecoin × chain matrix for crypto withdrawals.
  </Card>

  <Card title="Trade Settlement" icon="wallet" href="/v3/trade-settlement">
    The full deposit / balance / withdrawal model.
  </Card>

  <Card title="Idempotency" icon="repeat" href="/v3/idempotency">
    7-day TTL on withdrawal keys (carried forward from v2).
  </Card>
</CardGroup>