---
title: "How long does a stablecoin payout take? Settlement times by country and rail"
seoTitle: "How long does a stablecoin payout take?"
description: "Stablecoin payouts settle in minutes on Pix, SPEI, RTP, and Transfers 3.0, and in 1 to 5 business days on ACH, SEPA, and SWIFT. Full table by rail."
date: "2026-08-06"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "How long does a stablecoin payout take?"
    a: "The on-chain leg takes seconds to a couple of minutes. The total time depends on the local rail at the end: instant over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; about one business day over TED, wire, SEPA, and Colombian ACH; about two business days over US ACH; and up to five business days over SWIFT."
  - q: "Do stablecoin payouts work on weekends?"
    a: "On instant rails, yes. Pix, SPEI, and Transfers 3.0 run 24/7, so a payout sent on a Saturday night lands on a Saturday night. ACH, wire, SEPA, TED, and SWIFT follow banking days, so a weekend payout on those rails is delivered after the next business day opens."
  - q: "Why is my stablecoin payout on hold?"
    a: "A payout can sit in on_hold for compliance or banking review before release. At BlindPay every SWIFT payout starts in on_hold, and USD ACH, wire, and RTP payouts pass through it. Screening matches or unusual activity can also trigger a hold. A hold is a status, not an error, so show it as pending and do not retry."
  - q: "What is the fastest country to send a stablecoin payout to?"
    a: "Brazil, Mexico, and Argentina are among the fastest, because Pix, SPEI, and Transfers 3.0 settle in minutes, around the clock. In the US, RTP settles instantly, though USD payouts pass through a review step first."
  - q: "How long is a stablecoin payout quote valid?"
    a: "At BlindPay a payout quote is valid for five minutes by default and can be shorter for SEPA. Read expires_at from the response, which is in epoch milliseconds, rather than hardcoding the window."
---

A stablecoin payout takes as long as the local rail at the end of it. The on-chain leg settles in seconds to a couple of minutes. After that, the receiver gets funds instantly over Pix in Brazil, SPEI in Mexico, Transfers 3.0 in Argentina, and RTP in the US; in about one business day over TED, domestic wire, SEPA, and Colombian ACH; in about two business days over US ACH; and in up to five business days over SWIFT.

So "stablecoin payouts are instant" is half true. The stablecoin part is. The bank part is whatever the bank rail does.

Here's the full breakdown, with the rail-by-rail table, the steps that add time, and a few timelines you can reason about.

## What are the settlement times by rail?

These are the estimated times of arrival for BlindPay payouts, by the `type` you set on the receiver's bank account.

| Country | Rail | `type` | Estimated arrival | Runs 24/7 |
| --- | --- | --- | --- | --- |
| Brazil | Pix | `pix` | Instant | Yes |
| Brazil | PIX Safe | `pix_safe` | Instant | Yes |
| Brazil | TED | `ted` | ~1 business day | No |
| Mexico | SPEI | `spei_bitso` | Instant | Yes |
| Argentina | Transfers 3.0 | `transfers_bitso` | Instant | Yes |
| Colombia | ACH | `ach_cop_bitso` | ~1 business day | No |
| United States | RTP | `rtp` | Instant | Yes |
| United States | Domestic wire | `wire` | ~1 business day | No |
| United States | ACH | `ach` | ~2 business days | No |
| Europe | SEPA | `sepa` | ~1 business day | No |
| Global | SWIFT | `international_swift` | ~5 business days | No |

High transaction volumes can stretch any of these. SWIFT payouts have a 100 USD minimum and carry a UETR and an MT103 confirmation, so you can trace the wire. The live rail list is in the [bank accounts docs](/docs/bank-accounts).

## What happens between "send" and "arrived"?

A stablecoin payout is four steps. Only one of them is slow, and it's rarely the blockchain.

1. **Quote (you control this).** Request a quote, show the receive amount, confirm. A quote is valid for five minutes by default, sometimes less on SEPA.
2. **On-chain transfer (seconds to a couple of minutes).** USDC or USDT moves from the funding wallet. Fast networks like Base, Polygon, Solana, and Stellar confirm in seconds.
3. **Compliance and conversion (usually seconds, sometimes a review).** Screening runs on the payout. Most clear automatically. Some go to `on_hold`.
4. **Local delivery (the rail).** This is the number in the table above.

Add them up and a Pix payout is minutes end to end. A SWIFT payout is days, and nearly all of that is SWIFT.

## Why would a payout take longer than the table says?

Three reasons, in order of how often they show up.

**Cut-off times.** Banking rails have daily cut-offs. Submit after it and you're in the next business day's batch. In Eastern Time:

| Rail | Daily cut-off (ET) | Settlement after cut-off |
| --- | --- | --- |
| ACH | 9:00 PM | 1 to 3 business days |
| Same-Day ACH | 3:00 PM | Same business day |
| Domestic wire | 3:00 PM | Same business day |
| International SWIFT | 10:30 AM | Up to 5 business days |
| TED (Brazil) | End of Brazilian banking day | Same or next banking day |

Business days exclude weekends, US federal holidays, and applicable international banking holidays. The full reference is in [cut-off times](/docs/kb/cut-off-times).

**Compliance holds.** A payout can land in `on_hold` for review. At BlindPay, every SWIFT payout starts in `on_hold`, and USD ACH, wire, and RTP payouts pass through it too. Screening matches, unusually large amounts, and first-time activity can also trigger a hold. If compliance needs more information, it sends a request, and an unanswered request can end with the funds returned to the sender. Read [on-hold transactions](/docs/kb/on-hold-transactions) for how that works.

**Bad bank details.** A wrong account number or a closed account means the receiving bank rejects the payment. The payout ends `failed` or `refunded`. Stablecoin refunds go back to the originating wallet right away; fiat returns take as long as the receiving bank takes.

## What do real timelines look like?

A few scenarios. On USD and SWIFT payouts, review time comes on top of the rail time.

**Saturday, 11:00 PM, 5,000 BRL to Brazil over Pix.** Quote, send, done. Reais land in minutes. Pix doesn't care that it's Saturday.

**Tuesday, 2:00 PM ET, 20,000 MXN to Mexico over SPEI.** Minutes. SPEI runs around the clock too.

**Friday, 4:00 PM ET, 3,000 USD to a US bank account over domestic wire.** That's after the 3:00 PM wire cut-off, so it goes out Monday and settles the same business day, plus any review time.

**Friday, 4:00 PM ET, 3,000 USD over ACH.** Before the 9:00 PM ACH cut-off, so it's submitted Friday. About two business days means Tuesday, plus any review time.

**Wednesday, 9:00 AM ET, 25,000 USD to a supplier in Hong Kong over SWIFT.** Before the 10:30 AM cut-off, starts in `on_hold` for review, then up to five business days on SWIFT, depending on the correspondent chain. Track it with the UETR.

**Monday, noon, 2,000,000 COP to Colombia over ACH.** About one business day, so Tuesday.

## How does this compare with a traditional wire?

A SWIFT wire from a US bank to Brazil passes through one or two correspondent banks, each updating its own ledger and taking its own fee. That usually means 1 to 5 business days, and the receiving bank applies its own FX rate when the dollars arrive.

The same payment as a stablecoin payout over Pix settles in minutes, at a rate you saw before you sent it. For corridors with an instant local rail, the difference is days versus minutes. For corridors that still end in SWIFT, the difference is smaller on speed and bigger on traceability and quote certainty. We go deeper in [stablecoins vs SWIFT for B2B payments](/resources/more/stablecoin-vs-swift-b2b-payments), and on what "final" actually means in [stablecoin API SLAs and settlement finality](/resources/more/stablecoin-api-sla-settlement-finality).

## How should your product show payout timing?

A few things that save support tickets:

- **Show the ETA per rail, not per provider.** "Arrives in minutes" for Pix, "about 2 business days" for ACH.
- **Treat `on_hold` as pending.** Don't retry, don't show an error. It resolves to `processing`, `completed`, `failed`, or `refunded`.
- **Listen for webhooks.** `payout.update` fires on every status change, including `failed`, and `payout.complete` fires when local currency is delivered.
- **Read `expires_at` from the quote.** It's in epoch milliseconds. Don't hardcode five minutes.
- **Store the rail reference.** On SWIFT, keep the UETR; your finance team will ask for it.

The full integration flow, with endpoints and statuses, is in [how to integrate a stablecoin API](/resources/more/how-to-integrate-a-stablecoin-api).

## Where does BlindPay fit?

[BlindPay](/global-payments) pays out USDC and USDT as local currency over every rail in the table above, with [no pre-funding](/resources/more/no-pre-funding-stablecoin-payouts), a quote that locks the receive amount before you commit, and compliance screening inside the API. Payouts start from your own stablecoin wallet or from a [virtual USD account](/virtual-accounts) that converts ACH, wire, and SWIFT deposits into stablecoins. Rails cover Brazil, Mexico, Colombia, Argentina, the US, Europe, and 100+ countries over SWIFT (POBO/COBO). [Pricing is published](/pricing).

## What to do next

List your top three payout countries and look up each rail in the table. If any of them has an instant rail, that's the corridor to launch first. Then create a development instance, run a test payout, and use the sentinel amounts `66600` and `77700` to force `failed` and `refunded` so your UI handles the slow paths before real users hit them.

*This article is for general information only and is not legal, tax, or financial advice.*