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?