How do I pay the publisher of a web page?

Original Article ↗ Hacker News Discussion ↗

Efforts to let readers easily tip or pay the publishers of individual web pages run into both technical and behavioral hurdles. Commenters explore ideas like HTML metadata, browser-level pay buttons, QR or SEPA transfers, and various crypto and Lightning schemes, but note problems with fees, regulation, fraud risk, fragmented standards, and the fact that most users won’t voluntarily pay after consuming free content. Many conclude that, for now, advertising and platform-based subscriptions remain dominant, and that any viable micropayment system would need deep integration with existing financial infrastructure and browsers, plus strong incentives for both creators and users to adopt it.

Existing Ways to Pay Today

  • Many argue the web already supports payment: explicit “donate”/“support”/Patreon/Ko‑fi/PayPal links, merch stores, recurring subscriptions.
  • View: if a site doesn’t clearly expose a payment option, it should be treated as intentionally free.
  • Counterpoint: what’s missing is a standard, machine-readable way to express preferred payment methods so tools/browsers can automate discovery.

Standardized Metadata vs. Just Links

  • Proposal: HTML meta or <link> tags (or humans.txt) declaring how to pay a site.
  • Supporters: would enable a browser button/extension to tip without hunting around the page.
  • Skeptics: plain text + hyperlinks already solve this; meta tags add complexity and could be abused (e.g., hosting platform claiming tips).

Micropayments & Economics

  • Core issue: fees and infrastructure make true micropayments (e.g., a few cents per article) uneconomical; intermediaries may capture a large share.
  • Some suggest stored internal balances to aggregate many tiny transfers and settle infrequently.
  • Others note platforms that “solved” this (Twitch, Patreon, app stores, OnlyFans, etc.) do so via hefty cuts and closed ecosystems.

Crypto, Lightning, and Alternative Rails

  • Some see crypto (especially Lightning or stablecoins) as ideal for tiny, global, low‑fee payments, with examples of working systems and anecdotal success.
  • Critics say crypto is fragmented, volatile, fee‑ridden, scam‑prone, and still needs fiat on/off‑ramps; many people just want normal cash.
  • Debate over Brave: supporters view it as turning adblock users into revenue sources; detractors call it an ad middleman/racket.
  • General tension: censorship‑resistant, anonymous payments vs. regulatory KYC/AML requirements.

Browser / Payment Layer Proposals

  • Ideas: browser-native “tip/pay” button, with vendors aggregating payments and taking a small commission.
  • Concerns: browsers lack global payment infra, could become gatekeepers, and face conflicts of interest (especially ad or app‑store businesses).
  • Past efforts like Web Monetization API cited as having low demand and deployment friction.

User Behavior & Incentives

  • Many believe voluntary post‑hoc tipping is rare; most users won’t pay for content they’ve already consumed.
  • Others counter that a subset will tip if friction is very low.
  • Some argue recurring support models plus exclusive content align incentives better than one‑off tips.