Cannot charge card with CVV value "000".

[colinmollenhour]

Apparently some unlucky soul has a real card with a CVV value "000" and it cannot be charged. The error is:

The card was declined. [DO NOT HONOR DUE TO AVS/CVV SETTINGS (04), AVS Result: Zip and address match. (Y), CVV Result: Not Processed. (P)]

Not sure where along the line this is broken, either the JS code, the tokenization system, or the processor.

[slogsdon]

Thanks for the report, @colinmollenhour! I'll take a look to see where this error is occurring and issue a patch if it's something within the extension. If it's not and gateway related, I'll forward this on to the appropriate internal team.

[slogsdon]

Hey @colinmollenhour, would you mind emailing us at [email protected]? I have a few questions to get some information for our gateway team to use in debugging this.

[colinmollenhour]

Email sent.

[colinmollenhour]

This appears to still be an issue.. Any update?

[slogsdon]

@colinmollenhour, I'll take a look again, but we weren't able to reproduce this originally. Does this occur only in production?

[colinmollenhour]

I haven't tested it other than in production. Since I don't have a 000 card myself I can only test with a fake card and wouldn't be able to succeed anyway. However we do have customers that have 000 numbers occasionally and they are never able to complete check out. The SecureSubmit gateway appears to return a valid public token to the client, it just fails when we try to charge the token. Considering the CVV is PAN data and it is off-limits for the server I don't see how it could be something on the server-side.

[slogsdon]

@colinmollenhour Would you be able to send the transaction ID of the latest failed transaction because of this issue over email to me [email protected]? I'd like to make sure we have the exact transaction that failed to send to our gateway team for review. Thanks!

[colinmollenhour]

Sure thing, email sent.