Anyone using FraudRecord?
- Thread starter vpsnewb
- Start date
-
- Tags
- fraud order
Well, we recently saw an event on LET where a provider posted the wrong FraudRecord on the wrong account, therefore prohibiting that user from purchasing a service with another provider (its been taken care of now). Honestly it's a great tool but the way that it's setup allows for possibilities for mistakes like that to happen.
Personally, we use it as another tool to evaluate our new prospective clients and to reduce the amount of fraud orders we get. I hate to say this but our gut feelings does factor into it.
Personally, we use it as another tool to evaluate our new prospective clients and to reduce the amount of fraud orders we get. I hate to say this but our gut feelings does factor into it.
I assume it logs what provider adds records to it, yeah? Are these publicly available or only to those with the service?
It seems like a great tool and I want to check it out, but it seems like there are some obvious potential flaws, but since I haven't used it I don't know if these things have been accounted for.
The logs are publicly available, but the client's name, e-mail, IPs, etc. are all hashed (so its a bit difficult to find a specific record without knowing the person's information first to being with).
The WHMCS plugin for it though is actually quite convenient to work with.
The WHMCS plugin for it though is actually quite convenient to work with.
jarland
The ocean is digital
We use it for sure, but I am very outspoken among the three of us that the information needs to be taken with a grain of salt. Also, if I feel that a problem is resolved and/or I believe there is little chance of this person doing the same to another provider, I will not add a report. I believe that the value of FraudRecord depends on us providers not posting out of anger or spite.
I've tried it and didn't feel that it was worth the hassle.
When reporting a client you can't do it from one page, you have to make your way to the separate FraudRecord page in WHMCS. Sure, it's a good idea and I understand it's not for profit however it would be great to have some functionality tied in a bit "closer" to WHMCS to make the reporting a little more simple and convenient.
When reporting a client you can't do it from one page, you have to make your way to the separate FraudRecord page in WHMCS. Sure, it's a good idea and I understand it's not for profit however it would be great to have some functionality tied in a bit "closer" to WHMCS to make the reporting a little more simple and convenient.
I have considered it, however at this time I am not using it
I like the concept of it however it's bad from a customer point of view, Harzem is a good guy with good intentions but if I get wrongly tagged just because someone does not like me how do it I get it removed, there is no process, no way of me knowing my data is in fraudrecord unless the provider who rejects me or put me there says something.
And aside from that what data protection? I am all for using tools to spot the abusers but not at the price of blatantly dodging the legalities of it all, in fact no provider in the EU should even be using it as they breaking the law.
And aside from that what data protection? I am all for using tools to spot the abusers but not at the price of blatantly dodging the legalities of it all, in fact no provider in the EU should even be using it as they breaking the law.
FR has probably prevented 10 or so carders, a few spammers. Its not really big enough to make a difference but reporting the worst of the worst is helpful.
We have a HB port on the TODO list.
We have a HB port on the TODO list.
Currently not using it, but considering looking in to it. We have created our own routines and screening processes to make sure that no fraudulent orders pass. This is of course an more or less impossible feat, but we are seeing far far less abusive signups now than what we did a few years ago.
We use it as a secondary check. Haven't had any issues with it yet.
I'd really like to point out that Fraudrecord shouldn't be used as a be-all, end-all fraud detection tool. It's just that: a tool; something providers can use in their usual process, with good judgement and input, to determine to carry a client or not.
Here is, for example, a good report: https://www.fraudrecord.com/api/?showreport=af21f4161a215c52
Here is a not so useful report: https://www.fraudrecord.com/api/?showreport=aa35cd9ce3933253
Based on the prior good/bad reports, when reviewing the 'good' report, it was indeed found that the individual was spamming, so they were terminated. Based on the bad report, we haven't heard a peep from the individual.
Here is, for example, a good report: https://www.fraudrecord.com/api/?showreport=af21f4161a215c52
Here is a not so useful report: https://www.fraudrecord.com/api/?showreport=aa35cd9ce3933253
Based on the prior good/bad reports, when reviewing the 'good' report, it was indeed found that the individual was spamming, so they were terminated. Based on the bad report, we haven't heard a peep from the individual.
Aldryic C'boas
The Pony
In theory, such a setup sounds like a decent idea. But after reading some of the 'provider commentary'... I'd be wary on trusting reports at all. Demi works well enough for our anti-fraud; we'll just stick with her.
Yeah right,
We get spammers all the time that are pretty damn decent at what they do. sleeper accounts, 'resellers' pretending to be neutral etc.
I look for the obvious stuff.
Its a fun game.
- Non-matching PayPal name
- A non existent host-name or domain name
- A hostname linked to a blank page or a page with some BS one liner
- Weird looking company name; blah blah LTD solutions incorporated
Its a fun game.