POS Data Code

The Point of Sale (POS) Data Code and POS Entry Mode (PEM) are required input values to issuers or some Third Party Processors (TPPs) based on Card Association requirements. The data informs the issuers about the POS environment and capabilities.

Due to enhanced terminal configurations and payment security schemes such as EMV and digital payments (e.g. consumer digital tokens / wallets), Elavon requires this data to be sent in all inbound Authorization Only (01), Sale (02) and Refund (09) transactions for credit and debit transactions for all industries. If you are using Elavon’s Simplify product, this field is being set properly for you.

For Magstripe Read transactions processing as store and forwarded transactions via the stand-in response supplied by Simplify to the POS/PMS: the POS/PMS should capture the POS Data Code “as is” from the stand-in response from Simplify and forward them the same directly to Fusebox, or can be processed through Simplify when connectivity has been restored.

This page details the valid components for field 0047 and values for field 0054.

API Field 0047

POS Data Code field (0047) is alphanumeric with a maximum size of 29. It contains the POS Data Code values described in the following tables which Fusebox translates for the TPPs and Card Associations. Each Association has different codes representing the same or similar values and these values are in different orders. Below is Elavon’s generic set of values for each subfield. The TPP and Card Association translation is performed in the Fusebox TPP Interface layer.

There are currently 14 defined components to the POS Data Code, with the 15th being “Reserved for Future Use” (RFU). Each character represents a positional value. Each character element is delimited with the delimiter “;”, except for the last entry.

Example: 0047,C;1;1;1;0;1;6;5;4;1;3;C;0;4

note

In some cases, the card brands do not have a full listing of all capabilities; they want you to use the highest capability you support and assume if you support that, then you support lower capabilities as well.

47.1 - POS Device Capability Indicator

  • Usage: Card-entry capability static throughout the certification. Primary consideration: use the highest capability and closest match. The following list is in highest capability order; stop at the first valid case as you go down the list.

EMV Card Present Capabilities

ICC Contactless

  • Field Value: M
  • Usage: If the terminal is capable of ICC contactless as its highest capability. This inherits lesser capabilities.

ICC Contact and Contactless capability

  • Field Value: H
  • Usage: If the terminal is capable of ICC contact and non ICC contactless mag.

ICC Contact, Magnetic stripe, and Keyed capability

  • Field Value: C
  • Usage: If the terminal is capable of ICC contact, Mag, keyed.

ICC Contact Contact and Magnetic strip capability

  • Field Value: D
  • Usage: If the terminal is capable of ICC contact, Mag.

ICC Contact and key entry capability

  • Field Value: E
  • Usage: If the terminal is capable of ICC contact, keyed.

ICC Contact

  • Field Value: 5
  • Usage: If the terminal is capable of ICC contact

Non EMV Card Present Capabilities

Magnetic via contactless

  • Field Value: A
  • Usage: If the terminal is capable of Contactless Mag.

Magnetic stripe reader and key entry capability

  • Field Value: B
  • Usage: If the terminal is capable of Mag and Keyed.

Magnetic stripe reader capability

  • Field Value: 2
  • Usage: If the terminal is capable of Mag only.

Magnetic stripe signature capture

  • Field Value: X
  • Usage: If the terminal is capable of Mag and signature capture.

Keyed Entry only capability

  • Field Value: 6
  • Usage: If the terminal/POS is Key entry only, (i.e. PC with a keyboard).

MOTO/ECOM Terminal/POS Capabilities

Secure Electronic Transaction (SET) with certificate

  • Field Value: 1
  • Usage: POS-terminal that is capable of 3D secure eCommerce transactions.

Channel-encrypted Electronic Commerce Transaction (SSL)

  • Field Value: K
  • Used for POS-terminal that is capable of standard eCommerce, non-3D secure transactions.

Manual entered account, no terminal

  • Field Value: 1
  • Usage: Used for POS-terminal that is capable of for Mail Order Telephone.

47.2 - Cardholder Authentication Capability

  • This value normally does not change for the duration of the payment application certification. With a terminal, it reflects hardware capability.

No electronic authentication capability

  • Field Value: 0
  • Usage: Terminal is NOT PIN capable.

PIN authentication capability

  • Field Value: 1
  • Usage: Terminal is PIN capable.

Other

  • Field Value: 6
  • Usage: This value is not commonly used and mainly exists for special or legacy support.

47.3 - Terminal Card Capture Capability

  • Capability is usually static for the life of the certification. Can the card be Retained?

No capture capaility

  • Field Value: 0
  • Usage: If the terminal is is not able to mechanically retain a card.

Card capture capability

  • Field Value: 1
  • Usage: If the terminal is able to mechanically retain a card.

47.4 - Terminal Operating / Location Environment

  • Location of the Terminal.

No Terminal

No terminal Used

  • Field Value: 0
  • Usage: Voice auth or VRU uses.

On Premise

Terminal is On Merchant premises

  • Field Value: 1
  • Usage: Standard choice for Retail, Restaurant, Lodging, or Travel.

Terminal is On Card Holder premises

  • Field Value: 5
  • Usage: Unattended terminal, on card holder premises (at Home).

Terminal is On Merchant premise; mPOS (Mobile POS)

  • Field Value: P
  • Usage: Used to identify a Mobile POS terminal.

Off Premise

Terminal is Off Merchant premises

  • Field Value: 3
  • Usage: For terminals used Off Merchant premise. (Vending)

Terminal is Off Card Holder premises

  • Field Value: 6
  • Usage: Unattended terminal, off card holder premises (not at Home).

Terminal is Off Merchant premises; mPOS (Mobile POS)

  • Field Value: M
  • Usage: Used to identify a Mobile POS terminal used Off Merchants premises. (Portable device, trade shows, service calls, taxis, etc.)

Card Holder Device: PC, PDA, Smartphone

Cardholder owned device, off Merchant Premise

  • Field Value: Q
  • Usage: eCommerce - In-app off Merchant Premise (Anywhere other than Merchants premise).

Cardholder owned device, on Merchant Premise

  • Field Value: R
  • Usage: eCommerce - In-app off Merchant Premise (Anywhere other than Merchants premise).

47.5 - Cardholder Present Indicator

  • Indicate if the card holder was present for the immediate transaction event.

Cardholder present

  • Field Value: 0
  • Usage: If the cardholder was present during the transaction.

Cardholder Not Present

Cardholder not present (reason not specified)

  • Field Value: 1
  • Usage: If the Card holder was not present during the transaction and the reason was unspecified.

Cardholder not present, mail order

  • Field Value: 2
  • Usage: Used with MOTO: mail order use cases.

Cardholder not present, telephone order

  • Field Value: 3
  • Usage: Used with MOTO: mail order use cases.

Cardholder not present, Industry Practice

  • Field Value: 4
  • Usage: Used in Lodging and Auto Rental Industries where the card holder is not present by Industry Practice.
  • Examples: Lodging Incremental Authorization, Delayed Charge, and No Show transactions.

Cardholder not present, electronic transaction

  • Field Value: 5
  • Usage: Used for eCommerce.

Cardholder not present, Standing Authorization - Unscheduled

  • Field Value: A
  • Usage: Used in MOTO and eCommerce for standing authorizations that are not performed on a scheduled basis.
    • Examples: Unscheduled MOTO and eCommerce Transactions.

Cardholder not present, Standing Authorization – Recurring or Installment

  • Field Value: 9
  • Usage: Used in MOTO and eCommerce for standing authorizations that are performed on a scheduled basis.
    • Examples: MOTO and eCommerce Installment/Recurring Transactions.

47.6 - Card Present Indicator

  • Indicates whether the card was present for the transaction event.

Cardholder not present

  • Field Value: 0
  • Usage: Card was not physically available.

Cardholder is present

  • Field Value: 1
  • Usage: Card was physically available.

Contactless (NFC Chip / NFC mag)

  • Field Value: X
  • Usage: Used for NFC Mag or chip presented card data, includes consumer device sourced NFC data like Token or ApplePay.

Digital Wallet In-app

  • Field Value: Z
  • Usage: Future-use for card data presented via Digital wallet in eCommerce transactions (may include remote chip events over eCommerce).

47.7 - Card Data Input Mode Indicator

  • Field Value: G
  • Usage: Identifies how card data was sent.

EMV Card present items

ICC Contactless

  • Field Value: M
  • Usage: Contactless M/Chip or Visa Smart Card read.

ICC Contact

  • Field Value: 5
  • Usage: Integrated circuit card read.

Technical fallback to Contact ICC

  • Field Value: N
  • Usage: Fall back from NFC ICC capable card to Contact Chip read.

Technical fallback to Mag swipe

  • Field Value: 9
  • Usage: Fall back from ICC capable card to Mag-swipe.

Empty candidate list fallback

  • Field Value: P
  • Usage: Fall back from ICC to Mag Swipe when EMV Candidate list has no match.

Non EMV Card present

Contactless Magnetic stripe

  • Field Value: A
  • Usage: Contactless magnetic stripe read.

Magnetic Stripe read

  • Field Value: 2
  • Usage: Use when classic physical contact Mag swipe read (MSR event).

Magnetic stripe with signature capture

  • Field Value: X
  • Usage: Used when the terminal supports digital signature capture and the transaction is Mag swipe with digital signature capture.

Key Entry

  • Field Value: 6
  • Usage: Manual/Key Entry at the terminal.

MOTO / eCommerce Card not present capabilities

Manual, no terminal

  • Field Value: 1
  • Usage: No terminal / Manual entry of the card data. Common for phone VRU, or Mail order.

eCommerce: R - Pan Via Remote Chip

  • Field Value: R
  • Usage: Future use with remote chip transactions.

Channel-encrypted Electronic Commerce Transaction (SSL)

  • Field Value: K
  • Usage: eCommerce transaction over channel-encrypted (SSL) link (non-3D secure).

Secure Electronic Transaction (SET) with certificate

  • Field Value: I
  • Usage: eCommerce transaction over channel-encrypted (SSL) link (3D secure with cardholder certificate).

Secure Electronic Transaction (SET) with no certificate

  • Field Value: J
  • Usage: eCommerce transaction over channel-encrypted (SSL) link (3D secure with Merchant only certificate).

47.8 - Card Data Authentication Mode Indicator

  • Authentication method used for the transaction event. Recommend using a configuration parameter to set default value for unknown and non-PIN transactions.

Card Data Not authenticated

  • Field Value: 0
  • Usage: Used when there is no Authentication of Card data. Example, unattended and without PIN.

PIN

  • Field Value: 1
  • Usage: Used when this is a PIN based transaction.

Attendant verification of Card signature

  • Field Value: 5
  • Usage: Traditionally used in card-present environment where the signature is verified by the attendant.

Attendant verification of other ID

  • Field Value: 6
  • Usage: Used when the attendant verifies ID using some other form of card identification.

Electronic ticket environment

  • Field Value: S
  • Usage: RFU - Reserved for future use in electronic ticket vending.

47.9 - Cardholder Authentication Mode Indicator

  • Method used to verify the cardholder for this transaction. Recommend using a configuration parameter to set default value for unknown and non-PIN transactions.

Card Holder Not authenticated (Failed or PIN bypass)

  • Field Value: 0
  • Usage: Used when the Terminal supports and initiates a PIN bypass to complete the transaction.

Card holder PIN authenticated offline

  • Field Value: 1
  • Usage: Used when verification PIN is done offline between the Terminal PIN entry and card ICC.

Card holder PIN authenticated online

  • Field Value: 3
  • Usage: Used when verification PIN is done online between the Terminal PIN entry and the processing network. Common for swiped debit PIN.

Card holder authenticated by merchant (signature)

  • Field Value: 4
  • Usage: Used when attendant verifies the cardholder signature. Default for attended terminals when PIN not used.

Other

  • Field Value: 5
  • Usage: This value is not commonly used and mainly exists for legacy support. Default for unattended terminals when PIN not used or new authentication techniques, such as biometrics are used.

47.10 - Card Data Output Capability Indicator

  • Used to identify the terminal’s capability to update a card.

None

  • Field Value: 1
  • Usage: Typical for NON-EMV devices, or devices that cannot update a card, like NFC-only readers.

Integrated Circuit Card update capability

  • Field Value: 3
  • Usage: Used for Any EMV device capable of updating the Chip script data.

47.11 - Terminal Data Output Capability Indicator

  • Used to identify the terminal’s output capability.

No terminal printing or display ability

  • Field Value: 1
  • Usage: Common for Mail or phone order systems.

Terminal Printing ability

  • Field Value: 2
  • Usage: Common for swipe/tap only terminals.

Terminal Display ability

  • Field Value: 3
  • Usage: Common for interactive terminals that can display amounts and prompts for things like PIN. Also eCommerce websites.

Terminal Printing and Display ability

  • Field Value: 4
  • Usage: Common for interactive terminals that can display amounts and prompts for things like PIN. Also print receipts.

47.12 - PIN Capture Capability Indicator

  • Used to identify the Terminals PIN Capture Capability.

No PIN capture capability

  • Field Value: 0
  • Usage: Use when the Terminal has no PIN pad.

Device PIN capture capability unknown

  • Field Value: 1
  • Usage: This value is not commonly used and mainly exists for special/legacy support.

Device PIN capture capability unknown

  • Field Value: 1
  • Usage: This value is not commonly used and mainly exists for special/legacy support.

4 to 12 characters: [4, 5, 6, 7, 8, 9, A, B, C]

  • Field Value: 4-C
  • Usage: Use one of these values (4 through C) when the Terminal is capable of accepting PIN entries. The value used will represent the maximum length of PIN the terminal is capable of. (e.g. 4 is four bytes, C is 12 bytes).

47.13 - POS Device Attendance Indicator

  • Used to identify if the Terminal is attended or unattended.

Attended Terminal

  • Field Value: 0
  • Usage: Most common option, terminal is attended by an employee.

Unattended Terminal

  • Field Value: 1
  • Usage: Terminal is being certified for unattended use. (e.g. Vending machine or kiosk).

No terminal

  • Field Value: 2
  • Usage: This option is common for MOTO and eCommerce interfaces; used in Back office card on file use, standing auth use.

47.14 - POS Device Terminal Type**

  • Used to identify the type of terminal.

Merchant Register/Terminal

  • Field Value: 4
  • Usage: Most common option for normal terminal certifications.

Transponder (CAT)

  • Field Value: 6
  • Usage: Transponder - Card activated terminal, Kiosk as an example.

Unknown/Unspecified

  • Field Value: 0
  • Usage: Legacy use, there are no expectation to see this option used in a modern certification.

Cardholder-owned device (PC, PDA, SmartPhone)

  • Field Value: 5
  • Usage: RFU-Reserved for future use in in-app/eCommerce.

mPOS device (Merchant Mobile POS Device)

  • Field Value: 9
  • Usage: RFU-Reserved for future use in Merchant Mobile POS.

Secondary Transactions

Secondary transactions also require POS Data Code, such as Incremental Authorizations, Voids (Type 11) and Reversals (Types 76, 61). When the incremental authorization request is generated, the POS data code from the original authorization request should be used with modifications to sub-fields: 47.5 – 47.9 (these fields track entry mode factors but not capabilities). Card Not Present transactions need to modify the dynamic card / cardholder present / not present fields when a token is presented in place of the credit card.

important

If the POS Entry Mode (Field 54) changes from swipe or insert of credit card for EMV, then POS Data Code sub-fields 47.5 to 47.9 will also need to reflect that the card and cardholder are not present.

API Field 0054 - POS Entry Mode

  • Value (000) = Unknown
  • Value (01) = Manual Key
  • Value (04) = OCR Code Read
  • Value (05) = Integrated circuit card read;CVV data reliable (smart card)
  • Value (07) = Contactless; M/Chip or Visa Smart Card read
  • Value (10) = Scanned; MICR/check
  • Value (80) = Chip Card capable; unaltered track data read (used for EMV fall back to swipe)
  • Value (82) = Contactless Mobile Commerce device
  • Value (85) = Internet (not an ISO value)
  • Value (90) = Magnetic Stripe
    CVV/CVC certified, unaltered Track Data (1 or 2) included in Authorization Request. Required to participate in PS/2000 or CPS/200
  • Value (91) = Contactless magnetic stripe read
  • Value (95) = Integrated circuit card read; CVV data unreliable

EMV Impacts

Each merchant terminal defines its MID and TID. Each transaction requires a consistent EMV capability. Each card brand may have unique requirements that will be accounted for when the POS Data Code is accurately presented when processing the transaction.