The average international remittance still costs 6.36% of the transfer amount, according to the World Bank's Remittance Prices Worldwide, Issue 54 (Q3 2025). For a worker sending $400 home every month, that is over $305 lost to fees every year — money that never reaches the family it was meant for.
Bitcoin's Lightning Network offers a fundamentally different architecture. Instead of routing payments through correspondent banks or even a blockchain ledger for every transaction, Lightning uses pre-funded payment channels that settle instantly for under a single cent. A $500 transfer to Mexico via Lightning costs roughly the same as a $5 transfer: almost nothing.
But Lightning is not magic. It requires an on-ramp (buying Bitcoin), a network of payment channels with sufficient liquidity, and an off-ramp exchange in the destination country that supports BTC withdrawals. This guide explains exactly how each piece works, which corridors support Lightning today, and how it compares to stablecoin alternatives like USDC on Stellar.
Bitcoin's base layer (Layer 1) processes roughly 7 transactions per second and charges variable fees — sometimes $5, sometimes $50, depending on network congestion. For small, frequent remittances, those dynamics make Bitcoin Layer 1 impractical.
The Lightning Network is a Layer 2 protocol built on top of Bitcoin. It was introduced in a 2016 white paper by Joseph Poon and Thaddeus Dryja and became operational in 2018. Rather than recording every payment on the Bitcoin blockchain, Lightning lets two parties open a payment channel by locking Bitcoin in a multi-signature address on-chain. Once the channel is open, they can send unlimited payments back and forth instantly — only the opening and closing of the channel touch the blockchain.
The network effect comes from channel routing. If Alice has a channel with Bob, and Bob has a channel with Carol, Alice can pay Carol through Bob without opening a direct channel. Payments route across a web of interconnected channels using a technique called source routing with Hash Time-Locked Contracts (HTLCs), which ensure that either the payment completes atomically or the funds are returned. No intermediary can steal funds mid-route.
Fees on routed payments are tiny — typically 1 to 100 satoshis (one satoshi = $0.0000006 at $60,000 BTC). A $500 remittance might cost 500 satoshis in routing fees: roughly $0.03. That is not a typo.
~6,000 BTC — Total public Lightning Network channel capacity as of early 2026 (1ML.com Lightning Statistics)
A Lightning remittance has three distinct stages: on-ramp, Lightning transfer, and off-ramp. Understanding each stage helps you evaluate real costs and speeds for your corridor.
The on-ramp is where you convert your local currency (USD, EUR, GBP) into Bitcoin. Platforms like Strike (United States, zero fees on the Lightning layer), Coinbase, and Kraken are common on-ramps. Strike is notable because it abstracts the Bitcoin entirely — you send dollars, Strike converts to BTC, routes over Lightning, and the recipient receives local currency on the other end, all in one step.
The Lightning transfer happens in seconds. Once Bitcoin is on the Lightning Network, payments route through the channel graph to the destination node. For a well-connected network with adequate liquidity, this step is invisible to the user — it completes before they finish reading a confirmation message.
The off-ramp is where the recipient's exchange converts Bitcoin back into local currency (MXN, INR, BRL, IDR) and pays out to a bank account or mobile wallet. Exchanges like Bitso (Mexico), CoinDCX (India), Mercado Bitcoin (Brazil), and Indodax (Indonesia) support BTC off-ramps. The off-ramp step typically takes 10–60 minutes for the bank deposit, though the Bitcoin itself arrives in seconds.
For senders in the United States, Strike offers zero-fee Lightning remittances to supported corridors. Coinbase and Kraken also support Lightning withdrawals at a flat fee of approximately $0.02–$0.05 per transaction. Choose based on your send currency and the corridor you need.
Verify that your on-ramp supports Lightning Network withdrawals specifically — not just regular Bitcoin (Layer 1) withdrawals. Lightning withdrawals are labeled as 'Lightning' or 'LN' in the withdrawal interface.
Tip: Strike's 'Send Internationally' feature handles on-ramp, Lightning routing, and off-ramp in a single step for supported corridors (Mexico, El Salvador, Nigeria, Philippines as of 2026). This eliminates manual off-ramp coordination.
Not every country has a regulated exchange with BTC/local currency trading and Lightning Network deposit support. Before committing to a Lightning path, verify that the destination exchange is operational and accepting Lightning deposits.
As of March 2026, Lightning off-ramps with meaningful liquidity exist for: Mexico (Bitso — BTC/MXN), India (CoinDCX — BTC/INR), Brazil (Mercado Bitcoin — BTC/BRL), and Indonesia (Indodax — BTC/IDR). Nigeria (Luno) and South Africa (VALR) list BTC/NGN and BTC/ZAR pairs but currently price BTC at a significant premium above the mid-market rate, making the effective cost uncompetitive.
Tip: Use RemitRoutes to check live Lightning path costs for your corridor. The calculator shows the real all-in cost including on-ramp fees, routing fees, and off-ramp spread — so you can compare Lightning against USDC on Stellar or traditional providers in one view.
Once you have funded your on-ramp and the recipient has a Lightning-compatible wallet or exchange address, initiate the transfer. You will either scan a Lightning invoice (a QR code or alphanumeric string starting with 'lnbc') or use an app like Strike that generates the invoice automatically.
The payment routes through the Lightning Network in seconds. You will see a confirmation — typically a green checkmark and a transaction hash — within 5–15 seconds for well-routed payments. If routing fails (insufficient channel liquidity along the path), your on-ramp will retry with an alternate route or refund the payment automatically.
If you used Strike's integrated flow, this step is automatic — the recipient receives local currency in their account without handling Bitcoin at all. If you used a manual on-ramp/off-ramp flow, the recipient needs to sell BTC on their local exchange and withdraw to a bank account or mobile money wallet.
Off-ramp settlement times vary: Bitso (Mexico) typically settles MXN to SPEI in 10–30 minutes. CoinDCX (India) settles INR via IMPS in 30–60 minutes. Always factor this final leg into your total transfer time estimate.
| Method | On-ramp Fee | Transfer Fee | Off-ramp/FX Cost | Total Cost | Speed |
|---|---|---|---|---|---|
| Lightning (Strike) | $0 | ~$0.01 | ~0.3% spread (Bitso) | ~$1.50 | < 1 hour |
| USDC on Stellar | ~0.4% (Coinbase) | $0.01 | ~0.2% (off-ramp) | ~$3.00 | < 1 hour |
| Wise | $4.20 flat | Included | 0% FX markup | ~$4.20 | 1–2 days |
| Remitly (Express) | $3.99 | Included | ~1.5% FX spread | ~$11.50 | Minutes |
| Western Union (online) | $5.00 | Included | ~2% FX spread | ~$15.00 | Minutes–1 day |
| Bank Wire (SWIFT) | $25–45 | Included | 2–4% FX markup | $35–65 | 2–5 days |
Unlike USDC on Stellar (which is pegged 1:1 to the US dollar), Lightning transfers involve actual Bitcoin. If BTC price drops 3% during the 60 minutes between your on-ramp and the recipient's off-ramp, the recipient receives 3% less than expected. For large transfers or volatile markets, this exposure can exceed the fee savings. Strike's integrated flow mitigates this by locking a rate at initiation, but manual on-ramp/off-ramp flows carry full BTC price risk. For risk-sensitive senders, USDC on Stellar or Tron may be a better fit.
Lightning and USDC-on-Stellar are both sub-cent, sub-minute transfer technologies, but they have meaningfully different risk profiles and corridor coverage.
USDC on Stellar has broader corridor support because Stellar's exchange infrastructure (including Anchors like MoneyGram and local fintechs) covers more countries. The asset is a dollar-pegged stablecoin, so there is zero price volatility during transit. For most senders who want crypto economics without BTC exposure, USDC on Stellar is simpler and lower risk.
Lightning Network has lower raw fees (routing fees are closer to zero versus Stellar's 0.00001 XLM per transaction, both negligible) and is more decentralized — no single issuer controls BTC the way Circle controls USDC. For corridors where BTC off-ramp liquidity is competitive (Mexico, India, Brazil, Indonesia), Lightning can match or beat Stellar on total all-in cost.
The practical choice depends on your corridor. For USD → MXN and USD → INR, Lightning via Strike is highly competitive. For USD → NGN and USD → PHP, USDC on Stellar has better off-ramp infrastructure today. Run both scenarios on RemitRoutes to see which wins for your specific amount and corridor.
| Feature | Lightning Network (BTC) | USDC on Stellar |
|---|---|---|
| Settlement time | 1–10 seconds | 3–5 seconds |
| Transfer fee | < $0.01 | < $0.01 |
| Price volatility | Yes (BTC) | None (USD-pegged) |
| Corridor coverage | Mexico, India, Brazil, Indonesia (strong) | 360+ corridors (broader) |
| On-ramp options | Strike, Coinbase, Kraken | Coinbase, Kraken, Gemini |
| Off-ramp complexity | Medium (local BTC exchange) | Low (Stellar Anchors) |
| Custodial risk | Low (non-custodial wallets available) | Medium (USDC is custodial) |
| Regulatory clarity | High (Bitcoin is legal in most jurisdictions) | High (USDC is regulated) |
Lightning corridor viability depends on two factors: an active BTC off-ramp exchange in the destination country, and competitive BTC pricing on that exchange. An exchange with a 15% premium over mid-market makes Lightning more expensive than a bank wire.
As of March 2026, the four corridors where Lightning is genuinely cost-competitive are: USD/EUR/GBP → MXN (Mexico via Bitso), USD/EUR/GBP → INR (India via CoinDCX), USD/EUR/GBP → BRL (Brazil via Mercado Bitcoin), and USD/EUR/GBP → IDR (Indonesia via Indodax). In each of these corridors, the BTC/local-currency spread on the off-ramp exchange is within 0.5–1.5% of mid-market, making the total Lightning path cost under 2%.
Two corridors that have BTC off-ramps but are not cost-competitive today: NGN (Nigeria via Luno, where BTC/NGN trades at a significant premium due to local FX controls) and ZAR (South Africa via VALR, where the BTC/ZAR spread is currently wide). For these corridors, USDC on Tron or Stellar delivers better economics.
Lightning is not yet viable for several major corridors including PHP (Philippines), KES (Kenya), GHS (Ghana), and PKR (Pakistan) because no regulated exchange with Lightning deposit support and competitive BTC pricing operates in those markets. This may change as Lightning adoption grows globally.
4 corridors — Where Lightning Network is cost-competitive for remittances as of March 2026 (RemitRoutes live rate analysis)
Let's walk through a concrete example: a US-based sender transferring $500 to a family member in Mexico using Strike's Lightning integration.
On-ramp cost: Strike charges 0% on the first $1,000 per month for verified US users. No fee. Strike purchases BTC at the mid-market rate and routes over Lightning immediately.
Lightning routing fee: Approximately 1,000–5,000 satoshis on a $500 transfer, equivalent to $0.06–$0.30 at $60,000 BTC. Negligible.
Off-ramp FX spread: Bitso converts the received BTC to MXN at approximately 0.3–0.8% below mid-market (their bid/ask spread). On $500, this costs roughly $1.50–$4.00.
Total all-in cost: $1.50–$4.30 on a $500 transfer, or 0.3–0.86%. This compares to Wise at ~0.84% ($4.20), Remitly at ~2.3% ($11.50), and bank wires at 7–13% ($35–65).
Speed: BTC arrives at Bitso's Lightning node in under 10 seconds. Bitso converts to MXN and processes the SPEI bank transfer within 10–30 minutes. Total door-to-door time: under one hour, even outside banking hours.
BTC/local-currency spreads on off-ramp exchanges fluctuate daily based on local demand and liquidity. A corridor that costs 0.5% today might cost 1.8% next week if local exchange liquidity drops. Always run a live comparison on RemitRoutes before sending to confirm that Lightning is still the cheapest path for your amount and corridor.
Lightning is genuinely impressive technology, but it has real limitations that matter for remittance use cases.
Liquidity constraints: Large transfers can fail if there is insufficient inbound liquidity along the routing path. Most Lightning channels are sized for small payments. A $10,000 transfer may fail to route where a $500 transfer succeeds easily. For large transfers, SWIFT, Wise, or USDC on Stellar is more reliable.
Channel management complexity: Running your own Lightning node (for maximum privacy and control) requires technical knowledge and ongoing maintenance. Consumer-facing apps like Strike abstract this entirely, but they are custodial — you do not hold your own keys.
Regulatory uncertainty: While Bitcoin is legal in most remittance corridors, some countries (Nigeria, Tanzania, Algeria) have restrictions on cryptocurrency use that may affect your ability to convert to local currency. Always verify local regulations before using crypto remittance rails.
Internet dependency: Lightning payments require both sender and recipient nodes to be online. Offline or intermittent connectivity can cause payment failures. This matters in regions with unreliable internet infrastructure.
BTC volatility window: Even with a 30-minute transfer window, BTC can move 1–3% on volatile days. For $200–$500 transfers, this risk is modest. For $5,000+ transfers, consider stablecoin alternatives.
Lightning Network adoption is accelerating. El Salvador's Bitcoin legal tender law (2021) created a national Lightning infrastructure. Strike expanded internationally in 2023–2024. Major exchanges including Coinbase, Kraken, Bitfinex, and Binance have added Lightning support. The number of public Lightning nodes has grown to over 14,000 globally.
The most significant development for remittances is the emergence of Lightning service providers (LSPs) that manage channel liquidity on behalf of end users. Apps built on LSPs like the Lightning Development Kit (LDK) or Phoenix Wallet give users a non-custodial Lightning experience without the complexity of node management. This makes Lightning viable for less technically sophisticated remittance senders.
Interoperability is also improving. Protocols like Taproot Assets allow dollar-denominated Lightning payments — essentially stablecoin transfers over the Lightning Network — which would eliminate BTC price volatility while retaining Lightning's fee and speed advantages. If Taproot Assets gains exchange support, Lightning could combine the best of both worlds: Bitcoin's decentralization and USDC's price stability.
For remittance senders today, the practical advice is: use Lightning for Mexico, India, Brazil, and Indonesia where it is already cost-competitive. For all other corridors, USDC on Stellar or Tron remains the lowest-cost option. As Lightning infrastructure expands, this picture will change — check RemitRoutes regularly to see when Lightning becomes viable for your corridor.
RemitRoutes compares Lightning Network, USDC on Stellar, USDC on Tron, Wise, Remitly, and more — with live rates, real fees, and total all-in costs for 360+ corridors.
The Bitcoin payment over Lightning settles in under 10 seconds. The total transfer time including off-ramp bank deposit is typically 10–60 minutes depending on the destination exchange. This is significantly faster than Wise (1–2 days) or bank wires (2–5 days).
Lightning routing fees are typically under $0.01 regardless of transfer amount. The main costs are the on-ramp fee (0% on Strike for US users, ~0.4% on Coinbase) and the off-ramp BTC/local-currency spread (0.3–1.5% depending on the destination exchange). Total all-in cost for a $500 transfer is typically $1.50–$5.00, or 0.3–1%.
As of March 2026, Lightning is cost-competitive for four destination currencies: MXN (Mexico via Bitso), INR (India via CoinDCX), BRL (Brazil via Mercado Bitcoin), and IDR (Indonesia via Indodax). Strike also supports El Salvador and the Philippines in some flows. Other corridors lack competitive BTC off-ramp infrastructure today.
Lightning payments are secured by Bitcoin cryptography and Hash Time-Locked Contracts, which guarantee atomic completion or refund. Consumer apps like Strike are custodial and regulated as money services businesses in the US. The main risks are BTC price volatility during transit (typically 30–60 minutes) and off-ramp exchange counterparty risk. For risk-sensitive senders, USDC on Stellar eliminates price volatility while offering similar speeds.
Bitcoin Layer 1 (on-chain transactions) costs $2–$50 per transaction depending on network congestion and takes 10–60 minutes for confirmation. It is impractical for small, frequent remittances. Lightning Network is a Layer 2 protocol that routes payments through pre-funded channels, costing under $0.01 and settling in seconds. For remittances, always use Lightning rather than on-chain Bitcoin.
Yes, with Strike. Strike's 'Send Internationally' feature handles everything: you enter a dollar amount, Strike converts to BTC, routes over Lightning, and the recipient receives local currency in their bank account. You never interact with Bitcoin directly. For more technically oriented users, apps like Wallet of Satoshi or Phoenix Wallet provide non-custodial Lightning access.
For supported corridors (Mexico, India, Brazil, Indonesia), Lightning via Strike is typically 50–75% cheaper than Wise and 5–10x faster. Wise charges a flat fee of $3–7 plus 0% FX markup, totaling ~0.8–1.5% on a $500 transfer. Lightning costs 0.3–1% all-in and settles in under an hour versus 1–2 days for Wise. However, Wise covers 70+ corridors while Lightning is only competitive in 4 today.
A Lightning invoice is a payment request — a QR code or alphanumeric string (starting with 'lnbc') that encodes the recipient's Lightning address, the amount, and an expiry time (usually 30–60 minutes). You scan or paste the invoice in your Lightning wallet or app to initiate the payment. If you use Strike's integrated flow, the invoice is generated automatically and you never see it directly.
Compare live rates across 370+ corridors on RemitRoutes · methodology.