Show HN: We built an open source, zero webhooks payment processor

‘Zero webhooks’ money tool drops; devs holler ‘It’s just Stripe on training wheels’

TLDR: Flowglad promises open‑source billing without webhooks, but it still relies on Stripe for actual payments. Commenters debated whether webhooks are the real pain, questioned how charges happen, and balked at standard 2.9% + 30¢ fees—useful simplification, not a Stripe killer.

Flowglad hit Hacker News promising “zero webhooks” and a sane way to handle pricing and feature access, and the crowd instantly split into two camps: the “finally, fewer moving parts” fans and the “marketing hype, where’s the card processor?” skeptics. The pitch: one place to read a customer’s billing state, no messy event listeners, and real‑time feature gating. Translation for non‑devs: fewer brittle “did we get the billing email?” moments. But the comments lit up. clintonb side‑eyed the scare‑stats—“250+ Stripe events”—with a cool “you don’t need them all,” while aftbit asked the big question: does Flowglad actually charge cards, or do you still need Stripe or Braintree? Cue koakuma‑chan reminding everyone the real boss level is Visa/Mastercard rules, not webhook spam. Then baobabKoodaa dropped the hammer: it’s not a Stripe replacement, it’s an abstraction layer on top. The pricing line “2.9% + 30¢” sparked immediate wallet panic; swedishuser called it “Very expensive!” and the thread turned into a group therapy session about fees. Meanwhile, fans cheered the “use your own IDs” and quick Next.js/React setup, joking that Flowglad is “couples therapy for devs and billing.” Memes flew: “zero webhooks = zero headaches,” retorted by “zero webhooks = zero actual payments?” Classic HN energy—optimism vs reality check, with a side of fee rage.

Key Points

  • Flowglad offers a stateless, “zero webhooks” billing architecture with a single source of truth for pricing, features, and usage meters.
  • Developers can iterate on pricing models in test mode and deploy changes to production without redeploying application code.
  • The platform uses application-defined user or organization IDs, avoiding separate customer ID management.
  • A full‑stack SDK is provided, including server access (getBilling) and a React hook (useBilling) for real-time billing state in the frontend.
  • Integration steps include installing packages, configuring a Flowglad server client, exposing an API route, and wrapping the app with FlowgladProvider.

Hottest takes

"You don’t need to listen for all event types" — clintonb
"How does the actual payment processing work?" — aftbit
"Very expensive!" — swedishuser
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.