Wed, 06/15/2016 - 14:43
#1
CVV2 Testing with Demo account
Does CVV2 filters work with demo account. We updated our terminal cvv2 filter to reject transactions on code "N" but I am still getting an approved transaction with CVV2 code N in the transaction result. Does it take time for the changes to take effect in your test system or do I have to perform any additional steps?
Thanks
Did you enabled the CVV2 filter on a production gateway account? If yes, that has no bearing on the sandbox transactions. In sandbox, you are likely using the default account "Acme Sock" that is present in your developer account under the Merchants tab. This is a First Data owned demo gateway account in which we have no CVV2 filters enabled.
Hope this helps.
We don't have a production account. we are still testing our applications using the demo account created at https://demo.globalgatewaye4.firstdata.com/. I turned on the CVV2 filter under Administration-> terminals -> cvv2 filters
Thanks
Unfortunately, your developer account is not connected to your demo account created at https://demo.globalgatewaye4.firstdata.com/. So, the changes you make in your demo account will not apply to the transactions you are doing with the "Acme Sock" merchant.