You're building a payment platform that needs to handle cross-border settlements for merchants in Lagos and Nairobi. A $10,000 B2B payment through traditional correspondent banking costs $25–$100+ in direct fees, plus FX markups that can add another 2–5% on African corridors. It takes three to five business days. Send that same payment on-chain as USDC, and it costs under $0.10 and confirms in seconds.
But here's the catch: That Layer-2 network processes roughly 1,000 transactions per second in practice. A single tuned PostgreSQL instance handles 70,000+. For high-volume payment processing, you can't put every transaction on-chain. Do you go on-chain, off-chain, or both?
If you've been wrestling with this question, you're asking the wrong one. The on-chain vs. off-chain debate misses the point. The better question is: Which parts of your payment flow benefit from blockchain finality, and which parts need database speed?
This guide is for engineering leads and payment architects evaluating whether to add blockchain settlement to their payment stack. It covers cost and performance tradeoffs, when blockchain settlement adds value, hybrid architecture patterns, and a decision framework for your specific payment flows.
Why the On-Chain vs. Off-Chain Debate Misses the Point
Most content about on-chain vs. off-chain transactions falls into two camps. Crypto-native content claims everything should be on-chain for transparency and decentralization. Traditional fintech content dismisses blockchain entirely because databases are faster and cheaper. Both positions miss the point.
Here's what they get wrong: Traditional payments already use hybrid architecture. When you swipe a card at a store, Visa authorizes the transaction in real-time, in under one second. But actual settlement happens in daily batch cycles where net obligations between issuing and acquiring banks are calculated and transferred. Millions of off-chain transactions roll up into periodic settlements.
The practical question isn't on-chain vs. off-chain. It's which payment flows need public finality, counterparty trust, or cross-border settlement, and which need speed, privacy, or cost optimization.
You have three architecture patterns to choose from. Pure off-chain uses traditional database-based processing. Pure on-chain puts every transaction on the blockchain. Hybrid combines off-chain processing with periodic on-chain settlement. Most production payment systems that interact with blockchain use a hybrid approach.
If you're building cross-border payment infrastructure, understanding this distinction matters for every technical decision.
Understanding On-Chain Payments
When a payment happens on-chain, the transaction gets recorded on a public blockchain like Ethereum or Polygon. Network validators verify it. Once confirmed, the transaction becomes immutable.
On-chain transactions have four characteristics that matter for payment systems.
Finality: After confirmation, the transaction can't be reversed. Ethereum mainnet achieves finality in ~13–15 minutes (2 epochs under Proof-of-Stake). Layer-2 networks like Base or Arbitrum provide sequencer confirmation (block inclusion) in 2–5 seconds, though true finality depends on Ethereum L1 (~15+ minutes) and withdrawals to L1 carry a 7-day challenge window for optimistic rollups.
Transparency: Anyone can verify that a transaction occurred. This is useful for audits, dispute resolution, and regulatory reporting.
Counterparty trust elimination: The blockchain enforces settlement. No intermediary is required, and no party needs to trust the other's internal ledger.
Cost: Every on-chain transaction incurs gas fees. Ethereum mainnet typically runs $0.30–$0.50 for a token transfer during low-traffic periods, though fees are volatile and can spike significantly. Layer-2 networks charge $0.003–$0.09 for token transfers after the Dencun upgrade slashed data-posting costs by 90 percent or more.
On-chain settlement makes sense for high-value B2B transactions where finality justifies the cost, cross-border settlements where you want to eliminate correspondent banks, and situations where counterparties don't trust each other's internal systems.
Understanding Off-Chain Payments
Off-chain payments record transactions in application databases, APIs, or internal ledgers without involving the blockchain for each payment. This is how most payment processing works today.
Speed: Database write latency runs 10–50 milliseconds. Users see instant confirmation.
Cost: Per-transaction cost is negligible: just server and database expenses. No gas fees.
Privacy: Transaction details stay private to system participants. No public visibility.
Scalability: Hundreds of thousands of transactions per second are achievable with proper infrastructure. You're limited by database and server capacity, not blockchain throughput.
Trust requirement: Users must trust the platform operating the ledger. If Flutterwave processes your payment off-chain, you're trusting Flutterwave's systems.
Off-chain gives you speed and cost efficiency. On-chain gives you trustless finality. Most payment platforms combine both: off-chain for user-facing transactions where speed matters, with periodic on-chain settlement for finality.
So how do these tradeoffs look in practice?
The Cost and Performance Tradeoffs
Choosing between on-chain and off-chain comes down to three variables: cost per transaction, settlement speed, and throughput capacity. The tables below compare these across internal ledgers, traditional rails, and blockchain networks.
Note: Transaction costs and network throughput metrics are estimates as of Q1 2026 and are subject to network volatility and corridor-specific pricing.
Transaction Costs Across Different Approaches
Sources: Card network fees based on Visa and Mastercard published interchange fee schedules (updated semiannually). SWIFT costs per World Bank Remittance Prices Worldwide and Bankrate (2026). Mobile money fees per GSMA State of the Industry Report on Mobile Money 2025 (domestic P2P). On-chain gas fees based on Etherscan, PolygonScan, Arbiscan, and L2fees.info gas trackers (Q1 2026 snapshots). Internal ledger cost derived from AWS RDS and GCP Cloud SQL per-write pricing estimates.
Note: Internal ledger costs exclude compliance, fraud detection, and reconciliation overhead. Traditional rails include these costs. On-chain costs are gas fees for token transfers (e.g., USDC, USDT) and don't include custody or bridging infrastructure.
Settlement Speed
| Approach | Confirmation | Settlement finality |
|---|---|---|
| Off-chain (internal ledger) | <100ms | T+1 to T+3 (depends on payout rails) |
| Layer-2 (sequencer confirmation) | 2–5 seconds | ~15+ min (L1 finality) |
| Ethereum mainnet | ~12 seconds | ~13–15 minutes |
| Polygon PoS | ~2 seconds | ~30 min (checkpoint to L1) |
| Traditional cross-border (SWIFT) | Minutes | 1–5 business days |
Note: "Confirmation" is when the user sees success. "Settlement finality" is when funds are irreversibly transferred.
Throughput
| Approach | Transactions per second |
|---|---|
| PostgreSQL (tuned) | 70,000+ (simple operations) |
| Solana | ~1,000 effective (~3,500 including validator votes) |
| Polygon PoS | 700–1,400 |
| Base | ~1,000 |
| Ethereum mainnet | 15–20 |
Note: These aren't equivalent workloads. A PostgreSQL write inserts a row. An Ethereum transaction involves consensus across thousands of nodes, cryptographic verification, and global state changes. The numbers show raw capacity, not like-for-like comparison.
The Visa TPS Myth
Visa's commonly cited "65,000 TPS" is a theoretical peak capacity from 2017. Their actual average throughput, calculated from 233.8 billion transactions in fiscal year 2024, runs approximately 7,400–9,300 TPS. Still higher than any blockchain, but not the gap marketing materials suggest.
But even before you hit throughput limits, the economics break down. Consider an e-commerce platform processing 50,000 transactions daily (barely 1 TPS):
- Pure on-chain (mainnet): $15,000–$25,000 daily in fees. Uneconomical.
- Pure on-chain (Layer-2): $150–$4,500 daily in fees. Expensive but possible.
- Off-chain with daily batched settlement: $0.30–$0.50 daily per merchant (rolling up thousands of user payments into a single end-of-day settlement transaction). Highly economical.
The math points clearly toward hybrid architecture for high-volume use cases.
When On-Chain Settlement Makes Sense
On-chain settlement adds value in specific scenarios.
Cross-border B2B settlements: Traditional correspondent banking takes 1–5 days and costs $25–$100+ in fees, plus FX markups of 2–5 percent above mid-market rates. Stablecoin settlement on a Layer-2 network provides finality in seconds for under $0.10. For a remittance company settling with a partner bank in Nairobi, the economics favor on-chain settlement.
The infrastructure for cross-border stablecoin payouts is expanding fast. USDC has processed over $25 trillion in cumulative on-chain transaction volume since 2018, with Q3 2025 alone accounting for roughly $9.6 trillion. PayPal launched PYUSD stablecoin in 2023, Visa has run stablecoin settlement pilots since 2021, and Mastercard announced stablecoin payment capabilities in 2024.
High-value transactions requiring immediate finality: Off-chain ledgers can theoretically be reversed by the platform operator. On-chain settlement means the transaction becomes irreversible after confirmation. For property purchases, large B2B invoices above $100,000, or transactions where finality certainty justifies the cost, on-chain provides assurance.
Counterparty distrust scenarios: When international partners don't trust each other's internal ledgers, a neutral blockchain provides shared truth. Neither party can alter the record unilaterally.
Regulatory transparency requirements: Some jurisdictions require auditable transaction records. Public blockchains provide an immutable audit trail for regulatory reporting.
Regulatory Considerations
Compliance requirements vary by jurisdiction, but regulators generally focus on outcomes (transparency, auditability, consumer protection), not implementation specifics.
MiCA (EU): Fully enforced since December 2024, MiCA classifies stablecoins as E-Money Tokens or Asset-Referenced Tokens. It requires 1:1 liquid reserves, segregated custody, and regular audits. But it doesn't mandate that every payment transaction be on-chain. Off-chain processing is allowed as long as issuers can prove reserves. The practical impact: Several major EU exchanges restricted or delisted USDT for retail users under MiCA compliance requirements, while USDC remains available as the first MiCA-compliant global stablecoin.
Nigeria's ISA 2025: Signed in March 2025, this law expands the definition of securities to include digital assets, bringing them under SEC oversight. VASPs must meet capital adequacy requirements and comply with Travel Rule requirements per FATF guidance. On-chain isn’t mandated, but audit trails are.
Kenya's VASP Act 2025: Signed in October 2025, it introduces a licensing framework with the Central Bank of Kenya overseeing stablecoin issuers. Detailed regulations are still pending.
The pattern across jurisdictions: Regulators care about auditability and transparency, which can be achieved through off-chain audit logs. On-chain settlement is one way to achieve compliance, not the only way.
On-chain works for specific use cases. For many payment flows, off-chain is the better choice.
When Off-Chain Is Superior
Off-chain processing works better in several scenarios.
High-frequency, low-value transactions: When gas fees exceed a meaningful percentage of transaction value, off-chain is the only practical choice. Mobile money transfers of $5–$50, in-app purchases, subscription payments — these belong off-chain with batch settlement.
Privacy requirements: On-chain transactions are visible to anyone with blockchain access. For payroll, healthcare payments, or any scenario where transaction privacy matters, off-chain keeps details internal.
Instant user experience: Even fast blockchains add seconds of latency that users notice at checkout. For e-commerce, point-of-sale, and peer-to-peer transfers, off-chain processing gives instant feedback. Settle on-chain later.
Complex transaction logic: Multi-party splits, conditional payments, subscription billing with trials — these take more effort to implement and maintain in smart contracts than in application code. Off-chain gives you the full power of your application code.
Most production systems don't choose one or the other. They combine both.
Hybrid Architecture Patterns
Most production systems use a hybrid pattern. The blockchain handles the middle mile (settlement between counterparties) while traditional systems handle customer-facing processing, identity verification, and local currency conversion.
Pattern 1: Off-chain transactions with batch settlement: Process transactions in your internal ledger instantly, with no blockchain fees. At end of day (or week), aggregate and settle the net balance on-chain with a single transaction.
Picture 10,000 daily payments totaling $500,000. Settling each one individually on a Layer-2 network would cost $30–$900 in gas fees. Batch them into a single end-of-day settlement, and you pay a few cents.
Pattern 2: Threshold-based routing: Route transactions by value. Payments under a threshold (say, $1,000) batch-settle off-chain daily, while larger transactions settle immediately on-chain for the finality assurance that justifies the gas cost.
Pattern 3: On-chain settlement with off-chain metadata: Record the value transfer on-chain. Sender, receiver, and amount are publicly verifiable. Store everything else (customer info, order details, line items) in your database. You get blockchain proof of payment without exposing sensitive data or bloating transaction costs.
Pattern 4: Layer-2 with mainnet checkpoints: Process transactions on a Layer-2 for speed and low cost. The Layer-2 periodically posts batch proofs to Ethereum mainnet for ultimate security. You get Layer-2 economics with mainnet guarantees.
For most payment platforms, Pattern 1 (batch settlement) or Pattern 2 (threshold routing) makes the most sense. They're simpler to implement and provide the best balance of cost, speed, and finality.
Decision Framework: Questions to Determine Your Architecture
Work through these questions with your team to determine your approach.
1. What's Your Transaction Volume and Value Distribution?
- Under 1,000 transactions daily, mostly under $100: Off-chain is sufficient. Batch-settle daily.
- 1,000–50,000 transactions daily with mixed values: Hybrid. Off-chain for smaller amounts, on-chain for larger ones.
- Over 50,000 transactions daily, mostly under $100: Pure off-chain with daily batch settlement.
- High-value transactions over $10,000, regardless of volume: Benefit from on-chain settlement for faster finality.
2. Do You Need Immediate Settlement Finality?
- Yes, within seconds: On-chain via Layer-2.
- Yes, but hours are acceptable: Off-chain with hourly batch settlement.
- T+1 or T+3 acceptable: Off-chain with daily or weekly settlement.
3. Are You Processing Cross-Border Payments?
- Yes, and settlement with international partners is critical: On-chain eliminates correspondent banks.
- Yes, but only for accounting: Off-chain with periodic reconciliation.
- Domestic only: Off-chain likely sufficient.
4. What's Your Privacy Requirement?
- High (payroll, healthcare): Off-chain keeps details private.
- Medium (e-commerce): Hybrid. On-chain value transfer, off-chain metadata.
- Low (public transparency valuable): On-chain provides the audit trail.
5. Do Users Expect Instant Confirmation?
- Yes, under 100 milliseconds required: Off-chain for UX, settle later.
- 2–5 seconds acceptable: Layer-2 on-chain is feasible.
- Asynchronous (B2B invoices): Settlement timing is less critical; optimize for cost.
6. How Much Blockchain Complexity Can Your Team Handle?
- Low (small team, product focus): Off-chain is simpler. Avoid blockchain complexity until you need it.
- Medium: Consider Layer-2 for the best balance.
- High (blockchain engineers on staff): Sophisticated hybrid patterns are possible.
7. What's Your Regulatory Exposure?
- Heavy transparency requirements: On-chain provides built-in auditability that can simplify compliance.
- Regulated but implementation-agnostic: Off-chain with strong audit trails is sufficient.
- Minimal regulation: Optimize for cost and performance.
How Flutterwave Can Help With Hybrid Architecture
Building payment infrastructure that spans traditional rails and blockchain settlement is complex. It requires understanding both worlds and designing systems that move smoothly between them. Flutterwave processes billions of dollars annually across traditional payment rails (cards, bank transfers, mobile money) with coverage across 30+ African countries. That operational experience informs how we think about blockchain integration: pragmatically, not ideologically.
Blockchain settlement adds value for cross-border finality and cost reduction in specific corridors. Traditional infrastructure performs better for high-frequency domestic transactions.
For developers, this means APIs that abstract complexity. You shouldn't need to understand gas fees or bridge mechanics to process payments. Flutterwave handles the infrastructure decisions so you can focus on your product.
Each payment system should go off-chain, on-chain, or hybrid according to the team's specific needs. The decision framework in this guide helps you evaluate your options. When you're ready to implement, explore Flutterwave's payment APIs for traditional payment capabilities and StableRails for stablecoin settlement.
Top comments (0)