I spent 10 years doing CC processing for high-risk sites. So, I feel for the challenge you have ahead of you. =) That being said, do you differentiate on the

I spent 10 years doing CC processing for high-risk sites. So, I feel for the challenge you have ahead of you. =) That being said, do you differentiate on the type of fraud? Fraud is not fraud. I guess my question revolves around real fraud (stolen cc data being used), and friendly fraud (me charging back a transaction fraudulently claiming I never received a service). I'd be curious to know if you are handling that, and how. Is it merely a case of asking the people using your system to rate a particular transaction a certain way and putting into the pool of data to be processed? Or do you do something more? Also, you mention skipping verification steps. Do you do things to recommend specific extra steps, or do you just provide a score and then let the client figure it out? For example, a score of 90 might be reached in different ways. In some ways, you an automated phone call could alleviate much of the concern, while it in other cases, it wouldn't. I guess the question really comes down to whether you provide guidance on which verification steps to take.