PCI DSS POLICY
Payment Card Industry - Data Security Standard Policy
I.PURPOSE
The purpose of this policy is to establish guidelines for processing charges on Credit Cards to protect against possible theft of credit card account and personal cardholder information that has been provided to our Company, and to comply with the Payment Card Industry Data Security Standard (PCI DSS) requirements. The Company will adhere to PCI DSS standards in order to protect its customers, limit its liability and continue processing credit card payments.
II.SCOPE
This policy applies to ALL company departments, employees (working on-site and off-site), as well as independent contractors and/or apprentices/volunteers. This policy applies to any party that processes, transmits or handles cardholder information in a physical or electronic format. All computers and electronic devices involved in processing payment card data are governed by PCI DSS. This includes servers, computers, workstations & terminals that process, transmit or store credit card information.
III.POLICY
Any internal or external parties involved with the acceptance and processing of credit cards must ensure that PCI DSS compliance is maintained. To meet the Payment Card Industry requirements, the following will be strictly enforced:
General Requirements
A.Access to resources and Cardholder Data should be limited to only those individuals whose job requires such access.
B.Any job position that requires access to stored Cardholder Data will be considered security sensitive. Criminal and credit background checks must be performed for any person prior to assignment of duties that includes access to stored Cardholder Data. NOTE: As we transition into the adherence of this policy, the Company may initiate such checks on personnel who are presently performing the job duties newly defined as “security sensitive.”
C.Personnel involved in credit card processing in one of the following categories must attend credit card security training every year.
Has access to cardholder data.
Handles credit card payments or refunds as part of their regular job duties. Personnel who handle credit card payments on a one time or temporary basis are recommended to attend training but not required.
D.Any person processing credit card information must agree not to disclose or acquire any information concerning a cardholder’s credit card account without the cardholder’s consent.
E.Credit card numbers should never be stored on a personal computer or left unsecured on a desktop.
F.Credit card numbers should never be transmitted via unencrypted email or any other unsecured transmission method—including unified messaging.
G.A self-assessment questionnaire will be completed annually by the merchant.
H.Appropriate segregation of duties between credit card processing (sales and refunds) and the reconciliation function must be maintained.
In-Office Processing Requirements
If credit card data is received via a “secured” fax machine or via the mail, the hard copy that contains credit card data will be subject to the following requirements. Note: If the transaction is subsequently processed using a terminal or the Web, it will also be subject to those requirements.
A. Physical cardholder information must be locked in a secured area, and limited to only those individuals that require access to that data. In addition, access should be restricted to data on a “need to know” basis.
B.Credit Card transactions should be processed in accordance to Company guidelines and the credit card number should be red-noted to include no more than the last four digits. In addition, any Sensitive Cardholder Data should be masked.
C.Stored credit card information will be retained according to the Company retention policy so long as there is a business and/or legal purpose.
D.The following procedures shall be followed for masking credit card information when no longer required:
Blackout credit card number except last four digits and any Sensitive Cardholder Data
Cross-cut shred the original immediately (and not later than same day. If this option is utilized the credit card data shall be secured until shredding occurs).
Retain, if necessary, hard copy of document with unreadable credit card information.
General Credit Card Processing Requirements
A. Cardholder data should not be stored on the PC terminal.
B.Do not print the entire credit card number on either the hard copy or customer copy of any receipts.
C.All terminals must be PCI DSS compliant.
D.Notify the EVP of Operations about any technology changes affecting transaction processing.
Web Payment Processing & Electronic Storage Requirements
A.Approval by the Leader/PCI DSS Task Force or the Company’s EVP of Operations is required before entering into any contracts or before purchasing software and/or equipment that processes, transmits or stores credit card data
B.Sensitive Cardholder Data should not be stored
C.Third party payments should align with PABP or PA DSS approval.
D.Each merchant is responsible for assigning someone to administer the control of log-in privileges, limit software access to secure methods, delete or revoke access to software for terminated employees. Vendor-supplied defaults for system passwords should not be used.
E.Merchant will notify the Leader/PCI DSS Task Force and the EVP/Operations regarding any technology changes affecting transaction processing.
F.Network vulnerability scans shall be performed on machines/devices that are involved in the processing of credit/debit cards on a least a quarterly basis and after any significant change in the network.
IV.SANCTIONS
Merchants not complying with this policy may lose the privilege to accept credit card payments. Additionally, fines may be imposed by the affected credit card company. Persons in violation of this policy are subject to the full range of sanctions, including the loss of computer or network access privileges, disciplinary actions, suspension, termination of employment and legal action. Some violations may constitute criminal offenses under local, state and federal laws. The Company will carry out its responsibility to report such violations to the appropriate authorities.
V.DEFINITIONS & RESOURCES
A. Payment Card Industry Data Security Standard (PCI DSS). PCI DSS is the result of collaboration between the four major credit card brands to develop a single approach to safeguarding sensitive data. PCI DSS defines a series of best practices for handling, transmitting and storing sensitive data.
B.Cardholder Data: Includes cardholder name, full account number, expiration date, service code, PIN / PIN Block or Card Validation Code (e.g. three-digit or four-digit printed on the front or back of a payment card (CVV2, CVC2 data).
C.Sensitive Cardholder Data: Includes Card Validation Code
D.Merchant: Any person/department/company accepting money for goods or services. Includes fees.
E.Credit Card: Any payment card, including debit cards, which is issued by one of the major credit card associations (e.g. Visa, MasterCard, Discover, American Express, et al)
F.PCI DSS Task Force: A committee appointed by the Company to be responsible for full PCI DSS compliance.
G.Payment Application Best Practices (PABP): Program developed by Visa to assist software vendors in creating secure payment applications that are PCI DSS compliant.
A list of all vendors currently PABP compliant can be found on
Visa’s website.
H.Payment Application Data Security Standard (PA DSS): Program managed by the Payment Card Industry Security Standards Council (PCI SSC) formerly managed by Visa and known as PABP. PA DSS is a set of standards designed to assist software vendors in developing secure payment applications that comply with PCI DSS requirements. A list of validated payment applications will be listed on the
PCI SSC website.