The FOSSBilling Forum
I want to build a quantum Payment Gateway how can I contribute - Printable Version

+- The FOSSBilling Forum (https://forum.fossbilling.org)
+-- Forum: Development (https://forum.fossbilling.org/forum-11.html)
+--- Forum: Development - General (https://forum.fossbilling.org/forum-12.html)
+--- Thread: I want to build a quantum Payment Gateway how can I contribute (/thread-522.html)

I want to build a quantum Payment Gateway how can I contribute - DocBlah - 11-28-2025

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
  1. 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.)
  2. Are there any breaking changes planned for the payment API between 0.7.x → 0.8.x that I should prepare for?
  3. Should I submit this as a separate GitHub repo first, or directly as a PR to the main
    Code:

    FOSSBilling/FOSSBilling
    repository?
    (I want to follow the contributors’ workflow correctly.)
  4. Is there a preferred naming convention?
    e.g.
    Code:

    QuantumGateway
    ,
    Code:

    Quantum
    ,
    Code:

    Quantum_Vault
    , etc.
  5. 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!