-
-
Notifications
You must be signed in to change notification settings - Fork 6
Home
FlossPay is a kernel-inspired, enterprise-grade Free/Libre Open Source Payments Aggregator built for maximum auditability, transparency, and reliability. This wiki serves as the living knowledge base for FlossPay’s design, operation, security, and contributor onboarding.
- Project Overview
- Solution Architecture
- API Reference
- Deployment & Ops
- Security & Compliance
- Contributor Guide
- Governance & Process
- FAQ & Troubleshooting
- Roadmap & RFCs
FlossPay brings Linux governance and Oracle Financials discipline to payments infrastructure:
- Strict peer review & meritocratic maintainers
- Immutable audit trails, idempotency, and forensic logging
- Modular, plug-and-play “rails” for UPI, cards, wallets, and more
- Full compliance mapping (PCI-DSS, SOC2, ISO 27001)
- Detailed diagrams and sequence flows (add links to subpages as you create them)
- API-first, microservice modularity, Redis async, Postgres ledger
- Full OpenAPI spec (add or link the spec file here)
- Auth, idempotency, audit events, error handling, versioning
- Quickstart for local dev, cloud-ready guides (Kubernetes, Helm, Terraform)
- Observability: Prometheus, Grafana dashboards, SLOs
- HMAC, mTLS, audit partitioning, encrypted credentials
- Threat model, pen-test notes, compliance coverage
- Branching, PR process, code style (Java 21/Spring Boot idioms)
- Review gates, staging/production workflows
- Issue templates, discussions, RFCs
- Code of Conduct, Maintainer list, escalation paths
- Release process, long-term support, security policy
- Common setup/usage errors, debug recipes, platform-specific notes
- Milestones, proposals, and feature requests
- How to contribute to direction and planning
Want to contribute?
Start at Contributor Guide or join Discussions.
PRs, edits, and new pages are welcome—help us make FLOSS payments infra even stronger!
FlossPay is MIT Licensed.
© 2024-25 David Grace & FlossPay Contributors.
For sponsorship, collaboration, or professional engagement:
Open an Issue or Discussion with your context and intent.
This documentation follows Linux Foundation and CNCF governance models.
All feedback is welcome!
- 🏠 Home
- 🛣️ Roadmap Of Upcoming Phases
- 📡 API Reference & Usage
- 🏗️ Architecture Deep Dive
- 🚀 Deployment & Operations
- 🔒 Security Audit & Compliance
- 🤝 Contributor Guide
- 🏛️ Governance & Maintainers
- 🛣️ Roadmap & RFCs
- 🌍 Vision & Philosophy
- ❓ FAQ & Troubleshooting
Project Links
This documentation is a living resource. PRs, edits, and contributions are welcome!