https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17062#M9571 <P>Production account, yes.</P><P>&nbsp;</P><P>CCV turned on in the control panel, yes, if you mean:</P><P>&nbsp;</P><P>Fraud Detection Suite &gt; Enhanced Card Code Verification (CCV) Handling Filter is set to "enabled" and if "card code value does NOT match" is set to "decline".</P><P>&nbsp;</P><P>When creating a payment profile, bad CCVs don't get through. But they do when updating payment profiles.</P> Tue, 13 Sep 2011 05:40:16 GMT rm 2011-09-13T05:40:16Z https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17054#M9567 <P>I'm making a updateCustomerPaymentProfileRequest API call (CIM product) with&nbsp;validationMode set to liveMode. I don't believe AuthNet is performing the $0.01 ($0.00 in the case of Visa) auth because even with an incorrect CCV number, the payment profile is always updateable. Please advise.</P> Tue, 13 Sep 2011 01:14:39 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17054#M9567 rm 2011-09-13T01:14:39Z https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17060#M9570 <P>I'm assuming you're running this on a production account and not sandbox. Do you have card code validation turned on in your control panel? If you don't, the card would probably go through even if the CCV is incorrect. Also, is the card you're testing with AmEx?</P> Tue, 13 Sep 2011 02:35:49 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17060#M9570 TJPride 2011-09-13T02:35:49Z https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17062#M9571 <P>Production account, yes.</P><P>&nbsp;</P><P>CCV turned on in the control panel, yes, if you mean:</P><P>&nbsp;</P><P>Fraud Detection Suite &gt; Enhanced Card Code Verification (CCV) Handling Filter is set to "enabled" and if "card code value does NOT match" is set to "decline".</P><P>&nbsp;</P><P>When creating a payment profile, bad CCVs don't get through. But they do when updating payment profiles.</P> Tue, 13 Sep 2011 05:40:16 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17062#M9571 rm 2011-09-13T05:40:16Z https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17076#M9578 <P>That sounds like it could be a problem on Authorize.net's side of things. Can you paste your update code, since I'm sure the mods will want to see it to verify you're not doing something wrong?</P> Tue, 13 Sep 2011 17:27:06 GMT https://community.developer.cybersource.com/t5/Integration-and-Testing/validating-credit-cards-on-a-updateCustomerPaymentProfileRequest/m-p/17076#M9578 TJPride 2011-09-13T17:27:06Z