It gave the same error for a new customer. I added the CVV though, and it worked fine. Do you have the CVV set as a required field?
[EDIT:] It was
The 'AnetApi/xml/v1/schema/AnetApiSchema.xsd:cardCode' element is invalid - The value '' is invalid according to its datatype 'String' - The Pattern constraint failed.for the new customer. Makes sense.
Along the lines of the CVV handling in the module code (specifically, in the merchant "create order" feature in the backend -- a fantastic feature, might I add)... The reason Authorize.net won't store the CVV number is because it's illegal to keep the CVV.(1) It's supposed to be passed on to the payment gateway on the submission of the transaction, then discarded. Keeping going with this idea that the CVV numbers cant be stored anywhere, and the module having CVV field set as required, merchants processing orders thru the back-end would need to contact their customers for the CVV number every time they created an invoice for the customer. It'd be a better, more practical idea to have the the CVV field defaulted as an optional field, and have the merchant be able to make it a required field, if they desire.
(1) https://www.pcisecuritystandards.org/pdfs/pci_dss_v1-1.pdf (page 2)
Joined: 02/10/2008