I only really care about the fraud score line in the API call. I take the users' IP address and their Email (at checkout) and receive a number back along with some True/False Flags. Then I simply use a 90% cut-off to make my decision. This took less than an hour to write in and since I am not a real developer, I simply copied and pasted until it worked. I also liked how it replaced two Paid Subscriptions for me, I was paying One company to validate Emails and Another company to determine the Reputation of IPs. Now, I have one key, one price and that saved me a lot of money as a business. When I lost my test key due to a mistake I got a reply from Support within hours. They responded faster than the previous Vendor I dealt with. Review collected by and hosted on G2.com.

It is completely opaque. I get "Score 93", but no explanation of why or what criteria caused the number to pass. So, when I do have to issue a refund because someone passed through fraud detection without knowing why I don't know how to answer the question so I just shrug and pay the refund. The second complaint is related to this; it torches everyone using VPNs. We had a customer on a work laptop in a Hotel who could not complete checkout for Forty Minutes while my phone would keep changing his name into something else every time I tried to enter the notes in the ticket. Review collected by and hosted on G2.com.