Skip to main content

Understanding CVV Requirements

Learn why the CVV security code is optional for professional services and how PCI compliance affects data storage. This article explains the relationship between security codes, fraud risk, and processing fees.

Updated today

Overview

The CVV (Card Verification Value) is the 3- or 4-digit security code found on the back or front of a credit card. While designed as an extra layer of protection for e-commerce, its use varies depending on the nature of your business and regulatory requirements.


Why the Code is Optional

The CVV is primarily intended to verify that a customer has the physical card in hand during a transaction.

  • Low-Risk Environment: For most legal and accounting firms, the risk of fraud is lower than in traditional e-commerce because you have established, face-to-face or long-term relationships with your clients.

  • Processing Impact: Providing a security code is recommended, but it is not required to process a payment.

  • Fees: Opting not to enter the CVV code will have no impact on your transaction processing fees.

PCI Compliance and Security

Security standards play a major role in how CVV data is handled within the platform:

  • Data Retention: PCI compliance regulations strictly prohibit ClientPay from storing CVV information.

  • System Behavior: To maintain these security standards, certain areas of the software may not display a CVV field at all. In other instances, the field may appear but will not be populated or editable to prevent the accidental storage of sensitive data.

Did this answer your question?