• What is EMV or chip technology?
• Does EMV chip technology apply to e-commerce or mail order/telephone order (MOTO) transactions?
• Why do I need to pay attention to EMV chip technology?
• Do I bear the liability for fraudulent transactions if I don’t use an EMV chip capable device?
• Do the liability shift changes apply to e-commerce, mail order/telephone order (MOTO), contactless or mobile Near Field Communication (NFC) transactions?
• Am I required to update my point of sale to accept EMV chip transactions?
• What do I need to do to support EMV chip technology?
• What is the In-Person SDK and why should I use it?
• When will the Authorize.Net In-Person SDK be available?
• Will I need to make any software/development changes?
• What is the cost to change over to the new EMV chip technology?
• Will the Authorize.Net mPOS mobile application and Virtual Point of Sale (VPOS) support EMV chip technology?
• Will Authorize.Net provide EMV chip-enabled devices for use with VPOS or the mPOS app?
• Does my processor support EMV or Swiped Transactions?
• How do I find out which processor I am using?
• Is there developer documentation available?
• Does Authorize.Net currently support Near Field Communication (NFC) payments?
• Where can I get more information on EMV chip technology?

Q: What is EMV or chip technology?

A: EMV chip technology is becoming the global standard for more secure Card Present (CP) credit card and debit card payments. Named after its original developers (Europay, MasterCard and Visa), this smart chip technology generates a unique, one-time code every time it's used in-store at a chip-activated terminal. This feature is virtually impossible to duplicate in counterfeit cards, helping to reduce in-store fraud.

The technology may also be referred to as: "chip and PIN," "chip and signature," or "chip and choice."

Back to Top

Q: Does EMV chip technology apply to e-commerce or mail order/telephone order (MOTO) transactions?

A: No. EMV chip only applies to card present (contact) chip-enabled card transactions at the physical point of sale.

Back to Top

Q: Why do I need to pay attention to EMV chip technology?

A: Effective October 1, 2015, payment network rules on certain types of fraudulent transactions shifted so that merchants now may bear the liability for counterfeit fraud unless an EMV chip device is used. To protect against this potential liability shift, merchants are encouraged to adopt EMV chip technology at the point of sale.

Back to Top

Q: Do I bear the liability for fraudulent transactions if I don’t use an EMV chip capable device?

A: Yes. If a fraudster uses a counterfeit of a card that is EMV chip-enabled, you will be liable for the loss if the transaction was not processed through an EMV chip-enabled
device. However, if a fraudulent EMV chip card is processed through an EMV chip-enabled device, the issuers will continue to be liable for that loss.

Back to Top

Q: Do the liability shift changes apply to e-commerce, mail order/telephone order (MOTO), contactless or mobile Near Field Communication (NFC) transactions?

A: No. The EMV chip liability shift only applies to card present (contact) EMV chip-enabled card transactions at the physical point of sale.

Back to Top

Q: Am I required to update my point of sale to accept EMV chip transactions?

A: It is not a requirement to update your hardware to support EMV chip transactions. However, if you do not want to be liable for counterfeit transactions processed in person, then you will need to support EMV chip technology. For more information on liability coverages, please contact your Merchant Service Provider (MSP).

Please note, not all customers have EMV chip-enabled cards. You still need to be able to process the traditional magnetic stripe cards as well. The liability for fraud on magnetic stripe only cards has not changed.

Back to Top

Q: What do I need to do to support EMV chip technology?

A: You need to purchase an Authorize.Net-supported, EMV chip-compatible card reader to use with the Authorize.Net In-Person SDK, mPOS mobile application or Virtual Point of Sale (VPOS) application.

Back to Top

Q: What is the In-Person SDK and why should I use it?

A: In order to accept EMV chip transactions, your payment solution and every EMV chip device you use must be certified with each of the card brands (Visa, MasterCard, etc.).

To help you accept EMV chip cards quickly and easily, we created the Authorize.Net In-Person SDK (software development kit), which is the software that communicates the customer’s chip information from the EMV chip reader to Authorize.Net, then back to the EMV chip reader. The In-Person SDK has already been certified with the card brands for use with an Authorize.Net-supported, EMV chip-compatible card reader, allowing you to accept EMV chip transactions on a supported processor.

Back to Top

Q: When will the Authorize.Net In-Person SDK be available?

A: The In-Person SDK is available now for iOS, Android and Windows, but is only available on supported processors. Please see the schedule below for estimated support timelines.

Developers can begin using the In-Person SDK, but will not be able to process live EMV chip transactions until processor support is available.

Back to Top

Q: Will I need to make any software/development changes?

A: If you are using our mPOS application, you will need to upgrade to the latest version available in the App Store or on Google Play and purchase an Authorize.Net-supported, EMV chip-compatible reader available here.

If you are connecting to Authorize.Net through a non-mPOS payment solution, then you will need to update your solution to add support for Authorize.Net's new In-Person SDK, available for iOS, Android or Windows, and purchase an Authorize.Net-supported, EMV chip-compatible reader available here.

Back to Top

Q: What is the cost to change over to the new EMV chip technology?

A: You can purchase Authorize.Net-supported, EMV chip-compatible card readers available here.

Back to Top

Q: Will the Authorize.Net mPOS mobile application and Virtual Point of Sale (VPOS) support EMV chip technology?

A: Yes. The mPOS mobile application and new Virtual Point of Sale (VPOS) application both support EMV chip payments for merchants using FDC Nashville, TSYS, or NAB EPX as their processor. Additional processor support will be added on an ongoing basis. Please see the schedule below for estimated timelines.

EMV chip support for VPOS is now available for merchants that upgrade to the new version at https://vpos2.authorize.net.

Back to Top

Q: Will Authorize.Net provide EMV chip-enabled devices for use with VPOS or the mPOS app?

A: Yes, Authorize.Net-supported, EMV chip-compatible card readers are available here.

EMV chip support for VPOS is now available for merchants that upgrade to the new version at https://vpos2.authorize.net.

Back to Top

Q: Does my processor support EMV or Swiped transactions?

A: The following table outlines if your processor will support EMV chip or Swiped transactions using the Authorize.Net In-Person SDK or mPOS/VPOS mobile applications. 
 

Back to Top

Q: How do I find out which processor I am using?

1. Log into the Merchant Interface. 
2. Click Account from the main toolbar.
3. Click Merchant Profile from the menu on the left. 
4. Under the Payment Methods section, the Processor name will be listed.

Back to Top

Q: Is there developer documentation available?

A: Yes, the In-Person SDK has updated guides for iOS, Android and Windows.

Back to Top

Q: Does Authorize.Net currently support Near Field Communication (NFC) payments?

A: At this time, we do not support NFC (contactless) transactions. As we determine our plan for NFC support, we will provide more information.

Back to Top

Q: Where can I get more information on EMV chip technology?

A: Visa provides several valuable resources to learn more:

A website dedicated to EMV chip technology at http://www.visachip.com

The Visa Chip Bytes webcasts at http://www.visachip.com/visachipbytes

The Visa U.S. Merchant EMV Chip Acceptance and Contactless Guide – 10 Steps to Planning Chip Implementation for Contact and Contactless Transactions.

EMVCo provides additional resources at http://www.emvco.com.

Back to Top