Why Micropayments Never Worked on the Internet. Until Now

April 27, 2026
Why Micropayments Never Worked on the Internet. Until Now

The idea has been around almost as long as the web itself. If people could pay tiny amounts online (a few pence to read an article, a fraction of a cent per API call, a per-second fee for a stream) entirely new kinds of digital businesses would become possible. Pay for what you use, nothing more.

The fee problem that killed small payments

Traditional payment networks were designed around a different assumption: that transactions would be large enough to absorb processing costs. Every card payment passes through multiple intermediaries, including the issuing bank, the card network, and the payment processor, and each takes a cut. Interchange fees typically run 1% to 3% per transaction, often with a minimum flat fee on top.

For a small purchase, that flat minimum can matter more than the percentage. Merchants are legally permitted to set credit card minimums of up to $10, because small card transactions can cost them money to process. On very low-margin items, fees can run to 40% or more of the sale price.

This is a structural property of how payment infrastructure was built. It was designed for high-value, relatively infrequent transactions. The granular, continuous value exchange the internet economy needs was never the target use case.

What the internet built instead

Because micropayments weren't viable, the internet organised itself around a handful of monetisation models that could work within existing payment constraints.

Advertising became the default business model for free content: attention sold in bulk to offset the difficulty of charging per view. Subscriptions bundled access to reduce transaction frequency. Large one-time purchases replaced the small continuous ones that would have been more natural.

Advertising, subscriptions, and one-time purchases became the default because micropayments were impossible within the infrastructure available.

The consequences are visible everywhere. Content platforms optimise for engagement over quality because attention, not value, is what gets monetised. Paywalls force an all-or-nothing choice on readers who might happily pay a few pence for a single article. Independent creators struggle to monetise small audiences.

Bitcoin changed the situation without the payment layer

When Bitcoin launched in 2009, it demonstrated something genuinely new: digital value could transfer directly between parties, with no banks or payment processors involved in settlement, no permission required, and no minimum transaction size imposed by infrastructure.

That was a real opening. Bitcoin itself was built for settlement: block confirmation times, variable fees, and throughput constraints made it unsuitable for fast, cheap, continuous transactions. Micropayments need something closer to instant and essentially free.

Other blockchain networks followed, most built around a different goal: programmable smart contracts, decentralised applications, token ecosystems, general-purpose computation. Low fees, fast settlement, high volume, and predictable costs were never the primary design objective for these platforms.

Blockchain proved the underlying capability. A payment layer built specifically for it still needed to be built.

What purpose-built payment infrastructure requires

The requirements for functional micropayment infrastructure are specific, and most existing networks fail to meet all of them at once.

Fees need to be low and predictable enough that sub-penny transactions make economic sense. Throughput needs to handle volume at scale, potentially millions of transactions per hour across a global network, with settlement fast and deterministic enough that busy periods don't price out the use cases the infrastructure exists to enable.

There are longer-horizon requirements too, which most payment infrastructure simply ignores. Security needs to hold over decades: a network handling value in 2025 should still be cryptographically sound in 2040, which means anticipating quantum computing while it's still on the horizon. The validator set needs to stay accessible too, without expensive hardware requirements that gradually concentrate control in a small number of operators.

How eCurrency is built for this

eCurrency was designed as payment infrastructure from the start. The architectural choices reflect that directly.

The network uses a UTXO-based transaction model, the same foundational approach as Bitcoin. The UTXO model enables atomic value movement without account-style global state, and transaction fees are deterministic and independent of execution outcomes. That keeps the system predictable as demand grows.

Blocks are produced every ten seconds, keeping settlement fast and predictable.

Validators earn a direct share of each block's transaction fees, plus a subsidy from the network's Reward Fund. This combination smooths validator income across periods of low fee activity while keeping compensation tied to actual usage.

Staking works without lockups. Validators participate using the ECR they hold, without freezing capital or waiting in withdrawal queues. This keeps the network accessible to smaller validators and avoids the centralisation pressure that comes when staking requires committing funds to a custodial service. The protocol design behind these properties is covered in detail in our overview of eCurrency as an internet payment layer.

On the cryptographic side, eCurrency has native support for Falcon, the lattice-based digital signature scheme selected by NIST for post-quantum standardisation.

What becomes possible

When payment infrastructure stops imposing a floor on transaction size, previously unworkable business models become practical.

Publishers can charge per article. A reader who wants to follow a specific writer, or read a single piece of investigative journalism, pays for exactly that. A monthly bundle that includes content they'll never read is no longer the only option. The economics of independent publishing shift when the per-transaction cost approaches zero.

Streaming services can charge per second of consumption. API providers can price per call. Creators can receive direct payments from audiences for individual posts, videos, or contributions, without platforms taking a significant cut from every small transaction to cover their own processing costs.

Machine-to-machine payments become viable at scale: a connected device paying for network access, an autonomous service compensating a compute provider, distributed systems settling for data in real time. These interaction patterns are technically possible today; what's kept them economically unworkable is a per-transaction cost that doesn't approach a fraction of a cent.

Infrastructure shapes what gets built

The digital payment market was valued at $137.0 billion in 2025 and is projected to reach $682.8 billion by 2033, growing at a compound annual rate of 22.5%, according to Grand View Research. Most of that growth is in payments that look like the ones we already have: card transactions, digital wallets, mobile POS. The granular, programmable, machine-native payment economy is still waiting for infrastructure built to support it.

eCurrency is built to be that infrastructure: a payment layer designed from the ground up to do what payment layers need to do.

The cryptographic primitives exist. The consensus mechanism is live. What's been missing is a network built with payments as the primary goal from day one.

Share