[PCI DSS 1.x] 3.2.2 Do not store the card-verification code or value (three-digit or four-digit number p

[READ-ONLY] Archives [RETIRED] PCI DSS v.1.x Questions and Answers Protect Cardholder Data
1

[PCI-DSS] 3.2.2 Do not store the card-verification code or value (three-digit or four-digit number printed on the front or back of a payment card) used to verify card-not-present transactions.
[SIZE=3]
Note: See PCI DSS Glossary of Terms, Abbreviations, and Acronyms for additional information.[/SIZE]

3.2.2 For a sample of system components, verify that the three-digit or four-digit card-verification code or value printed on the front of the card or the signature panel (CVV2, CVC2, CID, CAV2 data) is not stored under any circumstance:

[ul]
[li]Incoming transaction data[/li][li]All logs (for example, transaction, history, debugging, error)[/li][li]History files[/li][li]Trace files[/li][li]Several database schemas[/li][li]Database contents[/li][/ul]

2

In one of our markets we have extremely high levels of credit-card fraud. In order to combat this problem, we make phone calls directly to peoples banks in order to authorize the transfer. However the banks require that we give the CVV number over the phone. Is it possible for us to store the CVV number in our system somehow, or do we need to find another way to get it from the client (the card details are only stored until the payment is authorized or until a timeout, and only 2 people have access to the details)?