Quote:
|
Originally Posted by **********
Hi,
Cascade billing can be good for some websites, but we at LiveCamNetwork.com prefer NOT to use cascade billing for several reasons.
First, we trust CCBill to take care of most of our fraud scrubbing. We have written our own fraud scrubbing layer called AHMAD, but overall, We trust CCBill's decision. if CCBill refuses a transaction for ANY reason, why should we question them? We trust CCBill to be the expert on credit card billing, otherwise, what are we paying them for? Why cascade that purchase down to a smaller provider who has weaker fraud-detection services or scoring practices? Just so we can make the sale only to have it charged-back later?
As a LIVE entertainment provider, 2Much / LiveCamNetwork suffers real losses when people use stolen credit cards, because we payout to the performers no matter what.
If you have a membership site, or site with "static" content that you've already paid for, Cascade billing isn't really a bad idea. But if you have a LIVE site with on-going costs, my suggestion is to FORGET Cascade billing. You have little more to gain, but take on a much higher risk.
Mark Prince
2Much Internet Services Inc.
|
Cascading billing is not just all about scrubbing. Sometimes, a card may be declined because of a network error where the backend processor could not get an authorization at that moment. Also, cascading credit card declines to a chack page works well. We use Netbilling exclusively as our gateway but do sometimes cascade between merchant accounts, depending on if it is a bank decline, fraud scrubbing decline or a network error.
It is good to trust your processor but the more control you have over things in the long run, the more money you will make.