In this article
Payment rails are the networks, and the rules that govern them, that carry a payment from one account to another: card networks, batch transfer systems such as ACH and SEPA credit transfer, large-value systems such as Fedwire and CHAPS, instant payment systems, cross-border arrangements instructed over SWIFT, and blockchains. A rail decides how fast the money arrives, at what hours, up to what amount, and whether the payment can be taken back afterwards.
The word comes from the railway: a bank, a processor or a payment app is the train, and the rail is the track it has to run on. Two payment products with very different screens often run on the same track, which is why they share the same cut-off times and the same limits.
The named systems below are described from the pages of the bodies that operate or govern them. Published limits carry their date where the source gives one, because operators raise them from time to time.
Counts from the sections of this article; the supplier payment is an illustrative worked example.
What does a payment rail consist of?
A payment rail consists of four things: a messaging format that says who pays whom and how much, a clearing arrangement that sorts and reconciles those messages, a settlement asset in which the banks actually pay each other, and a rulebook that binds every participant.
The messaging format is the language of the rail. An ACH file, a card authorisation request, a SWIFT message and a blockchain transaction are four different formats for the same sentence: debit this account, credit that one, for this amount.
The clearing arrangement is the sorting office. It receives the messages, checks them, routes each to the right institution and works out what each participant owes the others. On some rails this is a central operator; on a blockchain it is the network of validators.
The settlement asset is the money in which the participating institutions square up. On the main domestic systems it is central bank money: the Federal Reserve describes its Reserve Banks as settling ACH payments by crediting and debiting the settlement accounts of depository institutions, and the European Central Bank describes its large-value system as settling in central bank money. Across borders it is usually a balance one bank holds with another. On a blockchain it is the token itself.
The rulebook says who may join, what each party must do and by when, what happens when a payment is wrong, and who bears the loss. The rule-maker and the operator are often two different bodies. Nacha states that it governs the ACH Network and does not process payments itself, while the Federal Reserve and a private-sector operator run the processing. The European Payments Council writes the SEPA scheme rulebooks, and payment service providers that execute transfers must formally adhere to them.
What are the main families of payment rails?
Business payments run on six families of rails: card networks, batch credit and debit transfer systems, real-time gross settlement systems for large values, instant payment systems, cross-border messaging over correspondent accounts, and blockchains.
| Family | How it moves money | Named examples |
|---|---|---|
| Card networks | The merchant pulls funds from the cardholder's issuer; authorised in seconds, settled between banks later | The international and domestic card schemes |
| Batch credit and debit transfers | Payments are collected into files, exchanged and settled at set times | ACH, SEPA credit transfer |
| Real-time gross settlement | Each payment settles individually, at once, in central bank money | Fedwire, CHAPS, the Eurosystem's T2 |
| Instant payment systems | One payment at a time, in seconds, every day of the year | FedNow, the RTP network, SEPA instant credit transfer, Faster Payments |
| Cross-border correspondent payments | A message instructs banks to move balances they hold with each other | SWIFT messaging over correspondent accounts |
| Blockchains | A signed transaction updates a shared ledger; the token is the settlement asset | Ethereum and similar networks |
Card networks are the only family in the table designed around a merchant and a shopper rather than two bank accounts, and their rulebooks add a formal dispute process through which a cardholder's bank can reverse a payment after the fact.
Batch systems are the workhorses. The Federal Reserve describes the ACH as a nationwide network through which depository institutions send each other batches of electronic credit and debit transfers, and gives payroll direct deposit as a typical credit and mortgage or utility collection as a typical debit.
Real-time gross settlement, usually shortened to RTGS, sits at the other end: no batching, no netting, each payment paid in full the moment it is processed. Instant payment systems bring that immediacy to everyday amounts around the clock.
How do ACH, Fedwire, SEPA, Faster Payments and CHAPS compare on speed, hours and limits?
The named rails fall into three speeds: batch systems that settle within a banking day or two, large-value systems that settle at once but only during a business day, and instant systems that settle in seconds at any hour.
| Rail | Speed | Operating hours | Published value limit |
|---|---|---|---|
| ACH (United States) | Same day, next banking day or two banking days | Banking days, at set settlement times | $1 million per Same Day ACH payment, since 18 March 2022 |
| Fedwire Funds Service (United States) | Immediate | 9:00 pm Eastern on the previous calendar day to 7:00 pm Eastern, Monday to Friday | None stated by the Federal Reserve |
| FedNow Service (United States) | Seconds | Every day, all hours | $10 million per customer transfer, since 12 November 2025 |
| RTP network (United States) | Seconds | Every day, all hours | $10 million per transaction |
| SEPA credit transfer (euro area and wider SEPA) | Business days, within the scheme's maximum execution time | Business days | Not stated on the scheme page |
| SEPA instant credit transfer | Under ten seconds | Every day, all hours | No scheme-level maximum |
| Faster Payments (United Kingdom) | Real time | Day and night, 365 days a year | £1 million at system level |
| CHAPS (United Kingdom) | Same day, settled individually | Usually 6:00 am to 6:00 pm, Monday to Friday | No minimum or maximum |
A published limit is the ceiling of the rail, never a promise from your bank. The Federal Reserve says FedNow participants may use the maximum or set lower limits to suit their organisation, and the operator of Faster Payments notes that each bank and building society sets its own limit separately. The amount you can actually send is the lower of the two.
ACH speed depends on the instruction, not only on the network. Nacha estimates that about 80% of ACH payments settle in one banking day or less. According to Nacha, credits can settle the same day, the next banking day or in two banking days, and debits typically settle the same day or the next banking day.
Hours shape the weekend. The Fedwire business day described by the Federal Reserve runs 22 hours, from 9:00 pm Eastern on the preceding calendar day to 7:00 pm, Monday to Friday excluding holidays. The Bank of England gives CHAPS hours as usually 6:00 am to 6:00 pm on working days, with customer payments to be submitted by 5:40 pm. The Eurosystem's T2 runs Monday to Friday and closes at weekends. A large payment instructed on a Friday evening therefore waits for Monday on all three, while an instant system keeps running.
The euro picture has one more layer. SEPA credit transfer and SEPA instant credit transfer are schemes, meaning rulebooks, that the European Payments Council says can be used for euro payments across 41 SEPA countries and territories; the processing is done by clearing and settlement mechanisms that follow those rules. For the instant scheme, the Council states that providers have nine seconds to process a transaction from the moment the payer's provider receives the instruction, and that the service is available 24 hours a day on all calendar days.
Which payment rails are final, and which can be reversed?
Large-value and instant systems are built to be final once processed, while card payments and pulled bank debits can be returned or disputed for a period set by their rulebooks. Finality, in the glossary of the Committee on Payment and Settlement Systems at the Bank for International Settlements, is settlement that is irrevocable and unconditional.
| Rail | Finality and reversibility | Direction | Typical use |
|---|---|---|---|
| Card networks | Authorised at once, but open to a dispute under the scheme rules | Pull | Consumer sales, online checkout, small business purchases |
| ACH | Entries can be returned under the Nacha rules within set deadlines | Push and pull | Payroll, supplier payments, recurring collections |
| Fedwire | Immediate, final and irrevocable once processed | Push | Large and time-critical payments, closings |
| FedNow and the RTP network | Settled at once; the private network describes its settlement as final | Push | Urgent supplier and payroll payments, account-to-account transfers |
| SEPA credit transfer | A credit pushed by the payer; errors are handled through scheme procedures | Push | Euro salaries and invoices |
| SEPA instant credit transfer | A credit pushed by the payer, received in seconds | Push | Euro payments that cannot wait for a business day |
| Faster Payments | A real-time credit pushed by the payer | Push | Everyday sterling transfers and invoices |
| CHAPS | Irrevocable between the direct participants | Push | Property purchases, large corporate and financial payments |
| Blockchains | Final once the network has finalised the block | Push | Stablecoin payments, payments shared among several parties |
A final rail protects the person being paid: once the money has arrived, it is theirs. A reversible rail protects the person paying: an unauthorised debit or an undelivered order can be undone.
What is the difference between a push payment and a pull payment?
In a push payment the payer instructs their own bank to send money; in a pull payment the payee instructs their bank to collect it from the payer's account under an authorisation the payer gave earlier. The distinction decides who starts the payment, who can make a mistake, and who carries the risk that it comes back.
Wires, instant payments and credit transfers are push payments. The glossary of the Committee on Payment and Settlement Systems defines a credit transfer as a payment order made for the purpose of placing funds at the disposal of the beneficiary, and a debit transfer system as one in which debit collection orders made or authorised by the payer move from the bank of the payee to the bank of the payer.
Card payments and direct debits are pull payments. ACH is unusual in carrying both: Nacha reports that credits make up just under half of ACH volume and debits just over half.
For a business the difference is concrete in three ways:
- Control of timing. With a pull, the business collects on the due date without waiting for the client to act. With a push, it waits for the client to send.
- Return risk. A pulled payment can come back if the account lacks funds or the payer disputes the authorisation. A pushed payment has already left an account that held the money.
- Error risk. In a push, the payer types or pastes the destination, so a wrong or substituted account number is the payer's exposure. In a pull, the payee already holds the payer's details under a mandate.
What is the difference between clearing and settlement?
Clearing is the exchange and reconciliation of payment instructions between institutions, which establishes who owes what to whom. Settlement is the actual discharge of those obligations, when the settlement asset moves and the institutions no longer owe each other anything.
Batch rails clear first and settle later, while RTGS and instant rails do both at once for each payment. The gap between the two steps, and what it means for the moment a payment is really done, is the subject of a separate article on settlement in payments.
Where does SWIFT fit, if it carries messages and not money?
SWIFT is the messaging layer of cross-border banking: it carries the instruction, and the money moves across accounts that banks hold with one another. SWIFT describes itself as a global member-owned cooperative and a provider of secure financial messaging services, connecting a network of over 11,000 financial institutions.
Because no single central bank account exists for the whole world, a cross-border payment settles through correspondent banking, which the glossary of the Committee on Payment and Settlement Systems defines as an arrangement under which one bank, the correspondent, holds deposits owned by other banks, the respondents. A bank in one country that wants to pay euros keeps a euro account with a bank inside the euro area. The SWIFT message tells that correspondent to debit the account and pay the beneficiary's bank, which it does over a domestic euro rail.
How each bank in the chain is chosen, what it deducts and how long each hop takes are covered in the international articles on SWIFT and on correspondent banks.
Are blockchains payment rails?
A public blockchain is a payment rail by the same four-part test: its transaction format is the message, its validators do the clearing, its token is the settlement asset, and its protocol is the rulebook. The difference from a bank rail is that message, clearing and settlement happen in one step, on a ledger that every participant can read.
On Ethereum, according to the documentation published by the Ethereum Foundation, time is divided into slots of 12 seconds and epochs of 32 slots, which makes an epoch 6.4 minutes. Finality comes from checkpoints at the start of each epoch: when votes representing at least two-thirds of the total staked ETH link two checkpoints, the older one is finalised. The same documentation states that reverting a finalised block would require a party to commit to losing at least one-third of all staked ETH.
Three features set this family apart on the criteria used above. It has no operating hours and no business days. It is a pure push rail: only the holder of the keys can send, and nobody can pull. And reach works differently: a bank rail reaches anyone with an account at a participating bank, while a blockchain reaches anyone with an address, provided both sides are able and permitted to hold the token used. A business that keeps its books in bank money adds a conversion step at each end, through a regulated provider.
A comparison of ACH, wire and onchain payment on cost and timing is the subject of its own article.
Why does one payment often cross several rails?
One payment often crosses several rails because no single rail reaches every account, every currency and every amount, so each leg of the journey uses the rail that covers it.
Follow one invoice. A United States importer owes a supplier in Germany €250,000. The figures below are illustrative: the exchange rate of 1.08 dollars per euro, the $35 sending fee and the €15 correspondent deduction are assumptions chosen to make the arithmetic visible, not market quotes.
- Day 1: the importer funds its account over ACHThe importer holds $120,000 and collects three invoices from its own customers by ACH debit, a pull: $60,000, $55,000 and $45,000, or $160,000 in total. The debits settle on the next banking day, bringing the balance to $280,000.
- Day 2: the importer instructs its bankThe bank converts at the assumed rate: €250,000 costs $270,000. With the assumed $35 fee, $270,035 leaves the account, which keeps $9,965. This first movement is a book entry inside the bank, not a rail.
- Day 2: the instruction travels over SWIFTThe importer's bank holds euros with a correspondent bank in the euro area. A SWIFT message tells the correspondent to debit that account and pay the supplier's bank. No money has crossed a border: a balance has changed owner on the correspondent's books.
- Day 2 or 3: the euros move on a domestic euro railThe correspondent pays the supplier's bank through the euro large-value system, which settles each payment individually in central bank money. After the assumed €15 deduction, the supplier is credited €249,985.
- Same day: the supplier pays onward by instant transferThe supplier owes three subcontractors €80,000, €62,500 and €40,000. It sends three SEPA instant credit transfers totalling €182,500, each received in seconds, and keeps €67,485.
The invoice touched ACH, a correspondent account instructed over SWIFT, the euro RTGS system and SEPA instant: four rails, with four sets of hours and four rulebooks.
The ACH leg is why the importer could not pay on Day 1: the pulled funds had not yet settled. The correspondent leg is why the supplier received €15 less than the invoice, and why the importer could not see where the payment was after it left. The RTGS leg is why the payment could not move over a weekend. The instant leg is why the subcontractors were paid within seconds of the supplier's instruction, at any hour.
Simpler payments follow the same pattern: a payroll run funded by wire and paid out by ACH crosses two rails. The slowest and the most reversible leg set the timing and the risk of the whole chain.
What can a business choose about its rails, and what can it not?
A business can choose which payment methods it offers and accepts, which bank or provider it uses, and which leg it pays to speed up; it cannot choose which rails its bank has joined, the operating hours of a system, the rulebook, or the rail its counterparty's bank can receive on.
| Decision | Within the business's control | Fixed by the rail or the provider |
|---|---|---|
| Method offered to clients | Which methods appear on the invoice or at checkout | Whether the client's bank or country can use them |
| Speed | Paying for a same-day, wire or instant option where offered | Operating hours, cut-off times, settlement times |
| Amount | Splitting or scheduling a payment, asking for a higher limit | The system limit and the bank's own lower limit |
| Reversibility | Choosing a push rail for certainty or a pull rail for convenience | Return and dispute rights written into the rulebook |
| Reach | Opening an account with a provider connected to the needed rail | Which institutions and currencies the rail connects |
| Cost | Comparing providers and negotiating pricing | The fee structure each rail imposes on providers |
Access is the least visible constraint. Institutions join an instant system one at a time, so an instant payment only works when both the sending and the receiving institution take part. A business that needs a given rail should ask its bank whether it sends on it, receives on it, or both.
One case changes the count of payments rather than the rail. When a single incoming payment has to be shared among several parties, bank rails carry it as one receipt followed by several outgoing transfers, each with its own timing. On a blockchain rail, a payment router can make the division part of the payment. Shaka is one such router: each party's share is agreed, and can be signed by each recipient, before the client pays; the client pays once; and every party, up to 20 recipients, is paid at the same moment in one final transaction. It routes the payment and never holds the funds. It is not an escrow service, a bank or a processor, and it does not suit a payment that must be held until a condition is met, which is the job of an escrow or settlement agent.
A comparison of the methods themselves belongs to the article on B2B payment methods compared. Every method is a product built on one or more rails, and the rail sets the outer limits of what the product can promise.
What should you ask your bank or provider about a rail before you rely on it?
Before relying on a rail for a payment that matters, ask six questions: which rail the payment will actually use, when it settles, what the limit is for your account, whether it can be returned, what it costs at each leg, and what proof you will receive.
- Which rail carries this payment? A "bank transfer" on a screen may be a batch transfer, an instant payment or a wire. Ask for the name of the system.
- When is the payment settled, and when are funds available? Ask for the cut-off time, the settlement time, and whether weekends and holidays count.
- What is my limit? Ask for the per-payment and daily limits on your account, not the limit of the system.
- Can the payment come back, and until when? For a pulled payment, ask for the return and dispute periods that apply. For a pushed payment, ask what the recall procedure is and whether it depends on the beneficiary's consent.
- What is deducted along the way? For a cross-border payment, ask whether intermediary banks may deduct charges and who bears them, and at what exchange rate the conversion is made.
- What record will I hold? Ask for the reference that proves the payment was sent and the one that proves it was received, so both sides can reconcile it.
Those six answers also make two offers that look alike comparable: the same wire, sent by two banks, may share a rail and differ in cut-off time, limit and fee.
