I've commented on here recently about wanting to be able to save more than one credit card per customer, but my opinion is shifting a bit. I think the answer might be to have a table of CC info tied to Sales Order number. Some of our customers use the same CC each time, but most have multiple and still others never seem to use the same one twice. Keeping a list of CC from which to choose (a la Amazon) is a good idea, but we need to choose the card or enter the info at the time the SO is made and tie that info to the SO until the invoice is created, which could be weeks. The only answer we have found is using the SO notes field, which is okay, but it is cumbersome to retrieve when needed and is insecure in not only that it isn't obfuscated in the data tables, but also that it could wind up printed out with documents, even if the notes are hidden.
 
So, the idea is, independent of any stored CC info, a table of CC info tied to SO number, not printable on SO/Invoice/etc, but easily retrieved when needed... and ties into the CC processing add-on module thingie.

Laughable. They don't have the resources to enforce that in their own state, never mind the rest of the world. I doubt that their own division of motor vehicles could pass a ten minute audit.