EMV Chip&Pin

From Payment Processing Software Library
Revision as of 21:24, 21 September 2015 by Admin (Talk | contribs)

Jump to: navigation, search
This article is part of the
Payment Processing Software Library

Categories

Get it...

Credit Card Software
Download

Install it...

Installation
Upgrade & Migration

Connect to it...

Point Of Sale Integration

Set it up...

Quick Start Guide
Setup
Processor Setup

Licensing

Learn to use it...

Manual & User Guide
Knowledge Base
Frequently Asked Questions
Compliance Guide
Merchant Account Rates
User Interface Guides

Fix it...

Errors & Troubleshooting
Knowledge Base
Corrupted Install Repair

Get Help...

Contact
Processor Support Contacts

More Info ...

Glossary
Articles

See also...

911 Software
Help

CreditLine Payment Processing Software Chip & Pin. This site can also be reached at http://docs.911software.com

Looking for better rates?   Get a Free Credit Card Processing Cost Comparison!

EMV Cost: Compliance vs Non-Compliance

There is much misinformation floating around this topic. We would like to set the facts straight. Many of the common fraud situations are not within the scope of EMV. If a merchant does not go through the PCI compliance procedures and someone has been copying card numbers and info at the business location, then using those cards online, that merchant may still be still liable, chip cards or not.

EMV is not a mandate, a merchant cannot be held liable for anything that is not part of the disputed chargeback revenue.

  • Cost of EMV compliance: $250-$550/terminal
  • Cost of EMV non-compliance: an unknown percentage of your current chargebacks. Example: the merchant has $100/year in chargebacks (clients refusing to pay for the charges). 30% of those chargebacks are due to counterfeit cards, additional 10% of those are due to fraudulent claims by customers that they did not ring up the charge, where in fact they did. Merchant is now responsible for 40% of those chargebacks or $40/year in fraudulent charges.

EMV compliance does NOT protect your business, if someone is stealing legitimate card information from your location and using it somewhere else. In addition, it pays to remember, that EMV liability shift deals with counterfeit cards. People go to the trouble of creating fake cards, so that they can make significant purchases, such as expensive electronics, services and commodities. A night club, where a client may run up thousands of dollars, then refuse the charge is affected by the liability shift to a much greater degree than a grocery store.

EMV Terminals

We will be offering Ingenico IPP320/350 and Ingenico IWL220/250 terminals. The EMV functions of the terminals are universal across all processors. The EMV is not a plug and play functionality. Without our drivers, the pin pads will not function, as designed. In addition, the debit function of the terminals is processor specific, so ordering pin pads need to be done with specific processor in mind, to make sure that the pin pad is debit ready for your processor of choice. The integration and certification is rather difficult and so we will be providing the transparent drivers to our customers. All additional pin pad models would need to go through approval and integration by both ourselves and the processors.

EMV Deadline

EMV Deadling is October 2015.
911 Software intends to deliver EMV compatible interfaces by the deadline. We are engaging all major processors at the moment to obtain the specifications and schedule integration and testing logistics.

Chip & Pin or Chip & Signature?

US is adopting Chip & Signature model which will have no impact on the normal operating procedure. Basically, the card has the chip and the customer supplies the signature, they way it always worked.

Processor EMV Compliance

For the processors that are ready, we will be offering EMV solutions before the October deadline. The limiting factor is the processor readiness, we are going as fast as they allow us. At the moment, it is not clear how all the parties involved will be able to deliver the EMV solutions by the deadline. We are working with all major processors to follow their roadmaps to EMV compliance. Given that the liability shifts not only to the merchant but also to the acquirers, we are on the lookout for temporary waivers, as we have seen with MC Mandate lately.

API and Operational Difference

There is no difference in the API or Operational Procedure. Chip & Signature was designed to have a minimal impact