Authorize.NET CIM - How Card Code Verification is handled for transactions?

[jlist2015]

Summary: I can't seem to find anywhere in the CIM API or AIM documentation a specific explanation or confirmation that CIM AuthCap transactions benefit from having a confirmed CVV on the payment profile.

I understand the value to the Merchant after 1 October to confirm a valid CVV when submitting a CreateCustomerPaymentProfile, but since neither my interface or Authorize.Net are allowed to store the CVV, how does a confirmed CVV on a CIM Payment Profile benefit an AuthCap transaction where we only submit the Customer ID token, the Payment Profile ID token, and the amount to authorize? Does Authorize.Net set a "flag" on the Payment Profile that the CVV has been confirmed, or is the transaction submitted to the processor without benefit of the CVV?

[RichardH · Accepted solution]

Hello @jlist2015

Great questiion. CVV is useful for increased security which can be validated during transaction processing.

CVV is useful when creating customer profiles because it adds an additional layer of security

When creating a customer profile, if you include a CVV and you set validationMode to livemode, the CVV is used with the validation transaction and the results will be included in the response.  If the validation transaction was declined due to an incorrect CVV, no customer profile will be created.

CVV can also be used in future transactions to increase security

If you allow the user to select an existing payment profile but also require them to enter their CVV for subsequent transactions, the gateway will be validated as part of the request and the results will be included in the response.

Richard