EMV

On this page:

Introduction

EMV (for Europay-MasterCard-Visa) is a global standard supporting the use of chip cards (ICC’s, “smart cards”) for card present debit and credit transactions.

Simplify supports EMV processing, both contact and contactless, for the following Tran Types:

• Auth Only (01)
• Sale (02)
• Return (09)

Based on settings, each supported Transaction Type can be processed as either EMV or swiped. Please contact your Elavon representative for configuration setting.

When the POS sends a request to Simplify, it must populate the fields required to process the transaction. For in depth information on message requirements for EMV, see the Fusebox Integration Guide under EMV.

Simplify will attempt to process a transaction as EMV when the chip reader successfully communicates with the chip to obtain card data, and EMV processing is enabled for the card type and transaction type.

EMV processing is largely transparent to the POS, with the exception of receipt printing. Additional Status Message codes are used for EMV processing; see under Simplify-Controlled Field Definitions.

Contactless EMV is supported using rules similar to those used for contact EMV. Contactless EMV is enabled separately from contact; please contact your Elavon representative if you would like to enable contactless EMV. Simplify can also be configured to process contactless transactions using MSD emulation.

EMV Receipt Printing

EMV rules require the printing of additional data on the receipt for contact and contactless EMV transactions. The fields that must be printed will vary by TPP (Acquirer) and transaction outcome.

The response message from Simplify for an EMV transaction will provide the POS with two ways to print required EMV data:

• The Fusebox response includes fields specifically designed to provide receipt data (API 1378 and 1379). Simplify adds chip data to these EMV receipt fields before sending the POS a response.

• For more control over printing, the print string can be built by the POS from individual data fields in the response, where each field contains data for one EMV tag.

See also:

• Fields 1378 and 1379 in the sample Sale message below for examples of EMV receipt fields.
• Just below for a list of commonly used tags.
• The Fusebox Integration Guide under EMV Receipts for more information.

EMV Tags

EMV tags are typically present in the response to the POS in the following fields. (This is a generic list; specific transactions may omit some of these tags or include others not shown below.) For more information on EMV tags, see the Fusebox Integration Guide under EMV API Fields.

1376,0000000000000000420142045E031F00

Sample EMV Sale Message

The POS request and Simplify response (approved) for an EMV Sale transaction are shown below. Note concerning this sample:

• Additional fields, not shown in the samples, may also be sent to the POS for EMV.
• Descriptions are only given for response fields added to support EMV.
• For purposes of reference, EMV tag numbers have been noted for potential EMV receipt fields.

Request

Note: the POS request to Simplify does not require modification for EMV.

Response (Approved)

1376,0000000000000000410342031E031F02

1378,1327|Label Application: ;1300|TC:;1307|TVR: ;1325|AID: ;

1379,1327|Label Application:;1300|AAC: ;1307|TVR: ;1325|AID: ;