Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Endpoint

8/15/2016
05:00 PM
Dark Reading
Dark Reading
Products and Releases
50%
50%

US Payments Forum Publishes Update to Payment Networks Minimum Requirements for US EMV Chip Deployment

PRINCETON JUNCTION, N.J., August 11, 2016 – As U.S. issuers, merchants, acquirers and processors continue their migrations to EMV chip technology for more secure payments, many stakeholders may ask: “What is the least complex way to deploy chip for my organization?” To help merchants and acquirers develop their strategies for implementation, payment network members of the U.S. Payments Forum (formerly the EMV Migration Forum) have updated the guide outlining their minimum requirements for chip deployment, including changes to incorporate requirements for the recently announced faster EMV solutions from American Express, Discover, MasterCard and Visa.

The EMV Minimum Requirements Matrix, an easy-to-use Excel document, can be downloaded at http://www.emv-connection.com/minimum-emv-chip-card-and-terminal-requirements-u-s/.  

The EMV Minimum Requirements Matrix is intended for U.S. issuers, merchants, acquirers, processors and vendors who are planning deployments of EMV chip programs in the U.S. Its primary goal is to help stakeholders understand the minimum requirements of chip deployment for the payment networks reflected in the document. The document provides a tool for stakeholders to use as a baseline from which they can work with their partners to determine their best strategy to meet implementation requirements.

“Having the most current minimum requirements for chip implementation compiled in one place provides a starting point for merchants and acquirers in their chip deployments, whether they plan to implement all of the features or choose a simpler deployment such as the new faster EMV specifications,” said Randy Vanderhoof, director of the U.S. Payments Forum. “This resource is just one example of how the U.S. Payments Forum and its members will continue to provide guidance on the most critical aspects of the chip migration.”

The matrix focuses on the minimum card and terminal requirements for payment networks Accel, American Express, Armed Forces Financial Network (AFFN), China UnionPay, Discover, Jeanie, MasterCard, NYCE, PULSE, SHAZAM, STAR and Visa for the U.S. market. These participants have documented their respective minimum card and terminal configurations for EMV compliance. While the document addresses minimum requirements, decisions regarding deployment of chip technology will differ by stakeholder and involve a balancing of considerations, such as business needs and preferences, deployment timing, complexity and associated initial and future costs.

In addition to the EMV Minimum Requirements Matrix, the U.S. Payments Forum has a variety of resources for all stakeholders across the payments industry that are interested in furthering their education and understanding of EMV chip technology in the U.S. Resources including the infographic, “EMV Chip Cards: The Future of Payments,” the “EMV 101: Fundamentals of EMV Chip Payments” webinar and the EMV Connection Press Room are available at www.emv-connection.com.

 

About the U.S. Payments Forum
The U.S. Payments Forum, formerly the EMV Migration Forum, is a cross-industry body focused on supporting the introduction and implementation of new and emerging technologies that protect the security of, and enhance opportunities for payment transactions within the U.S. The Forum is the only non-profit organization whose membership includes the whole payments ecosystem, ensuring that all stakeholders have the opportunity to coordinate, cooperate on, and have a voice in the future of the U.S. payments industry.

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
Why Cyber-Risk Is a C-Suite Issue
Marc Wilczek, Digital Strategist & CIO Advisor,  11/12/2019
DevSecOps: The Answer to the Cloud Security Skills Gap
Lamont Orange, Chief Information Security Officer at Netskope,  11/15/2019
Attackers' Costs Increasing as Businesses Focus on Security
Robert Lemos, Contributing Writer,  11/15/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Navigating the Deluge of Security Data
In this Tech Digest, Dark Reading shares the experiences of some top security practitioners as they navigate volumes of security data. We examine some examples of how enterprises can cull this data to find the clues they need.
Flash Poll
Rethinking Enterprise Data Defense
Rethinking Enterprise Data Defense
Frustrated with recurring intrusions and breaches, cybersecurity professionals are questioning some of the industrys conventional wisdom. Heres a look at what theyre thinking about.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-19040
PUBLISHED: 2019-11-17
KairosDB through 1.2.2 has XSS in view.html because of showErrorMessage in js/graph.js, as demonstrated by view.html?q= with a '"sampling":{"value":"<script>' substring.
CVE-2019-19041
PUBLISHED: 2019-11-17
An issue was discovered in Xorux Lpar2RRD 6.11 and Stor2RRD 2.61, as distributed in Xorux 2.41. They do not correctly verify the integrity of an upgrade package before processing it. As a result, official upgrade packages can be modified to inject an arbitrary Bash script that will be executed by th...
CVE-2019-19012
PUBLISHED: 2019-11-17
An integer overflow in the search_in_range function in regexec.c in Oniguruma 6.x before 6.9.4_rc2 leads to an out-of-bounds read, in which the offset of this read is under the control of an attacker. (This only affects the 32-bit compiled version). Remote attackers can cause a denial-of-service or ...
CVE-2019-19022
PUBLISHED: 2019-11-17
iTerm2 through 3.3.6 has potentially insufficient documentation about the presence of search history in com.googlecode.iterm2.plist, which might allow remote attackers to obtain sensitive information, as demonstrated by searching for the NoSyncSearchHistory string in .plist files within public Git r...
CVE-2019-19035
PUBLISHED: 2019-11-17
jhead 3.03 is affected by: heap-based buffer over-read. The impact is: Denial of service. The component is: ReadJpegSections and process_SOFn in jpgfile.c. The attack vector is: Open a specially crafted JPEG file.