Stripe vs L402: Why Micropayments Need a New Payment Rail
The $0.50 problem
Stripe's US rate is $0.30 + 2.9% per transaction. A $0.50 charge costs $0.31 in fees. That's 62% gone, and anything under $0.50 isn't economically viable.
Other markets and processors shift the numbers (Stripe EU is around €0.25 + 1.5% for EEA cards, Stripe AU runs $0.30 + 1.75%, Adyen and Square are similar shape). The structure stays the same: a fixed cost per transaction kills the economics of small payments. The math runs the same way for PayPal, Razorpay, Worldpay, and every other card-based processor.
This matters because a huge category of API queries are worth less than $0.50:
- A weather lookup: $0.01
- A geocoding query: $0.005
- An exchange rate check: $0.001
- A single AI inference call: $0.02
These are the most common API calls in the world, and traditional payment processors make them impossible to monetize individually.
How L402 changes the economics
Lightning Network transactions have fees measured in fractions of a cent. A 10-sat payment (~$0.007) costs roughly 0.1 sats in routing fees, about a 1% fee rate regardless of the amount.
This means you can charge per query at any price point. The economics work at $0.001 just as well as at $100.
The comparison
| Aspect | Stripe / Traditional | L402 + Lightning |
|---|---|---|
| Minimum viable transaction | ~$0.50 | 1 sat (~$0.001) |
| Fee on $0.01 transaction | Not possible | ~1% |
| Fee on $1.00 transaction | ~33% | ~1% |
| Settlement | 2-7 business days | Instant |
| Account required | Yes (both sides) | No |
| KYC required | Yes | No |
| AI agent compatible | Requires manual setup | Native support |
| Geographic restrictions | Yes | No |
| Chargeback risk | Yes | No (settled instantly) |
| Custody model | Custodial | Non-custodial |
Beyond fees: the agent compatibility problem
Even if card processors dropped their fees to zero, they still wouldn't work for AI agents. Every card-based processor requires:
- An account for the buyer
- A credit card or bank account on file
- Often, identity verification
An autonomous AI agent can't complete those steps. L402 requires none of them. The Lightning payment itself is the authentication.
When to use what
Use a card processor when:
- Transactions are > $5
- You need subscriptions with complex billing logic
- Your customers are humans with credit cards
- You need chargeback protection
- You're in a regulated industry requiring KYC
Use L402 when:
- You want per-query pricing at any price point
- Your clients include AI agents or automated systems
- You want instant, non-custodial settlement
- You don't want to manage user accounts
- Privacy matters to your customers
They're complementary
L402 doesn't replace card processors for all use cases. It fills the gap they structurally can't: sub-dollar, instant, anonymous, machine-to-machine payments.
bolthub makes it easy to add L402 to any API. Start your free trial.
*Card processor pricing sourced from publicly available information as of 2026.*