Quote:
Originally posted by Kimmykim
Interesting, but I disagree on both counts.
First off the IPSPs that are compliant with both Visa and Mastercard rules have no reason to be shaken up.
|
Umm.. I dunno about you KimmyKim, but I would call having 10 seperate class action lawsuits launched against your company within a 60 day period a reason to be shaken up.
Face it, there are *problems* in the industry. It's under fire.. the heats just on "low" right now (gee I wonder why).
If you think that adult isn't going to face more regulation soon, go check your email and see whos offering the lastest beasty/underage/rape memberships for the day
... not to mention the flood of "legal" adult UCE.
Yeah, like my grandma really needs an extra 3" added to her penis.
Quote:
Originally posted by Kimmykim
As for sorting out the number of times the join page goes to a particular processor, I have no clue why you would do it by % when the most effective means of doing it would be to sort geographically and offer the surfer the most efficient means of joining a site based on where they are from, not some silly formula for this processor gets x and this one gets y.
|
You've totallly missed the point of the message, probably because your differing viewpoint blinded you to the wholesome goodness of the post....
The idea here is irrergardless of what you say, from the
clients standpoint, the 3rd party processing industry is LESS THAN STABLE, everyone knows this. Although some processors have been doing well to stay out of the headlines ;)
For instance, I would really like to hope that a certain processor will be around in 6-12 months.. but with the looming lawsuits and other issues.. do we really know for sure wtf is going to happen with them? Hell no.
If they, or anyone else for that matter were to fold... you can bet your not getting your rebill log. Not in this day. I would almost bet that it is
illegal for them to give you your customers rebill data (because they aren't really your customers, unless your doing gateway processing which is what I've been ranting about all along)
So the point was, if its 'legally' possible, use multiple accounts & spread new joins (and the new rebills that would follow) over a few different processors using that sillly 'X processor gets shot at Y signup' formula.
Think of it as member:processor load balancing.
Depending on the correctness of it, maybe you would need to be careful of running both EU accounts & US accounts.. although I'm sure there would be ways to do it legitimately if you really wanted to.