Payment Rails Explained: Types, Trends & Use Cases

A payment rail is the underlying network that actually moves money from a payer to a recipient. ACH, SWIFT plus correspondent banking, SEPA, UPI, RTGS, FedNow and the card networks are all payment rails. Each has a different operator, geography, settlement speed and cost basis.

If you're an Indian services exporter, only one of those questions really matters: which rail can deliver a client's money into your INR account, and what does it cost you by the time it lands? That's the question this page answers, with a worked example and the compliance steps that follow the money.

Payment rails are the underlying networks and infrastructure that move money from a payer to a recipient. Think of a rail as the track, and everything else in payments as a train running on it. The main types: ACH and SEPA (batch bank transfers), UPI, FedNow, RTP and Pix (real-time), Fedwire and CHIPS (large-value wires), the card networks, and SWIFT plus correspondent banking (cross-border). Also called payment networks or settlement systems.

Rails sit at the bottom of a four-layer stack, and the layers get mixed up constantly. Here's what each one does, because knowing which layer you're buying from tells you who's actually holding your money.

The aggregator row is the one most explainers leave out, and in India it's the layer that carries the RBI licence.

The Reserve Bank of India's consolidated Payment Aggregator Directions, dated 15 September 2025, define three categories: PA-Online, PA-Cross Border and PA-Physical. PA-CB covers entities facilitating cross-border inward and outward transactions, and it requires RBI authorisation.

Four buckets cover almost everything, plus a fifth that's still settling into place. Each rail below gets a short definition and a pointer, because the mechanics of any single rail deserve their own page rather than a paragraph here.

Card networks

• Visa and Mastercard - Global authorisation networks. Authorisation is instant, but funds typically settle to the merchant on a T+1 to T+2 cycle. The cost is interchange, a percentage plus a fixed fee, set by the network rather than published as a public rate card. The only hard, citable numbers are the EU's regulatory caps of 0.2% on consumer debit and 0.3% on consumer credit under the 2015 Interchange Fee Regulation. No equivalent published US or India rate exists.

Batch bank transfer rails

• ACH (Automated Clearing House), US - Bank-to-bank electronic transfers, batched and cleared in windows. Same Day ACH currently carries a limit of $1,000,000 per payment. Nacha has approved raising that to $10 million, but it doesn't take effect until 17 September 2027, so don't plan around it yet.
• SEPA Credit Transfer (SCT), Europe - Euro credit transfers across the Single Euro Payments Area, cleared in batch cycles, usually same or next business day. Often free between eurozone banks.
• SEPA Instant (SCT Inst) - The instant version, settling in seconds, 24/7/365. The old EUR 100,000 scheme cap was effectively removed under the 2025 EPC rulebook. The EU's Instant Payments Regulation also required fee parity with standard SCT from January 2025, and full send-and-receive support from euro-area payment service providers by 9 October 2025.

For how the US rails compare against each other on cost and use case, see our breakdown of US payment rails.

Rails that settle in seconds

• UPI (Unified Payments Interface), India - NPCI's real-time retail rail, 24/7/365, settling in seconds. Merchant acceptance is live in around ten countries for outbound spending from India. It is not a general inbound export-receiving rail.
• FedNow, US - The Federal Reserve's instant rail, launched 20 July 2023. The transaction limit was raised to $10 million effective November 2025.
• RTP (Real-Time Payments), US - The Clearing House's instant rail, 24/7/365, with a $10 million per-transaction limit effective 9 February 2025.
• Pix, Brazil - Brazil's instant payment system, operated by Banco Central do Brasil and launched in November 2020. Settles in seconds, always on, free for individuals.
• Faster Payments (FPS), UK - Operated by Pay.UK, always on with no standard cut-off. Settlement is usually within seconds, though it can stretch further if a participant isn't a direct scheme member.

Large-value and cross-border rails

• Fedwire, US - The Federal Reserve's real-time gross settlement system for large-value USD. It completed its migration to the ISO 20022 messaging standard with the 14 July 2025 go-live, announced the following day.
• CHIPS (Clearing House Interbank Payments System), US - Operated by The Clearing House. Also large-value USD, but it uses multilateral netting rather than gross settlement, which reduces how much liquidity participants need to hold. A private-sector system, distinct from the Fed's Fedwire.
• RTGS, India - The RBI's real-time gross settlement system for high-value INR, with a Rs 2 lakh minimum and no upper limit. Available 24x7x365 since 14 December 2020.
• SWIFT plus correspondent banking - SWIFT is a messaging network, not a settlement rail. It carries standardised payment instructions between banks, and the money itself moves through those banks' correspondent nostro and vostro accounts afterwards. That distinction explains most of what goes wrong in cross-border payments, and we cover it properly on our SWIFT network explainer.

Blockchain and stablecoin rails

• Stablecoin and distributed-ledger settlement - Distributed-ledger networks can function as settlement rails. Xflow announced a stablecoin acceptance pilot on 14 May 2026, with the stablecoin leg staying outside India. Settlement finality varies by protocol, so treat any blanket "instant and final" claim with suspicion. If this is where your interest sits, start with stablecoin payments.

Most guides compare every rail on every attribute. For an Indian exporter that's the wrong cut, because the answer collapses fast: of all the rails above, only two can put an overseas client's money in your INR account.

That's the whole routing decision. Everything else is either a leg inside one of those two routes or a domestic rail your client can't reach.

Speeds, value limits and effective dates for each of these sit in the Types section above, so they aren't repeated here.

One clarification on UPI, because it gets misread often. UPI's international presence is outbound merchant acceptance for Indians spending abroad, not a channel your overseas client can pay an invoice into. The India-Bahrain UPI-Fawri+ remittance link (November 2025) is a narrow corridor-specific exception, not general availability.

Every rail runs the same four steps, whatever its brand name. Two of them get blurred together in most explanations, and the difference matters when you're chasing a payment that hasn't arrived.

• Instruction - The payer tells their bank or platform to send a defined amount to a defined beneficiary.
• Verification and authorisation - The sending institution checks funds, identity and sanctions exposure, then authorises the instruction to move.
• Clearing - Payment instructions are transmitted, reconciled and sometimes netted between institutions. This happens before any money moves.
• Settlement - The obligation is discharged, with funds actually moving between the institutions' accounts. This happens after clearing.

The Bank for International Settlements' CPMI glossary keeps clearing and settlement as separate defined terms for exactly this reason. A payment can be fully cleared and still not settled, which is why your bank can confirm a wire "went through" while your balance hasn't changed.

A real transaction: a $10,000 invoice from a US client

An IT-enabled services (ITES) exporter in Bengaluru invoices a US client for $10,000. Here's how the two viable India-inbound routes handle it.

The correspondent-banking route. The client's US bank issues a SWIFT MT103 instruction. Correspondent banks in the chain screen and authorise it for sanctions and anti-money-laundering purposes before passing the message along.

The messages then clear between those institutions. SWIFT itself never touches the funds. Settlement happens across the correspondent banks' nostro and vostro accounts, and finally the Indian AD Category-I bank converts and credits INR to the exporter.

The PA-CB route. The client pays into a local-currency collection account in their own country, usually via a domestic rail like ACH. The PA-CB entity handles the cross-border collection and the FX conversion, then a domestic Indian rail delivers the INR. Fewer hops, and no correspondent chain to deduct from.

Getting this wrong is expensive in ways that don't show up on any single invoice. The upside of getting it right splits across five factors.

• Speed - The gap between seconds and several business days is working capital sitting idle. On a services business billing monthly, that's a permanent drag on cash conversion.
• Cost - Rail costs range from free to several hundred rupees plus an FX spread per transaction. The spread is usually the biggest line and the least visible one.
• Reach - Instant rails are mostly domestic. A rail that can't reach your client's country is not an option, however cheap it looks.
• Settlement finality - Once settlement completes, the obligation is discharged. Rails differ in when that point arrives, which affects when you can safely recognise the receipt.
• Availability - RTGS, UPI, FedNow, RTP, SEPA Inst and Pix all run 24/7/365. Batch rails and correspondent chains don't, so a Friday-evening payment can lose a weekend.

The honest problems with the traditional cross-border route are worth naming just as plainly:

• Unpredictable deductions - Correspondent banks take fees from the transferred amount depending on the charge code used, so the amount your client sends isn't the amount you receive.
• Limited visibility - Multi-hop chains give you no reliable view of where a payment is or when it'll land.
• Currency conversion opacity - Your AD bank converts at its own TT buying rate, and the gap to the mid-market rate isn't published anywhere you can check it.

Here's the part nobody publishes. The table compares the same $10,000 invoice across both viable routes, component by component. Read the source column carefully, because the honest answer for most of the correspondent chain is that the numbers aren't public.

Every cell marked illustrative is a triangulated range from secondary sources, not a figure any bank publishes. Correspondent-bank fees are negotiated bilaterally and treated as confidential, which is why no bank publishes them.

No AD bank publishes its FX margin as a fixed percentage either, because it moves daily with the bank's own TT buying rate. So on the correspondent route you can't calculate your receipt in advance, only reconcile it afterwards.

Now size it, using the illustrative ranges above:

• A $10,000 exporter invoice - Roughly $25 to $75 goes in visible fees, plus a few dollars for the Indian bank's handling charge, plus $150 to $200 in FX spread at 1.5% to 2%. The spread costs between two and eight times the visible fee line.
• A small Rs 40,000 invoice (about $420) - Fixed fees dominate instead. A flat USD 15 to 50 deduction alone can take roughly 4% to 12% of the payment before FX is applied at all.

So the FX spread, rather than the visible wire fee, is where most of the money goes. That's why an exporter can save up to 50% on FX costs by moving off a bank's own conversion rate onto a live mid-market rate with a disclosed fee.

Put it in paise, since that's the unit your bank quotes in. At USD/INR of about Rs 95.5 (July 2026), a 1.5% spread costs roughly 143 paise per dollar. The $40 in the table above works out at about 38 paise per dollar.

The rail delivers the money. It doesn't close your compliance file, and for an Indian services exporter the file is what causes trouble at audit. Three things have to happen after the funds land.

The purpose code

Every inward remittance has to be tagged with an RBI purpose code by the AD bank, for reporting under the Foreign Exchange Management Act (FEMA).

For software and IT services, RBI's current FETERS purpose-code list carries two that matter. P0802 covers software consultancy and implementation other than those covered in a SOFTEX form. P0807 covers off-site software exports, which generally require SOFTEX filing. Our RBI purpose codes directory lists the codes in full.

If the code is wrong, your bank has to file the correction, so flag it early.

The FIRC, and what "FIRA" actually means

The document RBI and FEMA recognise is the FIRC, the Foreign Inward Remittance Certificate, issued by the AD Category-I bank that receives the remittance. It's governed under RBI's Master Direction No. 16/2015-16 on Export of Goods and Services, dated 1 January 2016.

"FIRA", the Foreign Inward Remittance Advice, is industry shorthand for the same bank-issued advice, and it's the term Xflow itself uses.

If your CA asks for a FIRC and your platform hands you a Foreign Inward Remittance Advice, they're describing the same underlying proof of receipt.

EDPMS closure

EDPMS, the Export Data Processing and Monitoring System, is RBI's electronic system for AD banks to report and reconcile export-related inward remittances. Entries stay open until the bank matches the payment against the export documentation.

Most ITES and SaaS businesses have no shipping bill, so the matching document is different for them. It is either the SOFTEX software-export declaration, filed with the Software Technology Parks of India (STPI) or the SEZ authority, or the invoice and FIRC themselves for non-SOFTEX codes.

One recent change is worth knowing about. Under RBI A.P. (DIR Series) Circular No. 12 dated 1 October 2025, AD Category-I banks may close export entries of Rs 10 lakh or less on the exporter's own declaration that the amount has been realised, with quarterly consolidated declarations permitted.

Three shifts are actually changing how money moves, as opposed to being announced.

• ISO 20022 migration - Richer, structured payment messaging replacing legacy formats. Fedwire completed its migration on 14 July 2025. SWIFT's own cross-border coexistence timeline is worth checking against its programme page rather than assuming a date.
• Instant settlement becoming the default - FedNow, RTP, SEPA Inst, UPI, Pix and RTGS all now run round the clock. Regulators are increasingly mandating it rather than waiting: the EU required euro-area PSPs to fully support instant euro payments by 9 October 2025.
• Central bank digital currencies - The RBI is piloting a retail and wholesale digital rupee. Published pilot figures move often, so we're not quoting one here.

Stablecoin settlement belongs in the same list, with a caveat: finality depends on the specific protocol, so it isn't one uniform claim you can plan treasury around.

If you're receiving export earnings into India, the rail question resolves into a routing question.

The correspondent-banking wire works everywhere and costs you an amount you can't calculate in advance. A domestic instant rail is cheap and fast but can't reach your client. So the practical choice is who handles the cross-border collection and the FX conversion before a domestic rail delivers your INR.

That's the specific job Xflow does, and it's worth being precise about the boundary. Xflow doesn't operate SWIFT, ACH, SEPA, UPI, RTGS or any card network. It handles the cross-border collection and the FX leg, and a domestic Indian rail delivers the rupees afterwards. What that looks like in practice:

• Local collection instead of a correspondent chain - Your client pays into a local-currency receiving account in their own country, so there's no multi-hop deduction sequence between their bank and yours.
• A live mid-market rate with a disclosed fee - You see the rate you're converting at and the fee you're paying before the payment lands, rather than reconciling a spread afterwards.
• T+1 settlement - Funds reach your bank account on the next business day.
• Compliance closed automatically - eFIRA is auto-issued on every receipt, with purpose codes applied, so your EDPMS and GST-refund workflow carries on unchanged.
• Credentials worth checking - Final Payment Aggregator - Cross Border (PA-CB) authorisation from the RBI covering both exports and imports, as of February 2026, plus ISO 27001 and SOC 2 certification.

Xflow works with 20,000+ customers, supports payments from 140+ countries, and receives in 25+ currencies.

Whether that's the right routing choice depends on your corridors and on what your bank currently charges you. The arithmetic in the cost section above is the test worth running on your own numbers.