Ethereum's payment story changed when L2s became viable. A USDC transfer that costs $3 on mainnet costs ~5 cents on Base, near zero on Polygon. That gap restructures which payment flows are economical — recurring subscriptions, micropayments, retail checkout — and shifts the question from "is crypto payment fast enough?" to "which scaling network fits which customer base?"
Four Ethereum-scaling networks dominate merchant flows: Arbitrum, Optimism, Base, and Polygon. They're often lumped together as "L2s" — though Polygon PoS is technically a sidechain — and they overlap meaningfully in capability. But they differ in customer base, ecosystem anchors, and what each wins at. This post is the side-by-side.
The four networks at a glance
| Network | Type | Native asset | Key stablecoin | Anchor / ecosystem |
|---|---|---|---|---|
| Arbitrum One | Optimistic rollup (Arbitrum Nitro) | ETH | USDC, USDT | Largest L2 by TVL; DeFi default |
| Optimism | Optimistic rollup (OP Stack) | ETH | USDC, USDT | Original OP Stack; Synthetix / Velodrome ecosystem |
| Base | Optimistic rollup (OP Stack) | ETH | USDC (native) | Coinbase-built; U.S. consumer on-ramp |
| Polygon PoS | Sidechain (PoS) | POL | USDC (native + USDC.e), USDT | Large dev community; gaming + NFT mindshare |
Common ground: all four are EVM-compatible. All four route gas in cents (or fractions thereof) for a typical stablecoin transfer. All four have native USDC issuance — no bridge-asset dependency. All four are routed by MixPay through a single integration.
Where they diverge: customer base, ecosystem default, and the developer mindshare that shapes which wallet your customers actually open at checkout.
When each one wins
Base — U.S. consumer / Coinbase-funded checkout
Base is the L2 to default to when your customer base is U.S. consumer-leaning. The Coinbase relationship is the asymmetric advantage: a U.S. buyer with a Coinbase account can move funds to a self-custody Base wallet through a flow Coinbase has invested specifically in making short. That on-ramp shape doesn't exist on the other L2s.
For specifics on how MixPay routes Base, see Base on MixPay.
Arbitrum — DeFi-adjacent commerce
Arbitrum carries the largest L2 TVL by a comfortable margin and has the most active DeFi ecosystem. If your customers are active in DeFi protocols — yield farming, derivatives, liquid staking — Arbitrum is the L2 their wallets are most likely on. Stablecoin liquidity is the deepest of the three rollups here; ETH-on-Arbitrum is ubiquitous.
The earlier post on L2 stablecoin support covers Arbitrum and Optimism together — see Layer 2 payment support on Arbitrum and Optimism.
Optimism — OP Stack alignment, Web3-native commerce
Optimism is the chain to default to when your project is part of the OP Stack ecosystem (Superchain, Velodrome, Synthetix-aligned products). For everyone else, Optimism is a perfectly good L2 alongside Arbitrum — the trade-offs at a payment level are minor.
Polygon PoS — cheapest gas, highest volume tolerance
Polygon's gas costs are the lowest of the four. For a merchant accepting recurring payments, gaming microtransactions, NFT marketplace fees, or any flow where the per-transaction value is small and the volume is high, Polygon PoS is the rail to default to. The trade-off is the security model: as a sidechain, Polygon PoS doesn't inherit Ethereum's full security guarantees. For short-lived payment flows this rarely matters in practice.
For the per-chain detail, see Polygon PoS on MixPay.
The customer side — wallets and chain switching
A practical observation: most retail customers don't manually pick chains. They open whichever wallet their previous transaction left them in. That means the L2 your customers are already on is more important than the L2 with the best technical specs.
- Coinbase Wallet users → defaults to Base for many on-chain interactions.
- MetaMask users → defaults to Ethereum mainnet, but L2 networks are available with one click after they've been added.
- Phantom / OKX users → primarily Solana / EVM-compatible chain depending on configuration.
- Binance Pay / Trust Wallet users → BSC defaults, but support for L2s through MetaMask-compatibility.
MixPay's job at the chain layer is to surface the right L2 option based on what the customer's wallet supports. The merchant doesn't need to model wallet defaults; the asset/chain selector at checkout reflects what's available.
How L2 payments stack against mainnet
For most merchant flows the L2 wins. The headline comparison:
| Concern | Ethereum mainnet | L2 (typical) |
|---|---|---|
| Gas for USDC transfer | $1–$5 | $0.01–$0.10 |
| Confirmation time | 12–15 seconds | sub-second to a few seconds |
| Settlement to L1 | immediate | varies (rollup challenge windows) |
| Wallet ubiquity | every wallet | most wallets, with chain switch |
| Liquidity depth | deepest in crypto | very deep, especially USDC |
The cases where mainnet still wins:
- High-value B2B invoicing where a few dollars of gas are immaterial and the buyer's accounting team prefers the L1 settlement reference.
- Cross-platform compatibility when the customer's wallet hasn't added an L2 yet.
For everyday consumer checkouts, recurring billing, and retail flows, the L2s are the right default. The full mainnet picture is in Accept Ethereum mainnet payments with MixPay.
What changes for the merchant
Almost nothing. The merchant flow is identical regardless of which L2 the inbound payment used:
- Customer pays in ETH, USDC, USDT, or another supported token on whichever L2 their wallet is configured for.
- MixPay confirms the L2 transaction.
- Real-time price quote applies at the time of payment.
- Merchant credit lands in the chosen settlement asset (typically USDT or USDC).
- Reporting consolidates all four L2s plus Ethereum mainnet plus every other supported chain into one dashboard ledger.
Zero merchant fees at the MixPay layer. KYT compliance applies on every routed transaction. No node, no wallet, no per-L2 configuration.
For the broader stablecoin picture across these chains and beyond, see How to accept stablecoin payments — a 2026 merchant guide.
Choosing for your business
A pragmatic decision tree:
- U.S. consumer, retail, e-commerce → Base (primary), with Polygon PoS as low-gas backup.
- DeFi-adjacent, Web3-native → Arbitrum (primary), Optimism (secondary).
- Gaming, NFT, micro-payments → Polygon PoS (primary), Base (consumer-facing complement).
- B2B invoicing, high-value → Ethereum mainnet (primary), Arbitrum for L2-aware counterparties.
- Default for everyone else → accept all four. The marginal cost is zero, the customer picks, you settle in your stablecoin.
The full asset and chain matrix is on the accept page. Each network's chain-specific landing page (where one exists) covers wallet compatibility and confirmation-time detail.
FAQ
What is an Ethereum L2?
An Ethereum L2 (Layer 2) is a separate blockchain that batches transactions and settles them on Ethereum mainnet. The goal is to inherit Ethereum's security model while offering much lower per-transaction fees and faster confirmation. Arbitrum, Optimism, and Base are rollups (the most rigorous form of L2). Polygon PoS is often grouped with L2s in everyday usage but is technically a sidechain — different security trade-offs, similar economics for payments.
Which L2 should a merchant accept first?
If your customer base is U.S. consumer-leaning, start with Base — Coinbase's on-ramp makes the customer experience shortest there. If your customer base is DeFi-adjacent or has Ethereum-mainnet defaults, Arbitrum is the strongest first choice. If you need the cheapest possible gas at high volume, Polygon PoS wins. With a multi-chain processor like MixPay you don't have to pick — accepting all four costs nothing extra operationally.
How do L2 payments compare to Ethereum mainnet?
L2 payments cost a small fraction of mainnet gas (cents vs dollars) and confirm faster (seconds vs 12-15 seconds). They settle to Ethereum mainnet eventually, inheriting most of its security. The trade-off is that not every wallet supports every L2 by default — customers may need to switch network in their wallet. The MixPay quote engine surfaces both mainnet and L2 options at checkout so the customer picks whichever their wallet is configured for.
Which stablecoins work on Arbitrum, Optimism, Base, and Polygon?
USDC and USDT both deploy on all four. USDC is natively issued by Circle on Base, Polygon, Arbitrum, and Optimism (no bridge dependence). USDT is on Arbitrum, Optimism, and Polygon (also bridged via TRON-USDT for cross-chain treasury operations). USDT0 deploys on Polygon and Arbitrum specifically as a cross-chain stablecoin. MixPay routes all combinations.
Are Arbitrum, Optimism, and Base built on the same technology?
Optimism and Base are both built on the OP Stack — the same open-source rollup framework. Arbitrum uses Arbitrum's own Nitro stack. Functionally the three are very similar from a payment perspective: EVM-compatible, sub-second to a few-second confirmations, gas in cents. The differences that matter for merchants are ecosystem (Coinbase for Base) and developer mindshare (Arbitrum has the largest TVL of the three).
Is Polygon really an L2?
Polygon PoS is a sidechain, not a true L2 rollup — it has its own validator set and security model rather than inheriting Ethereum's. Polygon's zkEVM is a real L2. In merchant-payment conversations the term "L2" is often used loosely to mean "EVM-compatible Ethereum scaling solution", which Polygon PoS qualifies as. The economics are similar to true L2s; the security trade-off is real but rarely material for short-lived payment flows.
What's the gas cost of an L2 payment?
On Polygon PoS, gas is typically a fraction of a cent. On Base, Optimism, and Arbitrum it's typically under 10 cents at average usage levels, occasionally more during congestion. Compare to Ethereum mainnet at ~$1-$5 for a typical USDC transfer. For a merchant accepting payments, this gas is paid by the customer, not the merchant — but the lower it is, the more comfortable customers are paying.
Can I accept payments on all four L2s through one integration?
Yes. MixPay routes all four through a single dashboard and a single integration. The customer's wallet picks which L2 to use; the merchant settles in their chosen asset (typically a stablecoin) regardless of which L2 the inbound payment came from. There's no per-L2 configuration on the merchant side.
Does accepting L2 payments require running any infrastructure?
No. The merchant doesn't run a node, doesn't manage a wallet, and doesn't reconcile per-chain balances. MixPay handles the chain layer for all four L2s plus Ethereum mainnet. The merchant sees a unified ledger in their dashboard.