4 posts / 0 new
Last post
christophergarv...
CVV validation

Both the GET and POST Tokenize Credit Card API pages say: "Note: cvv check will not happen here and card information will not be validated." Is that true for only one value of "auth", or for any value?

When is the CVV validated, or is it? And if it isn't validated, why is it required?

Related: in the response to the token-based payments service, there's a "cvv2" element whose value is "I". What does that mean?


rohitrajagopal3538
Re: CVV validation

Hi Christopher,

CVV is validated when auth=True only. Auth=true runs a 0$ auth transaction which will validate the card from the issuing bank. If ‘Auth=false’ is chosen then the transaction will not go to the issuing bank and hence the validation will not happen.

‘I’ means CVV code entered is invalid or empty. You can read more about the error codes by going to the Token Based Payments page --> On the right side of the page, view the response fields --> look for CVV2.

Regards,

Payeezy Team


leeschmidgall8217
Re: CVV validation

Is there a charge for a $0 auth, or any other concerns with using a $0 auth here? With the Compass real time platform, we actually perform a validation call - is this $0 auth the same as a card validation rather than an actual $0 auth?


rohitrajagopal3538
Re: CVV validation

Hello,

The fees really depends on the agreement between the merchant and the acquiring partner. The get token call with auth=true performs card validation (CVV and AVS) by doing a $0 authorization on the credit card.

Regards,

Payeezy team