Creating a payment adapter
As we progress toward a 1.0.0 release, developers should anticipate changes to FOSSBilling that necessitate attention before custom modules and integrations regain full functionality.
These modifications will be confined to the 0.x releases and will be outlined in the 'breaking changes' section of the release notes. We are working to add these items to our roadmap to enhance visibility for external developers.
These pre-v1 releases are providing us the opportunity to update obsolete systems and replace cumbersome implementations inherited from the BoxBilling project so we appreciate the patience of external developers.
This guide is incomplete. Please help us complete it using the "Edit this page" button in the sidebar. Thanks! If you're looking to create your own extension, this documentation will tell you the bare minimum required, but looking at existing extensions will probably be necessary to get a complete idea on how to write one.
All payment adapters should reside under the /library/Payment/Adapter folder. They should all extend the Payment_AdapterAbstract class and implement it's functions.
The Payment_AdapterAbstract class has inline documentation of each function to aid in the development of payment adapters. You can find the most up-to-date version of this here (opens in a new tab)