Skip to content

Payment settlement time: how long does money take by payment method?

How long ACH, wires, RTP, FedNow, Pix, SPEI, SEPA Instant and SWIFT take, with the difference between authorization, settlement and availability.

Payment settlement time depends on the rail, not the amount. Instant rails such as RTP, FedNow, Pix, SPEI and SEPA Instant are built to confirm in seconds, around the clock. ACH and wires follow business days and bank cut-offs. SWIFT payments often take several business days to reach the recipient's account.

This guide covers how long money takes by method, as of November 2026, and separates initiation from availability. It builds on our deeper look at stablecoin payout settlement times and links to the rail guides for ACH and real-time rails. For the end-to-end cross-border picture, see cross-border payments explained.

Key takeaways

  • Authorization, settlement and availability are three different moments. Quoted "payment times" often mean only one of them.
  • Instant rails are available 24 hours a day, every day. ACH and wires follow business days, batch windows and cut-offs.
  • Cross-border delay sits mostly in the last mile. About 90% of Swift payments reach the destination bank within an hour, but 43% reach the end customer in that time (Swift 2024 data).
  • The fastest cross-border setup uses the fastest local rail in each destination, with SWIFT kept for countries that need it.
  • Ask every provider for the settlement time per rail and per direction, in writing.

What is the difference between authorization, settlement and availability?

Authorization is the approval to proceed, settlement is the final movement of value between institutions, and availability is the moment the recipient can use the money. They can be minutes or days apart, so a "2 day payment" needs a definition before you can compare it.

Use these working definitions:

  1. Initiation or authorization. The payer instructs the payment, or a card issuer approves it. No value has moved yet.
  2. Clearing. The banks exchange and validate the payment instructions. Errors, returns and rejects often appear here.
  3. Settlement. Value moves between the institutions through the rail's settlement mechanism. On ACH and cards this happens in batches. On instant rails it happens per payment.
  4. Availability. The receiving bank posts the credit to the recipient and releases any hold. This is the time that matters to your customer.

Card payments make the gap obvious. An authorization takes seconds, but the merchant receives funds only after capture and settlement through the acquirer, on a schedule the acquirer's agreement sets. This article does not give a card number because the schedule is contractual. Ask your acquirer.

How long does each payment method take?

Instant rails take seconds and run every day of the year, same-day ACH settles in fixed windows, and standard ACH, wires and SWIFT depend on business days. The table combines scheme-level facts from each operator with BlindPay's documented timing for its own payouts and collections.

MethodScheme-level behaviorBlindPay documented timingSource
RTP (US, The Clearing House)24/7/365 including holidays; $10 million per-transaction limitInstant, send and receiveThe Clearing House
FedNow (US, Federal Reserve)"Uninterrupted 24x7x365 processing"; $10 million limit since November 2025Not listed among BlindPay railsFederal Reserve
Same Day ACH (US, Nacha)Settles at 1:00 pm, 5:00 pm and 6:00 pm Eastern; $1 million per payment todaySee ACH belowNacha
ACH (US, standard)Batch processing on business days; two-day return timeframe for normal returnsSend about 2 business days; receive up to 5 business daysNacha
Domestic wire (US)Business days, bank cut-offs applySend about 1 business day; receive up to 5 business daysBlindPay docs
Pix (Brazil, Banco Central do Brasil)Launched 16 November 2020, 24/7/365Instant, up to 5 minutes to confirmBanco Central do Brasil
SPEI (Mexico, Banxico)Usually within seconds, available 24 hours a dayInstant, up to 10 minutes to confirmBanxico
Transfers 3.0 (Argentina)Interoperable immediate transfers, 24/7Instant, up to 10 minutes to confirmBlindPay docs
SEPA Instant (euro area, EPC)Beneficiary confirmation within 10 seconds, all calendar daysSEPA payout about 1 business dayEuropean Payments Council
ACH COP (Colombia)Domestic batch railSend about 1 business dayBlindPay docs
SWIFT cross-borderAbout 90% reach the destination bank within an hour (Swift, 2024); BIS notes correspondent banking is often described as T+1 to T+3Send about 5 business days; receive up to 5 business daysBIS WP 1385

Two readings of the table matter. First, a scheme-level time is what the rail can do, while BlindPay's documented time is what to plan for on a payout, because it includes bank partners and cut-offs. For example, SEPA Instant confirms in 10 seconds as a scheme, but BlindPay documents SEPA payouts at about 1 business day. Do not mix those two numbers. Second, BlindPay's own timings are listed in the BlindPay overview docs.

Why do payments take days?

Payments take days mainly because batch rails only run on business days, banks apply cut-offs, and cross-border payments pass through several institutions that each add checks. The network message itself is rarely the slow step.

The common causes, in the order they usually bite:

  • Cut-off times. A payment submitted after the bank's cut-off waits for the next processing window. Same Day ACH has three settlement windows, and anything that misses the last one rolls forward.
  • Business days. Standard ACH and wires do not run on weekends or bank holidays. A Friday afternoon payment can land on Tuesday.
  • Batch windows. ACH and card settlement process in groups instead of one payment at a time.
  • Compliance reviews. Sanctions screening, travel rule data and manual reviews can hold a payment, especially across borders.
  • Returns and rejects. Wrong account numbers or closed accounts come back days later, which resets the clock.
  • Time zones. A payment that settles in one country's business day may reach a recipient in another country after that bank has closed.

What is the last mile problem in cross-border payments?

The last mile problem is that most of a cross-border payment's delay happens after it reaches the recipient's bank, in local crediting and checks, not during transmission. Swift's 2024 data shows the gap clearly.

According to Swift data cited in the BIS paper, about 90% of cross-border payments over the Swift network reach the destination bank within one hour, and the paper notes that most of the delay arises in the last mile. Swift's own release puts the share reaching the end customer within an hour at 43%. Do not combine the two figures: one measures arrival at the bank, the other arrival in the customer's account.

The Financial Stability Board sets a target that 75% of cross-border payments are credited within one hour and the rest within one business day by end-2027. It is a target, not a measured result. Our guide on why cross-border payments are slow traces where the days go in more detail.

How long does a worked example take?

A worked example shows how the same $10,000 payment behaves differently by route. The timings below are illustrative planning assumptions based on the documented ranges above, not guarantees, and start on a Thursday morning before the cut-off.

RouteIllustrative planning viewWhy
US ACH payoutCredited about MondayDocumented at about 2 business days, so Thursday plus 2 business days is Monday
US wire payoutCredited about FridayDocumented at about 1 business day
Pix payout to BrazilCredited within minutesInstant rail, up to 5 minutes to confirm
SWIFT payout to a supplierCredited about the following ThursdayDocumented at about 5 business days

The point is the spread: the same amount takes minutes on one rail and a full week on another, and none of it depends on the amount.

How can you speed up payouts?

You can speed up payouts by choosing the fastest rail each destination supports, submitting before cut-offs and removing avoidable returns. Routing is the biggest lever, because the rail sets the floor on timing.

  1. Map every destination to its fastest rail. Use Pix for Brazil, SPEI for Mexico, RTP in the US where the recipient bank supports it, and SEPA for euro-area accounts.
  2. Keep SWIFT for where it is needed. Use it for countries without a suitable local rail and for supplier payments, and plan for several business days.
  3. Submit before cut-offs. Know the cut-off for each rail and batch payments ahead of it.
  4. Validate bank details first. Wrong details cause returns, and returns cost days. Verification of payee checks are spreading in Europe.
  5. Track by reference. Use UETR for SWIFT and the rail's own reference elsewhere, and surface status to the recipient.
  6. Fund ahead of the run. Payments that wait on funding wait on you, not on the rail.

For routing between SWIFT and local rails in more depth, read SWIFT vs local rails vs stablecoin.

What should you ask your provider?

Ask for timing by rail, by direction and by cut-off, and ask what the timing means: initiation to bank, or initiation to the recipient's available balance. A single "1 to 3 days" figure hides more than it tells.

Use this checklist:

  • Which rail will carry this payment, and why that one?
  • What is the settlement time for sends and for receives, separately?
  • What are the cut-off times and the time zone they use?
  • What happens on weekends and bank holidays in the destination country?
  • Do you provide a tracking reference and status webhooks?
  • What happens if the payment is returned, and how long does a refund take?

The FSB targets list transparency as a goal: providers should disclose total cost, expected delivery time and payment status tracking. Use that list as your baseline.

Where BlindPay fits

BlindPay is an API that moves money over local bank rails and SWIFT, so the settlement time you get depends on the rail you choose per corridor. Its documentation lists instant settlement for RTP, Pix (up to 5 minutes to confirm), SPEI (up to 10 minutes) and Transfers in Argentina (up to 10 minutes). It lists about 1 business day for wire, SEPA and ACH COP payouts, about 2 for US ACH payouts and about 5 for SWIFT. Behind the scenes, payments settle through stablecoins, and the overview docs show each timing. For cross-border supplier payments, SWIFT (POBO/COBO) reaches 100+ countries. See global payments for the corridors.

Methodology and sources

All scheme-level figures come from the operator or regulator named below, checked in November 2026. BlindPay timings come only from the BlindPay overview docs, checked in November 2026. Illustrative examples are labeled and are not guarantees.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.