|
|
EMV Implementation for Acquirers: 10 Questions to Answer When Formulating Your EMV Device Budget and Timeline
What changes need to be made to physical structures to accommodate new devices?
One expense associated with upgrading to new device types is changes that may be needed at brick-and-mortar locations. For example, replacing through-the-wall ATMs may mean remodeling at your branch locations so branches can accommodate terminals with different dimensions. These changes can have a substantial impact on your timeline and budget.
Have we factored in time for board or management approval of related expenses?
When establishing a timeline for your EMV implementation, be sure to include time for financial decision-making by your board or management. Purchasing new equipment, making brick-and-mortar changes, hiring trainers or consultants, evaluating new vendor agreements or service contracts—these and many EMV-related costs will require board or management approval, which may in turn require review by committee, or extended research and reporting. These potentially time-consuming decisions need to be accommodated in your EMV project timeline.
Will we offer the same transaction set to chip card users that we currently offer to magnetic stripe card users?
Linked to your choices about the devices that your institution will employ is the decision about the transactions those devices will support. Be aware that there will very likely be changes to ATM/POS loads and device configuration to support EMV. The nature and complexity of the changes will depend on the features and functions that will be offered at the devices.
Has my vendor received Level 1 and Level 2 certification from EMVCo for the devices I intend to support? Are they already in use in another network? (Have they been proven in the field?)
Terminal vendors are responsible for working with EMVCo to complete the following certifications for devices:
- Level 1: interface/card reader functions
- Level 2: terminal software application functions
You will also want to verify that these devices and software kernels are in use already so your institution is not in the challenging position of being a beta tester.
Copyright © 1996-2012, Paragon Application Systems
|