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 — the issuing bank, the card network, the payment processor — and each takes a cut. Combined interchange fees typically range from 1.5% to 3.5% per transaction, plus a flat per-transaction charge.
For a £2 purchase, that fee structure can consume more than half the transaction value. It's why merchants are legally permitted to set credit card minimums of up to $10 — small card transactions can actively cost them money.
For a merchant selling a £1.50 item, a single card transaction can wipe out the entire margin. The economics of small payments have never worked within the existing infrastructure.
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 an afterthought — and the system was never updated to handle it.
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 impossibility 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. Each of these models is a workaround, arrived at by necessity.
The internet didn't choose advertising as its primary business model because it was ideal. It chose it because micropayments were impossible.
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. The economics never matched the actual shape of digital consumption.
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 intermediaries, no permission required, no minimum transaction size imposed by infrastructure.
That was a real opening. But Bitcoin itself was built for settlement, and it shows. 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 — Bitcoin was neither.
Other blockchain networks followed, but most were built around a different goal entirely — programmable smart contracts, decentralised applications, token ecosystems. General-purpose computation platforms. The specific demands of payment infrastructure — low fees, fast settlement, high volume, predictable costs — were never the primary design objective.
Blockchain opened the door. But nobody built the payment layer that should have walked through it.
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 enough and predictable enough so that sub-penny transactions make economic sense. Throughput needs to handle volume at scale: potentially millions of transactions per hour across a global network. Settlement needs to be fast and deterministic. And the fee structure needs to adapt to demand, so that busy periods don't suddenly price out the use cases the infrastructure is supposed 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. And the validator set needs to stay accessible without expensive hardware requirements that gradually concentrate control in a small number of operators.
How eCurrency is built for this
eCurrency was designed as a 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 — which suits parallel processing and deterministic validation. In account-based systems, every transaction updates the shared global state in sequence. UTXO outputs are independent and can be validated simultaneously, which allows the system to scale with demand rather than slow down under it.
Blocks are produced every ten seconds and can hold up to 65,535 transactions at 8MB — a theoretical throughput approaching 400,000 transactions per minute. The ceiling matters less than the fee structure that governs how that capacity is used.
eCurrency's adaptive fee mechanism means fees rise proportionally with sudden demand spikes and fall during quieter periods — making spam economically prohibitive and routine micropayments consistently cheap.
All transaction fees go into a global reward fund. Each validated block releases a fixed proportion of that fund (1/500), giving validators a smoothed, predictable income that doesn't depend on the timing or size of individual blocks. This removes the incentive to manipulate transaction ordering for short-term gain.
Staking works without lockups. Validators participate using the ECRs 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 custodial services. 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. The architecture is built to evolve — new algorithms can be introduced via soft fork without disrupting existing addresses or requiring a chain migration.
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 fundamentally 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 but economically unworkable within existing payment infrastructure. That changes when the per-transaction cost approaches a fraction of a cent.
The most interesting business models of the next decade may not be ones we've already imagined. They're the ones that couldn't exist until the payment layer was ready.
Infrastructure shapes what gets built
The global digital payments market is projected to reach over $361 billion by 2030, growing at an annual rate of over 21%. The majority 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 the infrastructure 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.
Whether micropayments finally work is a solved technical problem. The cryptographic primitives exist. The consensus mechanisms exist. The throughput is achievable. What's been missing is a network with the right combination of properties, built with payments as the primary goal.
That network now exists.
