Mobile Device Use For Credit Card Payments

Mobile Device Use For Credit Card Payments

Technical Requirements and Instructions for Device Configuration

Introduction

The Technical Requirements and Instructions for Device Configuration of Mobile Device Use, apply to the process of accepting credit cards as payment for goods and services on a University- owned Mobile Device.  Campuses may establish guidelines within the scope of the Technical Requirements and Instructions for Device Configuration of Mobile Device Use For Credit Card Payments. Guidelines may be more, but not less, restrictive of these requirements.

Purpose

To reduce the risk of credit card fraud, ensure cardholder data is private and secure, and protect University assets.

Scope

This standard applies to all approved University of Massachusetts merchants, including employees, contractors, and managers, who are responsible for accepting payments, providing technical support, or securing equipment used to transact credit card payments on a University-owned Mobile Device.

Book Category
Treasurer's Office: Administrative Standards

Section A. Mobile Device Use

Section A. Mobile Device Use

In an effort to bring efficiency and improved shopping experiences to our customers, the University allows merchants to use University-owned mobile devices, such as smart phones or tablets, for credit card payment acceptance. Mobile payment acceptance brings about new risks to the security of cardholder data, and therefore, payment card acceptance on a University-owned mobile device must be in accordance with the guidelines outlined in this document, as well as those outlined in Section E, related links. 

Only University-Owned mobile devices may be used for credit card payment acceptance on behalf of the University.  These devices should be used with a Payment Card Industry (PCI) compliant application and work in conjunction with a PCI validated P2PE solution. 

The mobile card reader used with the University-owned device must be obtained from a PCI validated provider who is listed on the PCI Security Standards Council (PCI SSC) Point of Interaction (POI) list. This list outlines the approved card readers tested to work securely with the mobile solution. Additionally, the POI solution provider must be compliant with the appropriate PCI SCC security requirements, including the Secure Reading and Exchange of Data (SRED).  

Section B. Security & Technical Standards

Section B. Security & Technical Standards

Mobile devices create new challenges for the collection of payment information.  It is imperative that campuses ensure adherence to all applicable PCI DSS and Data Computing, Security & Technical Standards when using University-owned devices for payment card acceptance.

Payments must flow to a merchant account that has been established through the University Treasurer’s Office (see Treasurer’s Office Administrative Standards for the Treasurer’s Fiscal Procedure No. 08-01 Merchant Debit and Credit Card Receipts).  The mobile card reader and payment application solution must also be obtained through the Treasurer’s Office. Use of any other mobile reader or payment application in conjunction with taking payments on behalf of the University is prohibited. 

University-owned mobile payment devices can only be used for the purpose of collecting payments by credit card. The only applications that can be installed on the mobile device are (1) those needed to run the device reader and the mobile device payment solution application, and (2) those designed to combat the threat of viruses and/or malware. No other applications may be used on the device including email, social networking sites, or the internet. The University-owned device should not be used for texting, phone calls or other communication.

The University-owned device must be set up to follow strong password policies (biometrics or complex passwords and all default vendor passwords must be changed) and the auto-locking mechanism must be turned on. Employees are restricted from using the camera on the University-owned device to take pictures of any cardholder or payment processing information. The device and application must adhere to any patch management or system upgrades, as well as be protected by anti-virus and anti-malware solutions. Merchants are restricted from making any configuration changes to the University-owned device.

Tracking programs (i.e., find iPhone) must be utilized at all times in the event that the University-owned mobile device is lost or stolen. If able, the University-owned device should enable full disk encryption to prevent users from disabling device level authentication and to add additional protection in the event of theft or loss of the device. 

The University-Owned device must be logged (serial number, model number, operating system), and maintained by the Campus IT or other team responsible for ensuring that the device has the proper patch management.  Campuses are responsible for installing and regularly updating the latest anti-malware and software. Campuses may also consider application wrapping, which can be employed with an MDM (Mobile Device Management) solution to prevent and/or remove malicious software and applications. The University-owned device must be set up in a way that security measures on the mobile device are not circumvented (such as enabling USB debugging if already disabled or jailbreaking/rooting the mobile device). The University-owned device should be monitored to ensure that device configurations have remained secure. 

To further secure cardholder information, the University-owned device used for payment acceptance with an approved reader may only be set up to perform a CREDIT function; the merchant may not issue refunds on the mobile device (those will be handled by the Treasurer’s office as with other refunds). PIN numbers may not be entered directly into the mobile device.

The card reader will be assigned to the store that opens the merchant account, and tracked by the Treasurer’s Office in the same manner as other POS stand- alone devices. This separation of device and reader when not in use will help mitigate the risk of improper use or loss of data and ensure that only authorized users have access to collect mobile payments.

Merchants are responsible for all costs associated with the purchase/rental of mobile devices, readers, payment software, encryption software, anti-malware, MDM, or any other cost incurred to maintain the device in a PCI Compliant manner.

Employee Best Practices When in Use

Employees should use the same due diligence with the University-owned mobile device as they would a stand-alone POS machine including:

  • The University-owned device and card reader must be secured at all times in a locked secure location when not in use (e.g. locked in a cabinet or under 24 hour surveillance). 
  • All users of mobile devices for payment card acceptance must undergo annual PCI Awareness training prior to being given access to accept credit card payments. 

Section C. Discarding Equipment

Section C. Discarding Equipment

Upon closure of the merchant account or discontinued use of the mobile device, the card reader must be returned to the Treasurer’s office for proper disposal. The University-owned device will be returned to the IT or technology unit that is managing the security of the device for disposal of the University-owned device (removing all tags and business identifiers, and ensure no data is present on the device). 

Section D. Incident Response

Section D. Incident Response

Any University-Owned mobile device and/or card reader that is lost or stolen must be reported to the Treasurer’s Office by use of the PCI Security Incident Report and Breach Notification Form (see form listing below) as soon as detected. 

  • Risk-related Requests Form: Use for requests related to Security Incident, Carding Incident, Skimming Incident, Submitting a PCI Scan, Password Resets or Password Lockouts, Add/Delete User, Cyberkey Update, or New Merchant ID. Please note: This form requires login.

Notification will prompt the Treasurer’s Office to request the reader be disabled and securely, remotely, wiped.

In addition, the e-commerce Representative at the Campus must be notified of the incident and all other department heads or managers that are notified must be listed on the above noted notification form.

Section E. Related Links