This is an automated archive made by the Lemmit Bot.
The original was posted on /r/opensource by /u/UnitedLink3908 on 2025-06-05 09:21:18+00:00.
Hey r/opensource!
I got tired of “open core” payment APIs with paywalls and SaaS lock-in. So I spent the last few months building FlossPay: A payments backend inspired by Linux governance and Oracle-style auditability — but 100% FLOSS, MIT License, no strings attached.
Modular, async-first (Redis streams), PCI-ready, full audit trail.
UPI today, but the stack is rails-agnostic: cards, wallets, crypto, all coming up.
Features: Idempotency, HMAC SHA256, retries, DLQ, immutable logging, API-first, and all docs/Wiki public.
Designed for MSMEs, indie merchants, startups—skip $30K+ in infra costs, deploy yourself, own your stack.
Would love feedback, PRs, or stories from the trenches. What’s the most painful “black-box” API you’ve had to integrate?
Don’t forget to star my repo: github.com/gracemann365/FlossPay