Transactional Security Setup Guide Transactional Security is designed to encrypt your consumer s bank cards at the point of swipe or insertion and provide your Eagle system a token that can be used as a regular bank card number. This type of security not only helps prevent hackers from stealing any useful bank card numbers from your Eagle system, but allows you the same flexibility to process bank cards for credits, voids or returns. And enabling Transactional Security not only adds security to your system, it also has the effect of categorizing you as a Level C merchant, thereby reducing by nearly 200 the number of questions you are currently required to answer for your quarterly Payment Card Industry (PCI) Self-Assessment Questionnaire (SAQ)! The instructions to turn on Transactional Security for all your pin pads and tokenize or truncate any bank card number on Eagle can be found in this guide. We have provided Step By Step Instructions as well as links to additional Online Help and Training on Demand resources. Should you determine you need additional assistance, please contact your LPS. Before You Get Started: Following are the requirements and prerequisites for using Transactional Security: Eagle Licensing must activate option 1345 "Point to Point Encryption on system" in Options Configuration Your Eagle must be running Release 25 or higher You must be using the Epicor Payment Gateway You must be using Ingenico isc250 pin pads You must be processing payment cards on the Epicor Gateway with one of the following: FDMS Global Chase Paymentech RBS Worldpay (Available in March 2016) EPX Additional Training: Setup Instruction and Tokenization Utility Instructions can be found in Online Help and Training on Demand: Online/cloud help: http://help.eaglesoa.com/25/en-n-eagle/paymt_card_proc/transact_secur/transact_secur_ovr.htm Training on Demand: http://ondemand.epicor.com/cws/lms/catalog/viewcourse.do?courseuid=1851 Retailers will need to have TOD log in or isupport log in credentials to access this TOD video Step 1: Quick Recall Bankcard Data Before you implement Transactional Security, you have a choice to make on old bankcard numbers stored in Quick Recall which will not be tokenized or encrypted. 1. You can leave these bankcard numbers as is and as you run Transactional Security these numbers will be removed per Option 311 Days to store credit card numbers in Quick Recall Benefit, you will have these numbers to use for credits, voids, refunds and re charging, but you will still have bankcard numbers that can be viewed in your system. 2. You can truncate all the bankcard numbers in Quick Recall. Benefit, you will remove all actual bankcards numbers from your system, but you will not be able to pull up these older bankcard numbers for credits, voids, refund and re charging.
To truncate all bankcard numbers in Quick Recall, follow these steps: A. To run QRCCC, go to the Eagle Browser under Utilities, click Osprey. In the Osprey Window type QRCCC. B. In the QRCCC screen, choose A to Truncate on the top action and choose E to Execute in the bottom action and hit ENTER. C. Important After this step, all previous bankcard numbers will not be able to be seen or use the truncated number to issue credit, voids or returns. D. You will then receive a summary screen of the records truncated.
Step 2: Setup for Transactional Security You must download RBA 12.01 or higher from Device Configuration to the isc250 pin pad. WARNING: This download can take 45 minutes per pin pad if you are not yet on RBA 3.00. At each terminal with an ISC250 attached, do the following: A. Open Eagle Browser B. Click "Utilities" in the left pane C. Click "Device Configuration" D. Double Click on the line where "Credit/Debit Pad" is listed
E. In the grid, click on the line where "ISC250 RBA 12 or higher" is listed F. Click "Download" G. Wait until it is finished H. Go back to the Credit/Debit Pad screen and click Options
I. Choose Transactional Security (P2PE) from the Device Configuration options menu for the isc250 pin pad and click OK J. Repeat these steps for all terminals with an ISC250 attached. Step 3: Tokenize Bankcards in Customers Maintenance (MCR): Setup If you have option 3565 Keep customer credit cards on system set to B or C, you can follow the instructions below to tokenize those cards. A. Open Customer Maintenance (MCR) B. Click the Go to button or (Ctrl+G) on the keyboard
C. Select option A or Credit Card D. Click Action at the top of that window
E. Click Convert Stored Cards to Tokens F. Click Yes on the confirmation screen and the process will begin Step 4: Purging other credit card data in Eagle: Setup There is one other area that store bankcards the need to be purged if you want to remove all credit card data from you system. Protobase file If you want to remove all bankcards from Eagle, you will need to purge the Protobase files, which will require an SR into Advice line to assist with this.