Different credit card payment processors use different security protocols. Ours doesn’t require the security code but looks at other attributes of the purchase. So, we’re safe ruling out the security code but obviously still have a problem.
My best guess is that this is an issue tied to the int’l status of the credit card, but I have had several int’l visa charges go through fine today. :S I talked to someone on our development team about how this works. There are a few different tests of credit card numbers that credit card systems walk through in order to determine whether a card number is valid (before even trying to charge the card and determining whether the charge is allowable from a balance standpoint).
For VISA, they look at the first digit of the credit card number and the total number of digits in the credit card number. Last, it does a numeric calculation (the Luhn Check - http://en.wikipedia.org/wiki/Luhn_check) based upon the digits and order of digits in the card number to verify that it is a valid card number.
There’s not a good way for me to look at your credit card number to see what might be tripping the invalid trigger, but can you confirm that the first digit of the number is 4 and the full number is 16 digits long? If this is the case, then the error is tied into the Luhn algorithm.
PS I emailed you earlier today to let you know that we added some complimentary credits to your account. Hopefully you can use those while we get this working for you.