Real-Time Cross-Border Settlement: Blockchain vs Bank Rails

Real-time cross-border settlement means the recipient can use final funds within seconds or minutes of a payment being sent, at any hour, with no wait for a bank cut-off. It takes two fast legs: a transfer between countries that does not queue in batches, and a local rail at the destination that credits the account on arrival.

This post sorts the rails by what they deliver and says where real-time stops being the goal. The route between two countries is covered in what a stablecoin corridor is.

Fast is not the same as final

Speed measures how soon the recipient sees a credit. Finality measures whether that credit can be undone. A rail can show a credit in seconds and still allow a reversal, and a rail can be final and still only open on business days.

The Federal Reserve describes the Fedwire Funds Service as a real-time gross settlement system (RTGS, where each transfer settles one by one, in full, the moment it is processed) whose transfers are final and irrevocable once processed (Federal Reserve Board). The same page gives the hours: the business day opens at 9:00 p.m. ET on the preceding calendar day and ends at 7:00 p.m. ET, Monday through Friday, excluding holidays. That is close to 22 hours a day, five days a week, not 24/7. On Lumx the FEDWIRE cut-off is 3:00 PM ET on US business days, and a request after the cut-off waits.

ACH is built the other way. It collects payments into batches and settles them together later, which is the net settlement model: slow by design, as why cross-border payments are slow explains, with its own return mechanics. Gross settlement removes the gap in which one side has paid and the other has not, the exposure Herstatt risk describes. What real-time adds is irrevocability: a wrong beneficiary cannot be recalled.

Blockchain finality depends on the network. Stellar's documentation says nodes "reach consensus, apply a transaction set, and update the ledger every 5-7 seconds" (Stellar developer docs), and that is one network's timing. On Lumx, Stellar carries only the BRL to USDC on-ramp, and off-ramps run on Ethereum, Polygon, Base and Tron. On Ethereum, ethereum.org documents slots of 12 seconds and epochs of 32 slots, and only epoch-boundary blocks can be finalized once a supermajority link joins two successive checkpoints (ethereum.org). Finality there is counted in epochs of 6.4 minutes, not seconds, so ask which confirmation count a provider waits for. Stellar, Ethereum, Polygon and Tron are compared network by network, and whether stablecoin payments can be reversed covers the reversal side.

On Lumx, a payout is not reported as one event. An off-ramp moves through TRANSFERRING_STABLECOIN, TRADING, TRANSFERRING_FIAT and SUCCESS, and each change fires its own webhook: offramp.transferring_stablecoin, offramp.trading, offramp.transferring_fiat and offramp.success. Every payload carries createdAt and updatedAt, so a customer can compute its own p95 from the transaction's creation to the offramp.success event, per rail. The docs mark an off-ramp as complete once funds leave Lumx's banking partner, and the receiving bank can still hold them for its own review, so that measure stops at Lumx's side of the hand-off.

Which payment rails are real-time and which are not?

These are the rails a Latin America cross-border flow touches. Only some run at any hour, and a few follow bank calendars.

Operating days, cut-offs and settlement by rail (Lumx cut-off times page, read on November 1, 2026). The Lumx columns are processing targets, not guarantees, and not the rail operators' own rules

Pix (Brazil's instant payment system, run by the Central Bank) and SPEI (Mexico's interbank transfer system, run by Banxico) have no cut-off on Lumx, and Faster Payments (the UK's real-time bank transfer network) has none either.

For euro payments, the ECB says the SCT Inst scheme makes funds available within ten seconds, 24 hours a day, every day of the year. SCT Inst payments in euros fall under Regulation (EU) 2024/886 of March 13, 2024, which governs euro payments sent in seconds (EUR-Lex). On Lumx, a payment of EUR 100,000 or more sent between 4:30 PM and 2:30 AM UK time routes to a standard SEPA Credit Transfer instead, which settles the same or next business day.

Colombia belongs in a Latin America view too. COP payouts on Lumx go by Bre-B (Colombia's instant payment system) or by ACH Colombia, chosen when the destination is registered. Bre-B has a Banco de la República cap of 1,000 UVB per transaction, and ACH Colombia carries the invoices above it.

Limits are in the payout cut-offs by rail. SWIFT's gpi tracking shows where a wire is but does not remove the intermediary banks' hours. The head-to-head is in stablecoins vs SWIFT. Linked payment systems against stablecoins compares the route that links rails such as Pix across countries.

How does a blockchain leg change the timeline?

A cross-border bank payment passes through correspondent accounts, each with its own hours and fee. A stablecoin leg replaces that chain with one wallet transfer, which has no cut-off and no weekend. It does not finish the job alone: for Latin America the answer is a hybrid, with the cross-border step on a blockchain and the last mile on a local rail such as Pix or SPEI. The recipient gets reais or pesos in a bank account and never holds a token.

A Friday-evening payment on each route, assuming the customer's Lumx wallet already holds the stablecoin (Lumx cut-off times page)

The blockchain leg is identical in every row, so the destination rail decides. For the Brazil corridor, the walk-through is in USDC to Brazil by Pix, with live rates on USDC to BRL and USDC to MXN.

What are the best real-time settlement providers for each payment need?

The destination rail follows from who is paid and in which currency. The blockchain leg follows from the stablecoin held: on Lumx, USDC runs on Ethereum, Polygon and Base, USDT on Ethereum, Polygon and Tron, and Stellar is on-ramp only, for BRL to USDC.

Rail and blockchain leg by payment need, with the providers that list each rail (Compare pages and Lumx Coverage, read November 2, 2026)

Lumx fits the Latin America rows: Pix, SPEI and Bre-B behind BRL, MXN and COP accounts, with no cut-off. For USD, Lumx pays out over ACH, Fedwire and SWIFT, and a request after the 3:00 PM ET FEDWIRE cut-off waits. For pounds and euros it uses Faster Payments, up to GBP 1 million per payment, and SCT Inst or a standard SEPA Credit Transfer, which Lumx picks itself.

What slows down a payment that says real-time

Four things slow a fast-looking route; none is the blockchain. The funding leg: a payout starts only once the sender's funds are in, so a USD wire deposit starts the clock later than a Pix or SPEI one. The cut-off: payments sent at 2:55 PM ET and 3:05 PM ET on a Fedwire leg land on different days. The reviews: transfers above standard thresholds can trigger an extra risk review, which the docs say typically adds up to two business hours, and a transaction held as an RFI (request for information, a compliance hold that asks for a document) may be refunded to the sender if the customer does not answer within 24 hours. The receiving bank can hold a credit for its own review, even on an instant rail.

Is real-time settlement cheaper than batch?

Not by itself. The Financial Stability Board sets speed and cost as separate targets for end-2027: 75% of retail cross-border payments with funds available within one hour, and a global average cost of no more than 1%, with no corridor above 3% (FSB).

A bank paying out in a currency it does not hold locally has to position balances there ahead of time, a cost of its own that a stablecoin leg removes. A real-time route adds the cost of getting the destination right first time, since it cannot be recalled. Fees by corridor are in cross-border payment costs in 2026.

On Lumx, the pricing model is a monthly platform fee plus usage-based per-transaction fees, transparent FX on locked quotes, no pre-funding; no published plans. No pre-funding means the customer does not leave capital parked in nostro accounts abroad: conversion and settlement happen when the transaction is started.

What I would measure before calling a route real-time

I would not accept a median as proof of real-time. I would ask a provider for the time from submit to usable funds at the 95th percentile, over a full week that includes a weekend and a banking holiday in both countries, split by destination rail. A business-hours median makes a batch rail look fast. The slow tail is what a finance team lives with: the supplier still waiting on Monday, and the payroll that arrives a day late.

When real-time settlement is the wrong goal

• A payment that needs a second approver or an invoice check before it goes.

• A forward-dated payment at a rate fixed today. That is a hedging question for the client's bank or FX broker.

• A destination with no instant rail, where the last leg runs on ACH or a bank wire. The credit will not arrive on a weekend.

What real-time settlement looks like on Lumx

Lumx is stablecoin payments infrastructure for businesses that move money between Latin America and the rest of the world: one API to collect, hold, convert, and pay out in BRL, MXN, COP, USD, EUR, and GBP or in USDC and USDT, over local rails such as PIX, SPEI, PSE, Bre-B, ACH, FEDWIRE, SEPA, and Faster Payments, with SWIFT and on-behalf-of payments and collections (POBO and COBO) in USD, EUR, and GBP, plus named virtual accounts, custodial wallets, and KYB/KYC built in.

A payout starts with a quote. A floating rate has no price lock. A locked rate carries an exchangeRateId and holds for 30 seconds, 1 minute or 5 minutes: the 30-second lock has no fee, and the longer ones include a fee for volatility risk. The off-ramp then converts stablecoin from the customer's wallet and sends it to a pre-registered destination.

The destination sets the last leg, as in the table above. The rail list is on the Coverage page and global payments.

Methodology and sources

The finality wording and hours for Fedwire come from the Federal Reserve Board's Fedwire Funds Services page. The SCT Inst definition comes from the ECB's SCT Inst page and the regulation from EUR-Lex. Blockchain timing comes from the Stellar documentation and ethereum.org. The speed and cost targets are the G20 targets as published by the Financial Stability Board. Provider rail lists come from the linked Compare pages. Product behavior comes from the Lumx docs on payment rail cut-off times, Coverage, Transactions, Exchange Rates, Destinations, Wallets and RFI.

The rail columns for Lumx are Lumx's own processing targets, not the operators' rules. The Bre-B cap is the Banco de la República's Circular Reglamentaria Externa DSP-465, Asunto 18, numeral 3.2, sheet of March 31, 2026, in its compendium.

Verified on November 1, 2026. Operational context, not legal, tax, or investment advice.

Cover photo: Deva Darshan on Unsplash.