Re: AVS mismatch prevention

I just read that here, hmm. Seems like a counterintuitive way to set up the system, I would logically expect that decline means don't charge at all. But personally, I just allow through the transaction as long as the zip code matches. It's hard to mess that up, and people aren't likely to hit it by guessing. Don't know if that's the smartest solution but it's been working for me so far.

Re: AVS mismatch prevention

The problem we see is assistants using the boss's credit card to make the charge, using information they wrote down a year ago. So, when the boss got his new card and the CCV number changed, they failed to pass this information along. So, the assistant tries to use the old information.

We had to resort to blocking them in our app after three failed attempts. Otherwise, they would run up dozens of declined charges, which results in dozens of holds and dozens of transactions fees to us.

Re: AVS mismatch prevention

Or scream louder since we've been reporting this issue as far back as 2009, if not longer. We were told back then that a solution was coming. Guess when the banks are in trouble, solving issues like this gets put on the back burner.