Quote:
Originally posted by goBigtime
 CCbill is worry free eh? The whole 3rd party processing industry is very shaken up, and those who aren't are too new/naive to know they should be.
Then have someone code up a solution that allows you to specify the % that each processors join buttons show up when your surfers visit your CustomJoin.cgi to passively spread the load, or if you want accurate and active balancing have it create a db that keeps track of which processor has X signups.
|
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. These are the guys talking to Martin Elliot on a near daily basis -- these are also the guys that have great relationships with their banks and have wonderful sources within that community as well. As long as they do as Visa/MC require they should have no real problems but will continue to have a heavy workload implementing new crap that comes along.
Having 3-5 processors is not a good idea, since you cannot use two different regions to acquire on the same site. If you get caught with an EU and a US on the same site you run the risk of being told by both of your processors that you are terminated.
Personally I think two credit card processors is plenty for Visa and Mastercard transactions.
Where someone should look to diversify and add to their revenue stream while minimizing their risk is with alternate sources of billing -- dialers, sms, regional credit cards like JCB, Eurodebit, etc.
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.