i everyone,
I’d like to contribute a new payment gateway adapter for Quantum Gateway / Quantum Vault to FOSSBilling.
Quantum Gateway provides credit-card processing, a hosted payment form, recurring billing, and vault/token storage. Since many merchants still use Quantum, I believe an official FOSSBilling adapter would be valuable for the community.
Before I start coding, I’d appreciate some guidance to make sure the module follows project standards and works smoothly with future updates.
What I’m planning to build
- A full payment adapter under
Code:
/library/Payment/Adapter/QuantumGateway
- Hosted/redirect payment form
- Callback/IPN support
- Optional MD5/HMAC verification
- Support for Quantum Vault (token storage) if possible
- Test mode support
- Clean, documented PHP code following FOSSBilling’s adapter structure
What I need help with
- Is there an up-to-date example gateway adapter the team recommends using as a reference?
(I see Stripe/PayPal modules, but want to confirm which one best reflects the current coding standards.)
- Are there any breaking changes planned for the payment API between 0.7.x → 0.8.x that I should prepare for?
- Should I submit this as a separate GitHub repo first, or directly as a PR to the main
Code:
FOSSBilling/FOSSBilling
(I want to follow the contributors’ workflow correctly.)
- Is there a preferred naming convention?
e.g.
,
,
, etc.
- Would the team accept a new gateway adapter into the core project, or should it remain an optional community extension?
What I already have
I’ve already created a working skeleton adapter with form POST, callback handling, and configuration fields. Before finalizing it, I want to ensure it aligns with FOSSBilling’s guidelines.
Goal
I want to maintain this adapter long-term and keep it compatible with new FOSSBilling versions. Any advice, references, or best practices from the team would be extremely helpful.
Thanks in advance — excited to contribute to the project and give something useful back to the community!