Some of the tools to fight credits/chargebacks I have been thinking off would not need alot of information sharing. Rather we need to find some common situations (ex. subscriber not loging into to his account after signup) to look for when trying to spot which transactions might end up as credits/chargebacks. The variables (ex. average days of membership, reseller hits, subscribers names etc. ) used to build a profil of potential bad transactions, would be unique for each paysite (each paysites have its own lifetime, setup etc., so it would make sense that the "profiles" are unique for each paysite). That way we can keep valuable information secure at the paysites, the scrubbing at minimum, and not end up like current processors who have setup broad scrubbing levels, which hurts profits to much for everyone involved.
Ofcourse building a database of known cheating webmasters, and subscribers doing credits/chargebacks could give an extra layer of protection. As you mention this would also open new issues like who to trust, but if this is done right, then all information would be safe from outsiders (this would ofcourse only be available to verified paysites, it would also be possible to make a system which will expose those paysites misusing the information).
It would have been great if UAS, or another trusted adult organization would have been around, but since this is not the case, then I guess we could use the almighty "dollar" as trust - meaning a private company who have money to loose if they are not professional about the setup.
|