This question has been sufficiently answered. If a merchant does in fact store this code and a card company finds out, it's big trouble and can result in some steep fines. The purpose would be to ensure that you're not storing on file a stolen credit card-primarily for the merchant's safety. What they should be doing with the verification code if they do so is requesting verification from the bank that the code does in fact match, but then they should not store the CVC code in their database. ![]() Some merchants ask you to provide this number when saving a card on file. As such, providing this number decreases the probability of the transaction being rejected.Īlternately, a transaction submitted without the CVC indicates that the transaction was submitted using previously stored credit card information, but the card was not itself present at the time of the transaction. Since this number is theoretically never recorded in any database, having this number present at the time of the transaction should indicate with greater certainty that the card itself is truly present and therefore that the transaction is not fraudulent. Therefore, any time you give that number to a merchant, they're supposed to use it immediately and then immediately forget it. ![]() ![]() Card companies require that it never be stored or recorded, but rather passed directly from the customer to the merchant gateway and then immediately forgotten. The CVC (sometimes "CVV" or "CVV2") is supposed to indicate whether the card is present at the time of the transaction.
0 Comments
Leave a Reply. |