interfasys

I don't mind paying extra as long as the PM module can populate the services section in the shopping area so that customers can purchase support at the same time they purchase a plan of some sort.

Any ETA for 3.1? Wondering what the release cycle is. Monthly? Quarterly? Yearly? :S

We don't have any use for any of these, but I like the fact that some devs want to hear from users. I second the request for OVH domains though and there is a request for it in the FR forum.

Links provided don't work. +1 for this request.

This would be ideal for support and development. As a service provider, I'd like to be able to sell support packages A package can be, for example, for 3 hours of hosting support. A customer raises a ticket for support and if they have bought the package, we can start on it right away, otherwise, we send a link to buy a package. An in-app timer could be useful. We start it once we confirm to the customer that we'll be working on it right away and we'll stop it when we're done, giving us an indication on how much time it took us to perform the task. Once work on the ticket has been completed, we can remove an amount of time from the package, in 15 minutes increment per example. The customer knows at all times how many hours/minutes are left.

OVH is a very good provider of cctlds with attractive prices and they support DNSSEC http://www.ovh.com/fr/domaines/ They now offer a RESTful API https://api.ovh.com/console/#/domains NETIM is another one to consider http://www.netim.com/domain/prices.php (public prices) Their API http://support.netim.com/en/wiki/Category:Functions They already have an open source module for the most popular billing platform http://support.netim.com/en/wiki/WHMCS_Module

gogetssl.com provides very cheap SSL certs via their SOAP API. They're completely white label and they have modules for WHMCS and Hostbill, among others, which could be adapted. Also, you don't need a $100 deposit like Enom, so it's perfect for smaller vendors. You need to be registered to have access to the API doc.