Quote:
Originally Posted by cw1865
1. If the order volume is such that manually running the orders makes sense, do that.
2. If the order volume exceeds this, perhaps the system can do an authorize and capture (instead of simply authorizing)
Personally, I manually do it and frankly its the favorite part of my day.
1. If billing matches shipping, I run the transaction, if AVS is in any way negative, I'm looking at IP Address, if area code for zip code is correct and things of that nature. Even aside from fraud, this also helps to prevent shipping to an incorrect address, you'd think people would type their addresses correctly all the time, but believe it or not they do make errors. I'll even google the phone number/address because sometimes that helps {you'll find addresses linked to freight forwarding companies, and that to me is an automatic kill order}
2. If billing doesn't match shipping, I do all of the above first and make the decision to authorize/capture based on my own 'subjective' feel AFTER 12 hours has passed. <-this snares most stolen cards because most people DO report their cards stolen.
Last year I got tagged for ONE fraudulent order and frankly I should've known better.
|
This is the way we do it, too. Manually capture the information, call our CS line, get the number of the issuing bank, speak to a live person whenever possible to validate the information, then process the transaction, or not. We've also gotten pretty good at guessing if an order is fake or not, before we even call to try and verify anything. We also give card users a financial disincentive to using a card by having a 3% Handling Fee to manually process the transaction. On a $30k watch, that's $900 of disincentive; not small potatoes! Worst case scenario, which we've had happen, is for someone's account to be hacked and all the info changed, including addresses. You get a clean and validated transaction...until the real owner files the chargeback 45 days later. You're out the product =and= the cash. As usual, the bank claims no responsibility, even though =their= system was breached. We had this happen one time on a, for us, fairly small transaction; total loss was about $13k. Next time it happens, I think we'll sue the card holder themselves for not protecting their card information better thus allowing the hack.
Lyle Knox
FeelGoodWatches.com