Blockstream

What Are Payment Rails?

AddedIntermediate
TL;DR: A payment rail is the network infrastructure that moves money from a payer to a payee. The major traditional rails are ACH for batch transfers, Fedwire for high-value wires, RTP and FedNow for real-time payments, card networks for consumer purchases, and SWIFT for cross-border messaging. Each trades off settlement speed, cost, operating hours, and dispute handling differently. Bitcoin adds new rails: on-chain settlement, the Lightning Network for instant payments, and the Liquid Network for larger transfers and stablecoins, all running 24/7 without banking hours.

A payment rail is the underlying network that carries a payment from one party to another. A paycheck arriving by direct deposit traveled over ACH, while a card tapped at checkout ran through a card network's authorization system. The money is the cargo, and the rail is the track it travels on.

Every rail, old or new, gets judged on the same axes: how fast value reaches finality, what moving it costs, when the rail is open, and who carries dispute risk. This article walks through the major traditional rails on those axes, then applies the same questions to Bitcoin's payment rails, which payment companies are increasingly evaluating alongside the traditional rails.

How Payment Rails Work

Most payments involve three distinct steps that are easy to conflate. Authorization confirms the payment can happen: the account exists, the funds or credit are available. Clearing exchanges the payment instructions between institutions. Settlement moves the actual money, and only settlement makes the payee whole.

Rails differ in how far apart those steps sit. A card payment authorizes in seconds but settles to the merchant days later. An ACH transfer batches instructions and settles on a banking-day schedule. A Fedwire transfer collapses all three steps into one near-instant, final movement. The gap between "the payment went through" and "the money has arrived, irreversibly" is where most of a rail's cost, risk, and complexity lives.

Consumer payment apps add another layer of nuance: most are platforms riding on rails rather than rails themselves. A balance transfer inside such an app moves on the company's internal ledger, while money entering or leaving the platform travels over card networks or ACH underneath.

ACH: Batch Transfers on Banking Hours

The Automated Clearing House (ACH) network is the United States' batch-transfer rail, governed by Nacha. It carries direct deposits, bill payments, and business-to-business transfers by collecting instructions into batches and processing them on a banking-day schedule. Standard ACH credits settle in one to two business days, and Same Day ACH settles eligible payments of up to $1 million within the same business day.

ACH's strengths are cost and reach: transfers typically cost a few cents to a few dollars, and nearly every U.S. bank account is reachable. Its constraints are the calendar and reversibility. The network observes banking days and holidays, and transactions can be returned after settlement for errors, insufficient funds, or unauthorized activity, so true finality arrives days after the money appears to move.

Wire Transfers: Fedwire and Same-Day Finality

Fedwire, operated by the Federal Reserve Banks, is a real-time gross settlement system: each transfer settles individually and irrevocably, in near real time during operating hours. Wires are the rail for high-value, time-critical payments such as real estate closings and interbank settlement.

The trade-offs are cost and hours. Banks commonly charge tens of dollars per outgoing wire, which makes the rail uneconomical for small payments, and Fedwire operates on business days only. A wire initiated on Friday evening waits until the next business day, no matter how urgent the payment is.

Real-Time Rails: RTP and FedNow

Two newer U.S. rails close the speed and hours gap. The RTP network, operated by The Clearing House since 2017, and FedNow, launched by the Federal Reserve in July 2023, both settle individual payments in seconds with immediate finality, 24 hours a day, every day of the year.

Both are credit-push systems: the payer initiates every transfer, and nothing can pull funds from an account. That design removes the chargeback mechanics of pull-based rails. Their limits lie elsewhere: both carry only U.S. dollars between participating U.S. institutions, per-transaction limits apply, and bank adoption is still expanding. For domestic payments they represent the legacy system's closest answer to instant settlement.

Card Networks: Authorization Now, Settlement Later

Card networks are the most widely used consumer rail, and the most expensive for the businesses accepting them. Card acceptance costs a merchant interchange, network assessments, and processor markup. All-in, standard consumer credit cards cost U.S. merchants roughly 2.5% to 3.5% per transaction as of 2025. On the debit side, the Federal Reserve publishes average interchange by network under Regulation II. Because these fees are percentage-based, they scale with volume indefinitely: a processor moving $1 billion a year hands tens of millions of it to the card stack.

Speed on card networks divides into two stages. Card authorization happens in seconds, but settlement to the merchant runs on a delay measured in days, and every transaction carries chargeback exposure for months afterward. The chargeback system gives consumers a dispute path, and it gives merchants a fraud cost line that no other rail imposes at the same scale.

SWIFT and Cross-Border Payments

Most cross-border payments travel over SWIFT, which is a messaging network rather than a settlement system. SWIFT carries standardized payment instructions between thousands of banks; the money itself moves through chains of correspondent accounts that banks hold with one another. That separation is why an international payment can take anywhere from minutes to several days and accumulate fees at each hop, depending on the currency corridor and the number of intermediaries in the chain.

Cross-border settlement is where legacy rails concede the most ground, and it is one of the first places businesses look at Bitcoin rails, which treat a payment to another continent the same as a payment across the street.

Comparing the Traditional Rails

Rail Settlement Speed Operating Hours Cost Character Reversibility
ACH Same day to two business days Banking days Low, flat Returnable after settlement
Fedwire Near-instant, final Business days High, flat per transfer Irrevocable
RTP / FedNow Seconds, final 24/7 Low, flat Credit-push, no pulls
Card networks Authorization in seconds; merchant settlement in days 24/7 authorization; banking-day settlement Percentage of every transaction Chargebacks for months
SWIFT (cross-border) Minutes to days Varies by correspondent chain Fees per intermediary Varies by corridor

Rail characteristics above reflect U.S. payment systems as of June 2026; fees, operating hours, and settlement rules can change as networks update their policies.

Bitcoin's Payment Rails

Bitcoin contributes three rails that answer the traditional constraints differently: the Bitcoin blockchain itself for final settlement, and two layer-2 networks built on top of it for speed and volume. All three operate continuously, cross borders natively, and price transfers without taking a percentage-scale cut of the amount.

On-Chain Bitcoin: Settlement Without Banking Hours

An on-chain Bitcoin transaction settles directly on the Bitcoin blockchain, with a new block roughly every ten minutes, every day of the year. Fees are set by the transaction's size in bytes and current network demand, not by the amount being moved, so transferring $1 million costs about the same as transferring $100. That structure favors high-value settlement; for small, frequent payments, confirmation times and per-transaction fees favor the layers above it. The trade-offs between the base layer and Lightning are covered in Lightning vs. On-Chain, and the fee mechanics in Why Does Bitcoin Have Fees?

Lightning: A Rail That Settles in Seconds

The Lightning Network is a payment rail built on Bitcoin where final settlement happens in seconds. There is no authorization-then-settlement split: when a Lightning payment completes, the payee has the funds. The architecture is explained in What Is the Lightning Network?

The fee model is structurally different from interchange. Routing fees are set by node operators as a small base fee plus a rate measured in parts per million of the amount, which for typical payment sizes keeps costs a small fraction of card acceptance. That rate scales with the amount, but stays orders of magnitude below interchange's percentage-based pricing.

Lightning payments are also push-based, like RTP and FedNow. The payer sends; nobody pulls from a stored card number. That removes fraud-driven chargebacks as a cost line for the business accepting payments. The same property removes a consumer protection layer, so refunds and disputes become something the merchant relationship handles rather than the network.

Liquid: Settlement and Stablecoin Transfers

Lightning is built for payment-sized transfers. For treasury moves, batch settlement, and cross-border flows, the Liquid Network is the second Bitcoin layer-2 rail: 60-second blocks, deterministic finality with roughly two-minute settlement as the conservative convention, and 24/7 operation with no banking hours anywhere in the stack. The architecture is covered in How Does the Liquid Network Work?

Liquid also carries USDT, which makes it a working stablecoin rail for cross-border settlement. After the Elements Improvement Proposal 200 fee reduction, a confidential USDT transfer on Liquid costs a few cents. Confidential Transactions hide amounts and asset types from outside observers, so a company's settlement flows are not public market data, while counterparties and auditors can still be granted visibility.

How Lightning and Liquid Connect

The rails interoperate. Liquid ↔ Lightning swaps use atomic swaps, so funds move between rails without an intermediary taking custody along the way; the mechanics are explained in How Do Cross-Layer Swaps Work? A business can accept small payments over Lightning and consolidate into Liquid for settlement, or fund Lightning capacity from a Liquid balance.

Integration Paths for Payment Companies

Running Lightning infrastructure directly means running nodes, managing channels and liquidity, and hiring for a skill set that is still scarce. Core Lightning is the open-source implementation suited to teams that want that control.

Greenlight is the hosted path: Blockstream runs Core Lightning nodes in the cloud while the signing keys stay on the company's own devices, so the host never controls the funds. Nodes start on demand, the interface is the same gRPC surface as self-hosted Core Lightning, and a company that outgrows hosting can migrate its nodes to its own infrastructure. Greenlight passed 200,000 nodes in 2024, and its free tier covers 1,000 on-demand nodes.

A business that wants to take payments without operating any of this infrastructure has lighter-weight options too; the practical paths are laid out in How Can a Business Accept Bitcoin Payments? and Lightning Network for Merchants.

How to Compare Payment Rails

A payments team can put every rail, legacy or Bitcoin, through the same five questions:

  • Does settlement reach finality in seconds, minutes, or days?
  • Do fees scale as a percentage of every transaction, or stay flat as volume grows?
  • Does the rail run 24/7, or does it observe banking hours and holidays?
  • Who carries dispute and chargeback risk, and for how long?
  • Can funds move without an intermediary holding them in transit?

Cards, ACH, and wires each concede at least two of those questions, while Lightning and Liquid were designed with all five in mind. The real-time rails close the speed and hours gap for domestic dollar payments but stop at the border. For a payments team, the practical exercise is to model actual transaction volumes against each rail's fee structure and settlement profile rather than to pick a winner in the abstract.

Frequently Asked Questions

What is a payment rail?

A payment rail is the network infrastructure that moves money from a payer to a payee. ACH, Fedwire, RTP, FedNow, card networks, the Lightning Network, and the Liquid Network are all payment rails, and each carries different settlement speeds, operating hours, costs, and dispute models.

What are the payment rails in the US?

The major U.S. rails are ACH for batch transfers, Fedwire for high-value real-time gross settlement, RTP and FedNow for 24/7 instant payments, and the card networks for consumer purchases. Bitcoin's on-chain, Lightning, and Liquid rails operate alongside them without banking hours or geographic boundaries.

Is PayPal a payment rail?

PayPal is a payment platform rather than an underlying rail. Transfers between PayPal balances move on the company's internal ledger, while money entering or leaving the platform travels over existing rails such as card networks and ACH. Most consumer payment apps follow this same pattern of riding on rails they do not operate.

Is Lightning cheaper than card networks?

For typical payment sizes, yes. Card acceptance costs U.S. merchants roughly 2.5% to 3.5% per transaction all-in, while Lightning routing fees are a small base fee plus a parts-per-million rate set by node operators, orders of magnitude below interchange's percentage-based rates. Businesses should model their own volumes.

How fast does the Liquid Network settle?

Liquid produces blocks every 60 seconds with deterministic finality, and roughly two minutes is the conservative settlement convention. The network operates 24 hours a day, seven days a week, with no banking hours, cutoff times, or holiday schedules anywhere in the stack.

Do Bitcoin payments have chargebacks?

No. On-chain, Lightning, and Liquid payments are push-based and final once settled, so there is no network-level chargeback mechanism. That removes fraud-driven chargeback costs for businesses, and it also means refunds are handled at the merchant level rather than by the rail itself.

Mockup view Refreshed Added Overlap resolution
Version history
LatestCurrent version (unreleased edits)
v3Pre-benchmark-trim2026-06-14 · 11 changes
v2Pre-IA-expansion (custody re-segmentation + new sections)2026-06-12 · 77 changes
v1Legal de-risk fixes2026-06-11 · 77 changes