What are micropayments?

Payments small enough that traditional payment infrastructure cannot process them economically. Typically defined as transactions under a dollar (with the threshold rising over time). Use cases include per-article content access, per-search-query payments, per-email cover charges, and other granular paid interactions where a recurring subscription does not fit.

Why did micropayments fail for thirty years?

Two structural reasons. First, traditional payment processing fees (15-30 cents minimum per transaction) made small payments unprofitable. Second, user-experience friction (entering payment details for every transaction) made the use case impractical. Both barriers are structural to traditional payment infrastructure.

What changed in 2024+?

The Lightning Network reached production-grade reliability with sub-cent fees per payment. Cashu added bearer-token semantics on top of Lightning. The combination produces payment infrastructure where four-cent transactions are economically viable and the user-experience friction is reduced enough to support real use cases.

Are micropayments solved now?

The technical primitives work. Adoption is the variable. Lightning and Cashu provide the infrastructure; building applications that use them appropriately is ongoing. The pattern of new infrastructure followed by gradual application development matches how other internet primitives evolved.

What does Rythm have to do with micropayment history?

Rythm is one application of the new micropayment infrastructure. Cover charge filtering for email is a use case that earlier micropayment attempts (Hashcash, Microsoft Passport, Beenz) tried and failed to make work. The Lightning + Cashu combination makes it economically viable in 2026.

History of Micropayments on the Internet (1995-2026)

Micropayments have failed for thirty years until they suddenly worked. Here is the history, why earlier attempts failed, and what changed.

Micropayments on the internet have a thirty-year history of credible attempts that all failed. Each generation built on the last; each generation hit the same structural barriers. In 2024+, something changed: the Lightning Network plus Cashu produced infrastructure where micropayments actually work. This post is about why earlier attempts failed, what changed, and what the trajectory looks like now that the primitives function.

The 1990s: First Wave

The original micropayment dreams.

1995-2000: DigiCash. David Chaum’s pioneering ecash system. Cryptographic blinded signatures. Bearer-instrument tokens. Privacy-preserving by design. Filed for bankruptcy in 1998. Failed because the underlying banking infrastructure did not adopt the system at the scale needed.

1996-1998: CyberCash. Specialized in small online payments. Could not get fees low enough to make sub-dollar payments viable. Acquired in 2001; went out of business.

1996-2002: Millicent. Compaq’s micropayment system. Used “scrip” tokens denominated in fractions of cents. Closed in 2002 due to lack of adoption.

1998-2001: Beenz. “The Web’s currency.” Earned through online activity, redeemable with merchants. Reached 80+ countries before collapsing in 2001.

1999-2002: Microsoft Passport. Identity infrastructure that included micropayment capability. Discontinued for micropayment use.

The 1990s wave failed because of structural mismatch with existing payment rails. Banks did not support sub-dollar transactions efficiently. Credit card processors charged minimums that destroyed micropayment economics. The technical infrastructure existed; the financial infrastructure did not.

The Early 2000s: PayPal Era

The pivot to “small but not micro.”

2000+: PayPal. Solved person-to-person payments. The minimum economic transaction was around $1; below that, fees ate the value. Not a micropayment system, but a related success.

2002: Hashcash. Adam Back’s proof-of-work system. Senders had to compute a small hash to send mail. Adopted by some anti-spam systems. Failed as a general micropayment system because PoW was not transferable as value.

2002+: Per-article paywall experiments. WSJ, FT, NYT all experimented with paywalls. Most settled on subscriptions rather than micropayments because the per-article transaction infrastructure was missing.

Mid-2000s: M-Pesa. Mobile-money in Kenya. Solved micropayments in a specific economic context (mobile-first, cash-friendly economy). Did not scale to general internet micropayments.

2003-2007: Various ad-revenue-sharing models. Bloggers and small publishers experimented with revenue-sharing platforms (Helium, Squidoo). Not technically micropayments but solving the “how to pay creators” problem.

The early 2000s wave learned that traditional payment rails could not support micropayments and worked around the limitation. The use cases shifted to subscriptions, ad revenue, or P2P payments above a dollar threshold. True micropayments remained unsolved.

The Mid-2000s to Mid-2010s: Quiet Years

Micropayments largely abandoned as a technical pursuit.

Subscription dominance. Spotify, Netflix, SaaS companies built business models on monthly recurring revenue. Micropayments were structurally inferior for most use cases.

Ad-supported content. YouTube, Facebook, Google search all built on advertising rather than micropayments.

App stores added their own friction. iTunes and Google Play set effective minimums; below those, transactions were uneconomical.

Bitcoin exists but is slow and expensive at the protocol level. Satoshi’s original BTC supports payments but on-chain fees made micropayments impractical at higher network demand.

Researchers continued working on payment channels. Theoretical work on what would later become Lightning. Not yet production-grade.

The era was characterized by “micropayments are not solved, and other models work, so we work with the other models.”

The Mid-2010s: Lightning Emergence

The technical breakthrough.

2015: Joseph Poon and Thaddeus Dryja publish the Lightning paper. Layer-2 payment channels that could support sub-cent transactions on top of Bitcoin.

2016-2018: Lightning Network development. Multiple implementations (LND, c-lightning, Eclair). Test networks. Mainnet rollout in late 2017.

2018-2020: Lightning grows. Capacity scales. Routing improves. Wallet UX matures. Use cases include in-person payments, content tipping, and cross-border remittance.

2018: Streaming sats / Podcasting 2.0. Listeners stream sats per second to podcast hosts. Real-world use of micropayments at scale.

2020-2022: Wallet UX improvements. Wallet of Satoshi, Phoenix, and others bring Lightning to consumer-friendly form.

The Lightning emergence solved the technical problem of how to send sub-cent payments efficiently. The user-experience problem was being addressed in parallel.

The Cashu Layer (2023-2025)

The bearer-instrument addition.

2023: Cashu protocol publication. David Wagner publishes the first version of the Cashu protocol. Bearer-instrument tokens on top of Lightning.

2023-2024: Mint implementations. Multiple Cashu mints come online. Wallet implementations follow.

2024+: Production deployment. Mints stabilize. Wallets become user-friendly. Real applications start using Cashu.

2024+: First applications. Pay-per-action use cases. Tipping. Content access. Email cover charges (Rythm).

The Cashu layer added the bearer-instrument property that pure Lightning lacks. A bearer token can be embedded in an email; pure Lightning requires both parties to coordinate per-payment.

We covered the protocol at the cashu protocol explained for email use cases and the bearer-instrument argument at why bearer tokens are the right primitive for email payments.

What Changed

The structural shifts.

Cost per payment dropped. Lightning routing fees are typically 0.01-0.1% of the payment amount. For a four-cent payment, that is 0.0004-0.004 cents. Below the level that breaks any practical use case.

Settlement is fast. Lightning payments settle in seconds. The user-experience friction of waiting for confirmation is eliminated.

Bearer-instrument property added. Cashu adds the property that pure Lightning lacks: tokens that can be transmitted independently of the underlying payment infrastructure.

Wallet UX matured. Modern Lightning wallets handle most operational complexity transparently. Users can receive payments without managing channels manually.

Privacy-preserving by design. Cashu’s blinded signatures hide the link between issuance and redemption. Better than Lightning alone in some privacy dimensions.

The combination is that the structural barriers that defeated 1990s and 2000s micropayments are gone. The infrastructure works.

What Has Not Changed

The honest limits.

Adoption is still building. The technical primitives work; building applications that use them appropriately is ongoing. Most internet users have not encountered Lightning or Cashu in 2026.

User-experience for non-technical users. Onboarding to a Lightning wallet still requires more friction than a credit card. Custodial wallets reduce friction at the cost of custody.

Integration with existing payment infrastructure. Bridging between fiat and Lightning is friction-prone. Strike and similar services help but the bridge is still a friction point.

Regulatory uncertainty. Various jurisdictions have evolving views on Cashu, Lightning, and similar technologies. The regulatory landscape is not fully clear.

Application development is incremental. Each use case requires its own application. Email cover charges (Rythm) is one. Streaming sats for podcasts is another. There are not yet thousands of applications using the primitives.

The trajectory matches how other internet primitives evolved. SMTP existed for years before email became universal. HTTP existed for years before the web took off. The infrastructure-first, applications-after pattern is normal.

Where Rythm Fits

The role.

Rythm is one application of the new micropayment infrastructure. Cover charge filtering for email. Uses Cashu bearer tokens delivered in email bodies, melted through Lightning to the recipient’s wallet.

Validates the use case earlier attempts could not. Hashcash tried email cover charges with PoW and failed. Microsoft Passport tried with custodial infrastructure and failed. Various credit-card-based attempts failed because of fee minimums. Lightning + Cashu makes the use case economically viable.

Builds on the work of the underlying infrastructure. Rythm does not invent Lightning or Cashu; it uses them. The application benefits from the infrastructure work done elsewhere.

Is one of many applications to come. As the infrastructure matures, more applications will appear. Email cover charges is one; pay-per-API-call is another; pay-per-content-access is another; many more are possible.

A Specific Honest Note

Micropayments failed for thirty years and now work. The change is structural: Lightning solved the cost-per-payment and speed problems; Cashu added the bearer-instrument property; wallet UX matured to consumer-grade. The applications are starting to appear.

Rythm is one application. The use case (email cover charges) was attempted multiple times in the past and failed. With the new infrastructure, the use case is economically viable. The same infrastructure will support many other applications as they are built.

The History of Micropayments on the Internet (1995-2026)