Home - gracemann365/FlossPay GitHub Wiki

🏦 Welcome to the FlossPay Wiki!

FlossPay isn’t just code—it’s a kernel-inspired, enterprise-grade payments aggregator infrastructure.
Built for total transparency, auditability, and contributor empowerment.

🚦 Project Roadmap & Maturity

FlossPay is being built in public, phase by phase, following a rigorous roadmap.

  • Current status: Foundation (UPI rail, core infra, audit, modularity)
  • Upcoming: More payment rails, full test/ops/CI/CD, SRE/observability, and cloud-grade production features.

Want details on what’s shipped and what’s planned? 👉 See the full Roadmap & Phases

Note: All advanced features are transparently roadmapped, not hidden or exaggerated. Community feedback and PRs always welcome!

What makes FlossPay different?

FlossPay gives indie merchants and MSMEs the core of a $ 30,000+ enterprise payments backend—completely free, open, and auditable. Avoid SaaS lock-in, build custom rails, pass audits, and launch with confidence. UPI today, cards/wallets/crypto tomorrow—on your terms, not your vendor’s.

🚀 Why FlossPay?

One modular stack, all rails—no vendor lock-in.

FlossPay gives indie merchants and MSMEs the core of a $30,000+ enterprise payments backend—completely free, open, and auditable. Avoid SaaS lock-in, build custom rails, pass audits, and launch with confidence. UPI today, cards/wallets/crypto tomorrow—on your terms, not your vendor’s.

What makes FlossPay different?

  • Bank-grade resilience: Async-first, immutable ledger, fully auditable, Linux-inspired governance
  • Open for all: Indie merchants, MSMEs, SaaS, and devs—no lock-in, no black-boxes, 100% FLOSS
  • Security as default: PCI-DSS, ISO 27001, SOC2 mapped—compliance isn’t optional, it’s built-in
  • Pluggable Rails: Start with UPI, expand to Cards, Wallets, Net-Banking, and even Crypto (see roadmap)
  • Contributor-driven: Peer review, transparent standards, and a living, community-first wiki

🛤️ Supported & Planned Payment Rails

Current:

  • UPI Rail: Fully hardened, tested, and audit-ready

Coming Soon:

  • Card Rail: (Visa, Mastercard, RuPay; credit & debit)
  • Wallet Rail: (Paytm, AmazonPay, PhonePe, etc.)
  • Net-Banking Rail: (IMPS, NEFT, RTGS support)
  • Crypto Rail: (plug-in module for on-chain payments)
  • BNPL / PayLater Rail
  • Custom rails: Easily add your own microservice connector

All new rails are implemented as modular, plug-and-play services.
No vendor lock-in. No need to rewrite the core stack.

🏗️ What You’ll Find Here

  • Deep dives on architecture, design choices, and SRE ops
  • API docs, security/compliance guides, and real-world deployment patterns
  • Community and contributor handbook, roadmap, RFCs, and advanced troubleshooting

📢 Who Should Use FlossPay?

  • Indie merchants & MSMEs who want control over payments infrastructure
  • Startups & SaaS founders building custom payment flows or launching in new geos
  • Open-source enthusiasts and fintech hackers
  • Anyone tired of black-box payment APIs and high SaaS fees

📚 Wiki Index

This wiki is always evolving. PRs, edits, and new pages welcome!
FlossPay: UPI today, Cards/Wallets/Crypto tomorrow—always open, always yours.