|
If it were me and I had a solid ~/> 30 signups a day....
I would either
Plan A: I'm a king, I have my own merchant accounts!
Setup several merchant accounts, either all in one company name, or 1 merchant account per DBA. Use authorize.net, netbilling or someone else as a gateway processor and spend a small portion of the big money (~10%) saved in processing fees on a 24 hour answering service to handle 'customer support' --- easy enough to code them a low-access, no-damage admin panel.
Plan B: Please don't rob me of my rebills & reserves!
Setup 3-5 3rd party processing accounts.... try some of the 'free', no-visa-reg ones if you want to save and spread.
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.
We have a product that allows you to keep all the htpasswd files seperated at the apache level. It was created because we are strong believers in the scenarios listed above. But obviously this post is more than touting our own products so I won't mention it beyond that.
|