For partners
We'll build a module for your product
We cover development, documentation and support of the module. You provide API access, a sandbox and a short description of what it should do.
Who it's for
Who we work with
Payment providers
Payment acceptance, balance top-ups, support for refunds and recurring payments.
Domain registrars
Registration, renewal, transfer, NS and contact management — straight from the billing panel, no manual work.
Panel and service developers
Full service lifecycle (create, delete, suspend, resume), service state sync, editing, custom fields natively built into the billing interface.
Another service for hosting companies — antifraud, KYC, DDoS protection, mailings? Get in touch.
What it costs
Two models
A module in exchange for access
You provide API access and a sandbox, we build the module and publish it in the catalog. It costs you nothing.
- Development, documentation and support — on us
- The module is sold in the catalog to all clients, we set the price
- Minor updates — for example for a new API version — are free
When development is paid
Two cases: you want the module to be free for all catalog clients, or we declined to build it for free.
- The module is free for catalog clients — you pay for development
- We declined free development, but you still want the module
- Payment after delivery: first a working module, then the invoice
If the invoice isn't paid, the module is simply published in the catalog on the usual terms.
How it works
Four steps
- 1
Request
Briefly: what the product is, what the module should do, whether a sandbox exists.
- 2
Agree on scenarios
We fix the list of what the module does. That list is the scope — it doesn't grow along the way.
- 3
Access
API, sandbox, an account in your product. They stay with us for development, testing and fixes.
- 4
Build and publish
The module, a guide, a catalog listing. Usually up to 7 days, up to 30 for large ones.
What we need from you
- API documentation and access keys
- A sandbox where scenarios run without real money
- An account in your product for the duration of the work
- A short description of what the module should do
- A technical contact we can ask about the API
What we do
- A module for billmanager
- Installation and setup guide
- A catalog listing and publication
- Support of the module for clients
- Free minor updates, large ones on a paid basis
Terms
What to know upfront
Who owns the code?
We do. Neither the client who buys the module nor the partner whose product it integrates gets any rights to the module or its source code.
Is there exclusivity?
No. The module is available to every catalog user — that's the point: your product gets a channel to all hosting companies on billmanager.
What does free development include?
One module covering the list of scenarios agreed before the start. New scenarios and customisation for one of your clients are separate work.
How long does it take?
A small module usually up to 7 days, a large one up to 30. We name the exact date once we've looked at the API.
Who handles support?
The module is on us. Your service and API are on you. Minor updates, for example for a new API version, are free. Other updates aren't guaranteed, but you can sponsor one to raise its priority.
Can you decline?
Yes, without explanation. Usually the reason is simple: there's no sandbox, the API doesn't allow a decent integration, or billmanager itself has technical limits that make a proper module impossible.
Is this a public offer?
No. This page is an invitation to talk, not a public offer: terms for each project are agreed in writing.
Request
Tell us about the product
We'll reply by email. If we take it on, we'll send the list of what's needed to start right away.