servnetix said:
We offer a development solution that would allow you to do that, currently it isn't one we will be adding but it's on the list.
Both ModernBill and whois.cart offer integration with BluePay; both say it was a very simple implementation.
But I'm not going to buy a system that doesn't offer my gateway as a supported option.
What are the benefits of your package over ModernBill, so that I should consider changing gateway accounts?
Not sure what CISP is can you explain.
According to
VISA:
<snip>
Members must use, and are responsible for ensuring that their merchants use, service providers that are CISP-compliant. Service providers who have validated compliance with CISP can be found on the List of CISP-Compliant service providers. A Member who uses a service provider, or whose merchant uses a service provider, that is not a compliant service provider should refer that service provider to the CISP site for information on how to become compliant. Although there may not be a direct contractual relationship between merchant service providers and Acquiring Members, Members remain responsible for any liability that may occur as a result of non-compliance with CISP.
</snip>
And...
<snip>
If a merchant or service provider refuses to participate in CISP, Visa may impose a fine on such Member responsible for the merchant or service provider. Ultimately, merchants and their service providers must meet the CISP requirements to continue to accept Visa Payment products.
</snip>
we haven't set-up any affiliation with any of the registrars because they all offer different feaures and I don't want to push customer to one over the other.
Again, both ModernBill and whois.cart have, with Enom, and in both cases, they've negotiated much lower prices than I could get myself. So, again, there should be a reason why I'd give this up in order to use your offering... in what way is it better
?
About the Domain issues we will not offer a complete integration of a registrar. this would cost a ton of money.
It wouid cost us the same "ton of money", and it would be a lot more cost-efficient if you could do it and build your costs into the price.
We recommend you sending them to the registar Directly so if they ever leave they know were to manage the domain for themselves.
The problem with that is that to resell at least some of these providers you have to have code approved so your customers can manage their domains. As an example, OpenSRS requires you have your domain management interface approved before you can use your account.
Let me add that we do offer a customer interface so they can update information, add services, make payments, review invoices and even open support tickets. There are also domain tools they can use to ping trac and who-is.
These are all good features. Is your support ticket service integrated with DirectAdmin's? If not, then I imagine having two such ticket systems may confuse our clients.
We highly recommend hosting on it's own server , however we have many customers that host on the same production server.
This sounds very reasonable to me.
At the moment the show-stoppers for me are the domain management, the higher-priced domain registrations, and of course the fact that I can't manage your system with Linux.
Perhaps we should carry on the rest of this conversation privately; can you please email me with your contact information? (Mine is below, in my sig.)
Thanks.
Jeff