Intergrating FraudSmack is easy and does not add any extra steps for your customer. You collect
the information from your customer as you always have, and just before you process the credit card
with the credit card processor, you add a step in your code to call the FraudSmack service, and react to FraudSmack's result code ("ACCEPT",
"WARN", or "DENY").
| Standard Sales Process |
|
FraudSmack Sales Process |
 |
|
 |
The call to FraudSmack will return a result of "ACCEPT", "WARN", or "DENY". If the result is "ACCEPT", you have your
code continue with the processing the credit card (steps 4 and 5) and complete the sale. If, on the other hand, FraudSmack returns
"WARN" or "DENY", you can have your code direct your customer to an appropriate web page to
handle that return condition, skipping steps 4 and 5, at least until
you further investigate your customer.
Pseudo code demonstrating how to use the FraudSmack result:
SubmitButton_Onclick
{
DetailedRiskScore drs = FraudSmack.GetDetailedRiskScore ( your input parameters... ); //call FraudSmack
string result = drs.o_Result; // get the overall result from the DetailedRiskScore
object
if (result == "ACCEPT") {
ProcessSaleNormally(); //your code continues to process credit
card and complete the order. }
else if (result == "WARN") {
RedirectToWarnPage(); // this page can tell them to call us to provide
more info }
else if (result == "DENY") {
RedirectToDenyPage(); // this page can tell them we can not process
their sale at this time }
else if (result == "ERROR") {
EmailParsedDrsToStaff( drs); // send parsed drs to staff so
you can see why you had an error
RedirectToWarnPage(); // treat the same as a warn, have customer call,
can process sale manually and not lose sale }
}
By using FraudSmack, you can stop fraudsters before processing the credit card,
this in many cases will be enough to keep them from using your site in the future.
Fraudsters are often only interested in determining whether the card is still valid
for making charges, and by denying their sale prior to authorizing the credit card,
they can not determine if the credit card will be authorized. All they know is that
you will not process their sale, and therefore they are likely to move on to another
site that is unprotected to try testing their cards. While this doesn't stop the
fraudsters entirely, it does repel them from your store because you are not providing
the information they need.