Adult payment processors ccbill etc

I can not believe that dolphin still does not have native support for adult payment processors. Is boonex missing a trick or what? I still have a site running dolphin 5.6 and using aMember to accept payment through ccbill.

Now I am redeveloping the site. I was going to code it my self from scratch, but thought I'd check out the latest dolphin offering and see if it had improved sinse 5.6 which was just a buggy mess. Well dolphin 7.5 seems usable, and not as buggy it seems so far. Also better value for money. Still very querky and coded in a strange, disjointed way though :)  I'm liking a lot of the features so far, and the more mudular approach.

So why no adult pay processors? Even 5.6 had built-in support for ccbill, although too basic to be of any use, but there is no adult support for dolphin 7 at all, and yet it's a great platform for developing adult and dating sites with. I have looked in unity for adult payment mods and appart from a couple of out of date ones, can't even find anything there!

I think for any software like this, it should be very important to include a wide range of adult and non-adult payment processors as standard, so that it makes the software "more buyable", and continues un-interupted payment support when updating to latest versions, with out relying on 3rd party mods that may not get updated in time for new releases, or may not get updated at all!

Is there a good, functional, reliable adult payment (especially ccbill) mod out there? Or am I going to have to develop my own?

this works great and supports authorize.net for payment processing.

to attempt to provide these as default would require somebody from boonex staying up-to-date on the changes made from these gateways. they just dont have the time to keep up with the requirements, as they are busy developing the core platform.

http://www.boonex.com/unity/extensions/entry/Dolphin_7_Membership_Subscriptions_Module

did you take a look at that one?

No it isn't true that it would take up all their developer time! The developer of aMember develops and updates pay processor interfaces for about 50 or so pay processors by him self, as well as developing and maintain the main aMember software him self. Other script script developers do to, so as cart developers. The pay processors do not make changes very often that would effect the rutines and call--backs for 3rd party integration. When they do, they are normally minor, such as changing a url. It's normally only changes between dolphin versions that break pay processor functionality, not the other way round! There's no reason why the dolphin devs couldn't keep a good selection of payment processor interfaces maintained and included as standard, with out distracting them from the main dolphin development!

I had a look at the one you linked. I'd seen it before, but thanks any way. No ccbill though! Also not much info about it's verotel support. However, I already have 100s of members on my current site on monthly billing cycles with ccbill. So what ever I do I need to include ccbill to maintain those.

i mention authorize.net because of your reference to ccbill etc, so i provided mention of the etc. support on that module is superb, but as you state, you need CCBILL. you can inquire of him, because i think at one point, his mod actually supported CCBILL, and he may very well customize that for your needs.

i know specifically that coding for any of these payment gateways is a time consuming task, the dynamics of dolphin would not allow their team to keep updated instances of the payment processors. thats why they were dropped from v-6.x.x

i would give it a few days or so, as martinboi the author of the memberships module, is the brother of one of our Beloved and Cherished unity members who passed away. but i am sure that he would be able to provide your solution for CCBIILL

I agree 100% for the need of CCbill as a payment processor.  It is the number one adult processor and is, therefore, fairly ubiquitous.

Please make CCbill as one of the payment processors for Dolphin!

You will find a CCBill MOD here

 Yes I will be trying that mod out, but the point is, adult pay processors such as CCBill should be included as standard. It is not at all true that they take lots of time to develop and change all the time! I have worked with these processors over the years on different systems, and they only ever make minor changes! Coding for them is not at all rocket science, so adding as standard feature in dolphin will be streight forward!

well blimey, if its not rocket science, then by all means, create your module for CCBill and use it on your dolphin site. semi-demanding boonex to tend to your whims by adding ccbill becuase its used for adult sites is a tidge funny. i want google checkout as a payment processor, so you think i should demand they include that in their software as well because i have family oriented and business oriented sites that need to process payments?

okweb provided an option, i dont think boonex wishes to continue providing the payment gateways, there are too many and too many people have preferences.

What's got on your goat? I've just ordered a CCBill processor mod, so hopefully I won't have to custom develop one. The whole point that you seem to be missing is that more pay processors should be built in as standard. As I have said before, but you seemed to know better, pay processor programming is quite easy. They are designed to be easy. The pay processors make it easy in order to compete in the market. The worth of dolphin would be increased if they provided better support for pay processors out of the box. Yea google pay too if that's what you want for your family site, although you'd be better using paypal for that. Dolphin is marketed as a business platform, and business platforms need pay processors.

oh nothing has my goat. just babbling. you are correct, i could use paypal, but i dont like paypal and google doesnt make me beg for the funds to be sent to my bank acct. also, as a business entity, google checkout is more friendly for those who are paying an invoice or making a payment from a cart. you are correct, dolphin is develped as a business model, and with that business model, not all require processing for adult content. that is only one small portion of the greater scheme.

yeah i was just saying that based on your analysis, that it wasnt rocket science, then you should write the module and offer it for free. its easy as you state, and the payment processors write them to be easy. let us know when we can expect the module to be ready for download?

:)

 Ha, well I do code payment interfaces. That's the easy bit. However, getting to grips with dolphin's mod system and coding quirks, in order to create a pay system, isn't something I've really got time to learn right now. I just want to get this site updated ASAP! I have now installed Igor's CCBill mod, so hopefully that will do! I don't really think it's for me, Igor or anyone else to release a payment mod for free. I think they should be integrated in dolphin core as I have stated - just the popular ones, but including adult ones as they used to.

You said "not all require processing for adult content. that is only one small portion of the greater scheme."

It's not as smaller portion as you may think. It is still the largest collective industry on the web, and the pay processors that specialise in or support adult business models process a large percentage of all transactions performed online. You have to remember that dating sites that do not allow anyone under 18 (almost all of them), are usually classed as adult sites, especially if they allow adults to freely express them selves, and are therefore often not fully supported by most non-adult pay processors. So it's not a small portion of the greater scheme, but a nessesery area for support!

im just busting your chops man. i think payment modules 3rd party or otherwise are a crucial part of any site that is accepting payments or using the (cough cough) shopping cart provided with dolphin.

i think they should not be core elements, here is the deal bud, just so you understand. you may be 1000% correct that the payment gateways dont upgrade often, i am aware that authorize.net went through an immense update as we were transitioning from version 7.0.1 ---> 7.0.2. the processing options that are available and the specific details that any given client could request from those payments and updates. so the problem with asking boonex to include these payment modules in their core element, could prove disastrous, because if, and i am stating 'if' here, if there were an update for whatever reason on any given payment gateway, and boonex was months away from releasing any updates, then we would be forced to hack the modules ourself, or sit idle waiting on boonex to release an update. now the problem with hacking the module for any given release on the payment gateways protocol, would ultimately create serious issues when boonex does release their update or upgrade to the dolphin platform.

the benefit in having this provided from the 3rd party developers is that they could update as soon as there is a release. if you have been around here for any given length of time you would understand what i am saying here about the dangers of asking boonex to manage and be responsible for the payment modules. at any rate, you are correct, it would be great to have one module from any source that took care of all the possible gateway sources.

Yea I've been here since 2007 - just don't hang out here often! You have a point with updates. A very valued point too. Now I have to find a way of busting your chops back! OK here we go. Boonex already provide 2 gateways as standard. That's like a token jesture - so boonex can "sell" the product as being bundled with payment systems right outa the box. A marketing thing. Tiz all. With all versions of dolphin there are loads of horible bugs, and security issues that don't get addressed or patched by boonex between versions. However, the "community" are normally quick to share fixes or workarounds. In the case of payment processors, if they did change between dolphin versions, the change would most commonly be a url or query string change. With the main structure already in place, for most of us it wouldn't be too hard to hack that change and fix it. If it was more seriouse, then the "community" would pull together to fix it.... wouldn't they? From my experience over the years, I have never had a pay processor change a front end on me. The changes have always been back end. When they've sent an email out saying that they are making big changes to their systems, my response has always been, "Oh no. Shall I shoot my self now or wait and see."  However, after the changes have been made, everything has just worked the same with me not  haveing to make changes at my end. I think pay processors realise that they have to make changes transparent to their clients so as to not give their clients a bad experience with their service. 2CO always make a lot of changes, and make a big deal about it, but they always put redirects in place if necessary so that their clients don't have to make changes their end. So I think if boonex did provide a selection of the most common azdult and non adult processors, there would unlikely be any issues. And hey, maybe boonex could, and should release patches for issues such as that, or security issues!

Your point about 3rd parties being able to make updates quicker is still a very good point, but I think one of the issues is having alternatives. It's always important to be able to offer one or more alternative payment gateways to your members incase one fails, closes, or defaults you. Eggs in one barsket etc. I learned that the hard way when iBill sudenly closed down a few years back. That was a major fuck up for a lot of businesses, and sudenly I had no income, and had to work my nuts off to sort a new billing provider, integrate it in loads of sites, and explain the situation to loads of confused, angry punters. With dolphin as it is currently, if you have a non adult site that can use non adult billing, you are gifted with two pay processors - paypal and 2CO. That's fab, and you always have a backup. But there aint nothing provided outa the box for adult sites, including dating sites, let alone a backup you can go to if the first one goes wrong. Lets face it, dolphin's heritage is as a dating software, and it's current use is still predominantly dating. So for boonex to just provide two payment processors, neither of which are suitable for dating sites, well, it's a bit pointless, a bit of a marketing gimik. They could do better, and it would be a better "selling" feature!