10 posts / 0 new
Last post
ab9446
CVV validation only for the $0 auth

Hello,

Is it possible to have a merchant account that will do CVV validation for GET https://api-cert.payeezy.com/v1/securitytokens (adding the card and getting a transarmor token) but not require the CVV for any subsequent transaction via POST https://api-cert.payeezy.com/v1/securitytokens .

"E-Commerce Transaction (CVV2)" seems to require the CVV to be passed along for future transactions which is not possible due to PCI compliance, but I still want the initial $0 auth to validate the CVV (which "E-Commerce Transaction" doesn't seem to do).

Thanks.


rohitrajagopal3538
Re: CVV validation only for the $0 auth

Yes. During the GET tokenization call, setting auth=true allows you to do address and CVV verification. CVV is not required in any subsequent transaction and so you do not need to save it.


ab9446
Re: CVV validation only for the $0 auth

But when I test this in the sandbox with the CVV '234' (from here https://support.payeezy.com/hc/en-us/articles/204504185-How-to-test-CVD-CVV-CVV2-functionality), it gets created without an error.


ab9446
Re: CVV validation only for the $0 auth

Double post.


rohitrajagopal3538
Re: CVV validation only for the $0 auth

Yes, setting the verification value to "234" for a transaction would simulate the CVV2 Response "N". If the transaction is processed under a terminal that has the "CVV2 does not match" filter checked, the transaction will be declined due to failed CVV2 verification. Which sandbox account are you using for testing? The "Acme Sock" is configured to decline transactions when CVV2 verification fails. If you need this ability, you will need to add your own demo gateway account to your developer account and test.


rohitrajagopal3538
Re: CVV validation only for the $0 auth

Setting the verification value to "123" for a transaction would simulate the CVV2 Response "M" which is a match. This will not result in a declined transaction.


ab9446
Re: CVV validation only for the $0 auth

Merchant ID: 4635989683
API Key: AFCrcuanHTKv3riYIMFtRbNrjuNMjsN1

I'm not getting that response. Note that this is with the merchant type is set to "E-Commerce Transaction".

It does work when the type is set to "E-Commerce Transaction (CVV2)". The problem then is POST https://api-cert.payeezy.com/v1/securitytokens where I get the following:

Request:
{
"merchant_ref": "Astonishing-Sale",
"transaction_type": "authorize",
"method": "token",
"amount": "200",
"currency_code": "USD",
"token": {
"token_type": "FDToken",
"token_data": {
"type": "visa",
"value": "9147925569961111",
"cardholder_name": "John Smith",
"exp_date": "1023"
}
}
}

Response:
{
"correlation_id": "124.1468004350457",
"transaction_status": "declined",
"validation_status": "success",
"transaction_type": "authorize",
"transaction_tag": "87512645",
"method": "token",
"amount": "200",
"currency": "USD",
"cvv2": "I",
"token": {
"token_type": "FDToken",
"token_data": {
"type": "visa",
"cardholder_name": "John Smith",
"exp_date": "1023",
"value": "9147925569961111"
}
},
"bank_resp_code": "100",
"bank_message": "Approved",
"gateway_resp_code": "08",
"gateway_message": "CVV2/CID/CVC2 Data not Verified"
}

I'm using the same merchant account for the transaction without changing anything.


rohitrajagopal3538
Re: CVV validation only for the $0 auth

Which CVV filters have you selected?


ab9446
Re: CVV validation only for the $0 auth

CVV2 does not match(N)
Merchant indicated that CVV2 is not present on card(S)
CVV2 code is invalid or empty(I)


rohitrajagopal3538
Re: CVV validation only for the $0 auth

The transaction is getting declined because this CVV2 filter is selected - CVV2 code is invalid or empty(I)

The filters you select are applicable to all transactions. So, going back to your original question, you cannot enable the CVV2 filters for the tokenization calls alone.