This article will guide merchants through understanding and processing EMV payments and transactions.

What is EMV or chip technology?

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."

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

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

What is needed to process an EMV Transaction?

1. Authorize.net supports EMV on our processor connection for your Merchant Account.
   • Supported processor list below.
2. Utilize Authorize.net’s Mobile Point of Sale (mPOS) or Virtual Point of Sale (VPOS) applications with a compatible card reader purchased through POS Portal.
   • For more information on mPOS, see: What is the Mobile Point of Sale (mPOS) and how to use it?
   • For more information on VPOS, see: What is the Virtual Point of Sale (VPOS) and how do I sign in, and what to do if I can't?
   • EMV chip-compatible card readers are available with POS Portal.
3. Or a custom-built application using Authorize.net’s EMV SDK and a compatible card reader purchased through POS Portal.
   • The In-Person SDK is available for iOS, Android, and Windows, but is only on supported processors.

EMV or Swipe Processor Support

The following table outlines Authorize.net support of EMV chip or Swiped transactions by processor using the In-Person SDK or mPOS and VPOS applications.

To find the processor connected to your account use the steps below:

1. Sign in to 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.

Identify EMV Transactions in the Merchant Interface

Merchants will see the below additional data in the transaction’s details.

Entry Method - With the addition of EMV support a new field, Entry Method, has been added to the Transaction Details and Merchant/Customer Email Receipts. This new field will show how each credit card transaction was submitted:

Changes to EMV Receipts

Example of an EMV email receipt:

• Merchant Store Identifier (MID)
• Terminal Device Identifier (TID)
• Application Name (e.g. Visa)
• Application PAN (e.g. xxxx1234)
• Card Entry Mode (e.g. Chip Read)
• Transaction Total (e.g. USD$)
• Authorization Mode (e.g. Issuer)
• EMV Tag Data (recommended for all approvals)
• AID – Application Identifier (Tag 4F)
• TVR – Terminal Verification Result (Tag 95)
• IAD – Issuer Application Data (Tag 9F10)
• TSI – Transaction Status Information (Tag 9B)
• ARC – Authorization Response Code (Tag 8A)
• Cardholder Verification (e.g. Signature)

What response codes will be returned on EMV Transactions?

EMV Processing FAQs

• Do I bear the liability for fraudulent transactions if I don’t use an EMV chip capable device?
  • 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.
• Do the liability shift changes apply to e-commerce, mail order/telephone order (MOTO), contactless or mobile Near Field Communication (NFC) transactions?
  • No. The EMV chip liability shift only applies to card present (contact) EMV chip-enabled card transactions at the physical point of sale.
• Am I required to update my point of sale to accept EMV chip transactions?
  • It is not a requirement at this time 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.
• What is Quick Chip for EMV?
  • Quick Chip is available for all processors that support EMV. Quick Chip for EMV accelerates the existing EMV chip checkout process, allowing customers to check out in about two seconds or less using a chip-enabled card.
• What is the In-Person SDK and why should I use it?
  • 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.
  • The In-Person SDK is available for iOS, Android, and Windows, but is only on supported processors.
• Does the EMV SDK support Tips?
  • Within the SDK the merchant/developer has the following options available to them when passing a Tip amount to us:
    • These Tip configurations are available within the SDK:
      • Inperson iOS SDK
      • Inperson Android SDK
      • Declare the Total + Tip amount in one step
      • Perform an Authorize Only transaction, then a Prior Auth Capture with a different total that includes the Total + Tip
      • 3 customizable pre-defined %s
      • No Tip
      • Custom Tip
• Is OTA (Over The Air) updates supported?
  • The EMV SDK supports the ability for the merchant to update their EMV Reader with the latest firmware and Authorize.net configurations. This will be supported with all versions of the SDK.
    • Merchants will have the following options available to them:
      • Check to see if an update is available
      • Update the firmware
      • Update the config
      • Check device information
      • If an update is needed it can take 5-15 minutes to be downloaded and installed.
• Will I need to make any software/development changes?
  • ​​​​​​​If you are using Authorize.net’s mPOS or VPOS application, you should make sure to use the most recent version.
  • If you are connecting to Authorize.net through a non-mPOS or VPOS payment solution, then you will need to update your solution to add support for Authorize.net's In-Person SDK, and purchase an EMV chip-compatible card reader from POS Portal.
• Does Authorize.net support Near Field Communication (NFC) payments?
  • ​​​​​​​​​​​​​​At this time, we do not support NFC (contactless) transactions.