pointOfSaleInformation

The following fields provide point-of-sale information.

pointOfSaleInformation. amexCAPNData

Point-of-sale details for the transaction.
This field enables you to comply with American Express CAPN requirements.
Cybersource
 generates this value, which consists of a series of codes that identify terminal capability, security data, and specific conditions present at the time the transaction occurred. To comply with the CAPN requirements, this value must be included in all subsequent follow-on requests, such as captures and follow-on credits.
When you perform authorizations, captures, and credits through
Cybersource
,
Cybersource
 passes this value from the authorization service to the subsequent services for you. However, when you perform authorizations through
Cybersource
 and perform subsequent services through other financial institutions, you must ensure that requests for captures and credits include this value.
This field is available only for transactions using American Express payment cards on the
American Express Direct
,
Elavon Americas
, and
FDMS South
 processors.
American Express Direct
 and
FDMS South
For forced captures, obtain the value for this field from the authorization response.
For verbal authorizations, you cannot obtain a value for this field, so
Cybersource
 uses a default value.
Cybersource
 generates the value based on these factors:
  • Whether the transaction is an e-commerce transaction.
  • Whether the transaction is a card-present transaction.
  • Whether the payment data is swiped or keyed.

Specifications

  • Data Type:
     String
  • Data Length:
     12

Mapping Information

  • REST API Field:
    pointOfSaleInformation.amexCAPNData
  • SCMP API Fields:
    • auth_pos_data
    • bill_pos_data
  • Simple Order API Fields:
    • ccAuthReply_posData
    • ccCaptureService_posData
pointOfSaleInformation

pointOfSaleInformation. cardholderVerificationMethod

List of cardholder verification methods (CVMs) supported by the terminal.
This field is available only for
Cybersource
 integrations on the
Barclays
 processor.
Possible values:
  • CDCVM
    : Cardholder device CVM—supported only on
    Barclays
  • PIN
  • Signature

Specifications

  • Data Type:
     String
  • Data Length:
     15

Mapping Information

  • REST API Field:
    pointOfSaleInformation.cardholderVerificationMethod[]
  • SCMP API Field:
    terminal_cvm_capabilities_#
  • Simple Order API Field:
    pos_terminalCVMcapabilities_#
pointOfSaleInformation

pointOfSaleInformation. cardPresent

Indicates whether the card is present at the time of the transaction.
Possible values:
  • N
    : Card is not present
  • Y
    : Card is present

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.cardPresent
  • SCMP API Field:
    card_present
  • Simple Order API Field:
    pos_cardPresent
pointOfSaleInformation

pointOfSaleInformation. catLevel

Type of cardholder-activated terminal.
Possible values:
  • 1
    : Automated dispensing machine
  • 2
    : Self-service terminal
  • 3
    : Limited amount terminal
  • 4
    : In-flight commerce (IFC) terminal
  • 5
    : Radio frequency device
  • 6
    : Mobile acceptance terminal
  • 7
    : Electronic cash register
  • 8
    : E-commerce device at your location
  • 9
    : Terminal or cash register that uses a dialup connection to connect to the transaction processing network
Applicable Values for Card-Present Transactions:
  • Chase Paymentech Solutions
    : Only values
    1
    ,
    2
    , and
    3
     are supported.
  • FDC Nashville Global
    : Only values
    7
    ,
    8
    , and
    9
     are supported.
  • GPN
    : Only values
    6
    ,
    7
    ,
    8
    , and
    9
     are supported.
  • JCN Gateway
    : Only values
    6
    ,
    7
    ,
    8
    , and
    9
     are supported.
  • TSYS Acquiring Solutions
    : Only value
    6
     is supported.
  • Visa Platform Connect
    : Values
    1
     through
    6
     are supported, but some acquirers do not support all six values.
Applicable Values for PIN Debit Transactions:
Only values
7
,
8
, and
9
 are supported.

Specifications

  • Data Type:
     Non-negative integer
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.catLevel
  • SCMP API Field:
    cat_level
  • Simple Order API Field:
    pos_catLevel
pointOfSaleInformation

pointOfSaleInformation. deviceId

Value created by the client software that uniquely identifies the POS device.
This value is not sent to the processor. Instead, the value is forwarded to the
Cybersource
 reporting software.
This field is available only for
Cybersource
 integrations.

Specifications

  • Data Type:
     String
  • Data Length:
     32

Mapping Information

  • REST API Field:
    pointOfSaleInformation.deviceId
  • SCMP API Field:
    pos_device_id
  • Simple Order API Field:
    pos_deviceID
pointOfSaleInformation

pointOfSaleInformation. emv.cardholderVerificationMethodUsed

Cardholder verification method (CVM).
This field specifies the method that was used to verify the cardholder's identity.
Possible values:
  • 0
    : No verification
  • 1
    : Signature
  • 2
    : PIN
  • 3
    : Cardholder device CVM (CDCVM)—available only on the
    Barclays
     processor
This field is available only for
Cybersource
 integrations and the
Barclays
 processor.

Specifications

  • Data Type:
     Integer
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.cardholderVerificationMethodUsed
  • SCMP API Field:
    cardholder_verification_method
  • Simple Order API Field:
    ccAuthService_cardholderVerificationMethod
pointOfSaleInformation

pointOfSaleInformation. emv.cardSequenceNumber

Number assigned to a specific card when two or more cards are associated with the same primary account number.
This value enables issuers to distinguish among multiple cards that are linked to the same account. This value can also act as a tracking tool when the issuer reissues cards. When this value is available, it is provided by the chip reader. When the chip reader does not provide this value, do not include this field in your request.

Specifications

  • Data Type:
     String with numbers only
  • Data Length:
    • American Express Direct
      : 2
    • Visa Platform Connect
      : 2
    • Other Processors: 3

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.cardSequenceNumber
  • SCMP API Field:
    emv_request_card_sequence_number
  • Simple Order API Field:
    emvRequest_cardSequenceNumber
pointOfSaleInformation

pointOfSaleInformation. emv.chipValidationResult

Cryptogram validation results returned by the entity or service specified in
pointOfSaleInformation.emv.chipValidationType
.
Possible values:
  • A
    : Application cryptogram is valid, but the application transaction counter (ATC) is outside the allowed range. (A large increase in ATC values can indicate data copying or other fraud.)
  • C
    : Chip validation was completed successfully.
  • E
    : Application cryptogram is valid, but the ATC indicates possible replay fraud.
  • F
    : Format error in the chip data.
  • G
    : Application cryptogram is valid but is not a valid authorization request cryptogram (ARQC).
  • I
    : Application cryptogram is invalid.
  • T
    : Application cryptogram is valid, but terminal verification results (TVR) or card verification results (CVR) are invalid.
  • U
    : Application cryptogram could not be validated because of a technical error.
This field is available only for Mastercard near-field communication (NFC) authorizations that use payment network tokens on the
Visa Platform Connect
 processor.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.chipValidationResult
  • SCMP API Field:
    emv_reply_chip_validation_results
  • Simple Order API Field:
    emvReply_chipValidationResults
pointOfSaleInformation

pointOfSaleInformation. emv.chipValidationType

Entity or service that provided the validation results returned in the
pointOfSaleInformation.emv.chipValidationResult
 field.
Possible values:
  • 02
    : Mastercard pre-validation service. The Mastercard authorization platform validated the cryptogram before the issuer received the authorization request.
  • 03
    : Mastercard stand-in service. The Mastercard authorization platform validated the cryptogram because the issuer was not available.
  • 50
    : Issuer.
  • 90
    : Chip fall-back transaction downgrade process. The chip could not be read.
This field is available only for Mastercard near-field communication (NFC) authorizations that use payment network tokens on the
Visa Platform Connect
 processor.

Specifications

  • Data Type:
     String
  • Data Length:
     2

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.chipValidationType
  • SCMP API Field:
    emv_reply_chip_validation_type
  • Simple Order API Field:
    emvReply_chipValidationType
pointOfSaleInformation

pointOfSaleInformation. emv.fallback

Indicates that a fallback method can be used for authentication.
When a technical problem prevents a successful exchange of information between a chip card and a chip-capable terminal, you can use fallback to swipe the card or key the payment card information into the POS terminal.
Possible values:
  • Y
    : Fallback available
  • N
     (default): Fallback method not available
This field is supported on processors that support EMV fallback transactions.

Specifications

  • Data Type:
     String
  • Data Length:
     5

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.fallback
  • SCMP API Field:
    emv_request_fallback
  • Simple Order API Field:
    emvRequest_fallback
pointOfSaleInformation

pointOfSaleInformation. emv.fallbackCondition

Reason for the EMV fallback transaction.
An EMV fallback transaction occurs when an EMV transaction fails for one of these reasons:
  • Technical failure: the EMV terminal or EMV card cannot read and process chip data.
  • Empty candidate list failure: the EMV terminal does not have any applications in common with the EMV card. EMV terminals are coded to determine whether the terminal and EMV card have any applications in common. EMV terminals provide this information to you.
Possible values:
  • 1
    : Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal either used information from a successful chip read or it was not a chip transaction.
  • 2
    : Transaction was initiated with information from a magnetic stripe, and the previous transaction at the EMV terminal was an EMV fallback transaction because the attempted chip read was unsuccessful.
This field is available only on the
GPN
,
JCN Gateway
, and
Visa Platform Connect
 processors.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.fallbackCondition
  • SCMP API Field:
    emv_request_fallback_condition
  • Simple Order API Field:
    emvRequest_fallbackCondition
pointOfSaleInformation

pointOfSaleInformation. emv.isRepeat

Indicates the authorization is a duplicate authorization request.
When the
issuerInformation.pinRequestIndicator
 field is included in the authorization response message, you must submit a duplicate authorization request that includes the customer's PIN.
This field is available only for Mastercard transactions on the
Visa Platform Connect
 processor.
Possible value:
  • 01
    : Duplicate authorization request

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.isRepeat
  • SCMP API Field:
    emv_request_repeat
  • Simple Order API Field:
    emvRequest_repeat
pointOfSaleInformation

pointOfSaleInformation.emv.tags

EMV data that is transmitted from the chip card to the issuer and from the issuer to the chip card.
The EMV data is in the tag-length-value format and includes chip card tags, terminal tags, and transaction detail tags.
WARNING
These tags contain sensitive information and must not be included in this field:
  • 56: Track 1 equivalent data
  • 57: Track 2 equivalent data
  • 5A: Application PAN
  • 5F20: Cardholder name
  • 5F24: Application expiration date
  • 99: Transaction PIN
  • 9F0B: Cardholder name (extended)
  • 9F1F: Track 1 discretionary data
  • 9F20: Track 2 discretionary data
For contact EMV captures, contact EMV stand-alone credits, and contactless EMV stand-alone credits, you must include these tags in this field.
  • 95: Terminal verification results
  • 9F10: Issuer application data
  • 9F26: Application cryptogram
Merchants that accept contactless transactions that must include the tap-to-phone indicator in tag 9F6E byte 4 bit 8. Possible values:
  • 0
    : Transaction did not originate from a tap-to-phone acceptance device.
  • 1
    : Transaction originated from a tap-to-phone acceptance device.
Acquirers must support the tap-to-phone indicator in the TC 33 capture file location:
  • Record: CP02 TCR0
  • Position: 150
  • Field: Tap-to-Phone Indicator
IMPORTANT
If the original transaction includes EMV tag 55 (FDI Field 55), this tag must be included in follow-on reversal transactions.
JCN Gateway
These tags must be included:
  • 4F: Application identifier
  • 84: Dedicated file name
Visa Platform Connect
 Card-Present Transactions
Include this tag for better interchange rates:
  • 84: Dedicated file name
The value for Tag 84 corresponds to these data in the TC 33 capture file:
  • Record: CP02 TCR0
  • Position: 118-149
  • Field: Dedicated File Name - Application ID (AID)
The TC 33 capture file contains information about the payments and credits that a merchant submits to
Cybersource
. The processor creates the TC 33 capture file at the end of the day and sends it to the merchant’s acquirer. The acquirer uses this information to facilitate end-of-day clearing processing with payment networks.
Include these optional Mastercard integrated-circuit-card‐data EMV tag values in authorization requests:
  • 9F60: Authenticated application data
  • 96: Kernel identifier‐terminal

Specifications

  • Data Type:
     String
  • Data Length:
    • Visa Platform Connect
      : 252
    • Visa Platform Connect
      : 199 bytes for Japan
    • Other processors: 999

Mapping Information

  • REST API Field:
    pointOfSaleInformation.emv.tags
  • SCMP API Field:
    emv_request_combined_tags
  • Simple Order API Field:
    emvRequest_combinedTags
pointOfSaleInformation

pointOfSaleInformation. encryptedKeySerialNumber

Combination of the POS terminal's unique identifier and a transaction counter that is used when decrypting the encrypted PIN.
The entity that injected the PIN encryption keys into the terminal decrypts the encrypted PIN and creates this value.
For all terminals that are using derived unique key per transaction (DUKPT) encryption, this is generated as a single number within the terminal.
This field is supported only for
Cybersource
 integrations and only for processors that support chip and online PIN transactions.

Specifications

  • Data Type:
     String
  • Data Length:
     20

Mapping Information

  • REST API Field:
    pointOfSaleInformation.encryptedKeySerialNumber
  • SCMP API Field:
    pin_data_key_serial_number
  • Simple Order API Field:
    pinDataKeySerialNumber
pointOfSaleInformation

pointOfSaleInformation. encryptedPin

Encrypted PIN data.
This value is provided by the client software that is installed on the POS terminal.
This field is available only for
Cybersource
 integrations and only for processors that support chip and online PIN transactions. In the request, you must encrypt the PIN to send the data. Required for Discover and Diners Club online PIN and ATM transactions.

Specifications

  • Data Type:
     String
  • Data Length:
     16

Mapping Information

  • REST API Field:
    pointOfSaleInformation.encryptedPin
  • SCMP API Field:
    pin_data_encrypted_pin
  • Simple Order API Field:
    pinDataEncryptedPIN
pointOfSaleInformation

pointOfSaleInformation. entryMode

Method of entering payment card information into the POS terminal.
This field is available only on the
FDC Compass
,
OmniPay Direct
, and
Visa Platform Connect
 processors.
Possible values:
  • contact
    : Read from direct contact with chip card.
  • contactless
    : Read from a contactless interface using chip data.
  • keyed
    : Manually keyed into POS terminal.
    OmniPay Direct
    :
    For card-present transactions, this value is not supported.
    For PIN debit transactions, this value is not supported.
  • msd
    : Read from a contactless interface using magnetic stripe data (MSD).
    OmniPay Direct
    :
    For card-present transactions, this value is not supported.
  • swiped
    : Read from payment card magnetic stripe.
The
contact
,
contactless
, and
msd
 values are supported only for EMV transactions.

Specifications

  • Data Type:
     String
  • Data Length:
     11

Mapping Information

  • REST API Field:
    pointOfSaleInformation.entryMode
  • SCMP API Field:
    pos_entry_mode
  • Simple Order API Field:
    pos_entryMode
pointOfSaleInformation

pointOfSaleInformation. isDedicatedHardwareTerminal

Type of mPOS device.
Possible values:
  • 0
    : Dongle
  • 1
    : Phone or tablet
This field is available only for Mastercard transactions on the
Visa Platform Connect
 processor.
The value for this field corresponds to the following data in the TC 33 capture file:
  • Record: CP01 TCR6
  • Position: 141
  • Field: Mastercard mPOS Transaction
The TC 33 capture file contains information about the payments and credits that a merchant submits to
Cybersource
. The processor creates the TC 33 capture file at the end of the day and sends it to the merchant’s acquirer. The acquirer uses this information to facilitate end-of-day clearing processing with payment networks.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.isDedicatedHardwareTerminal
  • SCMP API Field:
    mpos_device_type
  • Simple Order API Field:
    mPOS_deviceType
pointOfSaleInformation

pointOfSaleInformation. laneNumber

Identifier for one of the terminals at your retail location that is used to complete a transaction.
This field is a request and response field. You defined the value for this field in the request message. This value must be printed on the receipt.
This field is available only for Mastercard transactions on the
FDC Nashville Global
 processor.
Use the
pointOfSaleInformation.terminalId
 field to identify the main terminal at your retail location.

Specifications

  • Data Type:
     String
  • Data Length:
     8

Mapping Information

  • REST API Field:
    pointOfSaleInformation.laneNumber
  • SCMP API Field:
    terminal_id_alternate
  • Simple Order API Field:
    pos_terminalIDAlternate
pointOfSaleInformation

pointOfSaleInformation. operatingEnvironment

Operating environment.
This field is available only on the
American Express Direct
 and
Visa Platform Connect
 processors.
Possible values for Mastercard:
  • 2
    : On merchant premises, unattended, or customer terminal. Examples: oil, kiosk, self-checkout, home computer, mobile telephone, personal digital assistant.
    Visa Platform Connect
    :
    Customer terminal is supported only for Mastercard transactions.
  • 4
    : Off merchant premises, unattended, or customer terminal. Examples: vending machine, mobile telephone, personal digital assistant.
    Visa Platform Connect
    :
    Customer terminal is supported only for Mastercard transactions.
Possible values for all card types except Mastercard:
  • 0
    : No terminal used or unknown environment.
  • 1
    : On merchant premises, attended.
  • 2
    : On merchant premises, unattended. Examples: oil, kiosks, self-checkout, mobile telephone, personal digital assistant (PDA).
  • 3
    : Off merchant premises, attended. Examples: portable POS devices at trade shows, at service calls, or in taxis.
  • 4
    : Off merchant premises, unattended. Examples: vending machines, home computer, mobile telephone, PDA.
  • 5
    : On premises of customer, unattended.
  • 9
    : Unknown delivery mode.
  • S
    : Electronic delivery of product. Examples: music, software, or eTickets that are downloaded over the Internet.
  • T
    : Physical delivery of product. Examples: music or software that is delivered by mail or by a courier.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.operatingEnvironment
  • SCMP API Field:
    pos_environment
  • Simple Order API Field:
    pos_environment
pointOfSaleInformation

pointOfSaleInformation. partnerSdkVersion

Version of the software installed on the POS terminal.
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the
Cybersource
 reporting software.
This field is available only for
Cybersource
 integrations.

Specifications

  • Data Type:
     String
  • Data Length:
     32

Mapping Information

  • REST API Field:
    pointOfSaleInformation.partnerSdkVersion
  • SCMP API Field:
    partner_sdk_version
  • Simple Order API Field:
    partnerSDKversion
pointOfSaleInformation

pointOfSaleInformation. pinBlockEncodingFormat

Format that is used to encode the PIN block.
This value is provided by the client software that is installed on the POS terminal.
Possible values:
  • 0
    : ISO 9564 format 0
  • 1
    : ISO 9564 format 1
  • 2
    : ISO 9564 format 2
  • 3
    : ISO 9564 format 3
This field is available only for
Cybersource
 integrations and only for processors that support chip and online PIN transactions.

Specifications

  • Data Type:
     Integer
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.pinBlockEncodingFormat
  • SCMP API Field:
    pin_data_pin_block_encoding_format
  • Simple Order API Field:
    pinDataPINblockEncodingFormat
pointOfSaleInformation

pointOfSaleInformation. pinEntrySolution

Type of PIN pad on the terminal.
Possible values:
  • PCI-SPoC
    : Screen
  • PCI-PTS
    : Physical PIN pad

Specifications

  • Data Type:
     String
  • Data Length:
     50

Mapping Information

  • REST API Field:
    pointOfSaleInformation.pinEntrySolution
  • SCMP API Field:
    terminal_pin_entry_solution
  • Simple Order API Field:
    pos_pinEntrySolution
pointOfSaleInformation

pointOfSaleInformation. serviceCode

Service code that is included in the track data.
This field is available only for American Express and Mastercard transactions on the
Visa Platform Connect
 processor.
You can extract the service code from the track data and provide it in this API field.

Specifications

  • Data Type:
     String
  • Data Length:
     3

Mapping Information

  • REST API Field:
    pointOfSaleInformation.serviceCode
  • SCMP API Field:
    pos_service_code
  • Simple Order API Field:
    pos_serviceCode
pointOfSaleInformation

pointOfSaleInformation. storeAndForwardIndicator

When connectivity is unavailable, the client software that is installed on the POS terminal can store a transaction in its memory and send it for authorization when connectivity is restored.
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the
Cybersource
 reporting software.
Possible values:
  • true
    : Transaction was stored and then forwarded.
  • false
     (default): Transaction was not stored and then forwarded.
This field is available only for
Cybersource
 integrations.

Specifications

  • Data Type:
     String
  • Data Length:
     5

Mapping Information

  • REST API Field:
    pointOfSaleInformation.storeAndForwardIndicator
  • SCMP API Field:
    store_and_forward_indicator
  • Simple Order API Field:
    pos_storeAndForwardIndicator
pointOfSaleInformation

pointOfSaleInformation. terminalCapability

POS terminal’s capability.
This field is available only for the
American Express Direct
,
BNP Paribas France
,
Banque de France et Tresor Public
,
Chase Paymentech Solutions
,
Credit Mutuel-CIC
,
FDC Nashville Global
,
FDMS Nashville
,
GPN
,
JCN Gateway
,
OmniPay Direct
,
Prosa
,
RBS WorldPay Atlanta
,
SIX
,
TSYS Acquiring Solutions
,
Visa Platform Connect
, and
Worldpay VAP
 processors.
Possible values:
  • 1
    : Terminal has a magnetic stripe reader only.
  • 2
    : Terminal has a magnetic stripe reader and manual entry capability.
  • 3
    : Terminal has manual entry capability only.
  • 4
    : Terminal can read chip cards.
  • 5
    : Terminal can read contactless chip cards; cannot use contact to read chip cards.
  • 6
    : Terminal has a magnetic stripe and chip reader capability.
  • 7
    : Terminal has a magnetic stripe and contactless reader capability.
  • 8
    : Terminal has a chip and contactless reader capability.
  • 9
    : Terminal has a magnetic stripe, chip reader, and contactless reader capability .
For an EMV transaction, the value of this field must be a value of
4
 or
5
.

Specifications

  • Data Type:
     Integer
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalCapability
  • SCMP API Field:
    terminal_capability
  • Simple Order API Field:
    pos_terminalCapability
pointOfSaleInformation

pointOfSaleInformation. terminalCardCaptureCapability

Indicates whether the terminal can capture the card.
This field is available only for
Cybersource
 integrations on the
Visa Platform Connect
 processor.
Possible values:
  • 1
    : Terminal can capture card.
  • 0
    : Terminal cannot capture card.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalCardCaptureCapability
  • SCMP API Field:
    terminal_card_capture_capability
  • Simple Order API Field:
    pos_terminalCardCaptureCapability
pointOfSaleInformation

pointOfSaleInformation. terminalCompliance

Flag that indicates whether the terminal is compliant with standards mandated by the Reserve Bank of India for card-present domestic transactions in India.
This field is available only for Mastercard transactions on the
Visa Platform Connect
 processor.
Format:
  • First character indicates whether the terminal supports terminal line encryption (TLE). Possible values:
    • 1
      : Not certified
    • 2
      : Certified
  • Second character indicates whether the terminal supports Unique Key Per Transaction (UKPT) and Derived Unique Key Per Transaction (DUKPT). Possible values:
    • 1
      : Not certified
    • 2
      : Certified
Example:
21
 indicates that the terminal supports TLE but does not support UKPT/DUKPT.
You and the terminal vendors are responsible for terminal certification. If you have questions, contact your acquirer.
The value for this field corresponds to the following data in the TC 33 capture file:
  • Record: CP01 TCR6
  • Position: 92-93
  • Field: Mastercard Terminal Compliance Indicator
The TC 33 capture file contains information about the payments and credits that a merchant submits to
Cybersource
. The processor creates the TC 33 capture file at the end of the day and sends it to the merchant’s acquirer. The acquirer uses this information to facilitate end-of-day clearing processing with payment networks.

Specifications

  • Data Type:
     Integer
  • Data Length:
     2

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalCompliance
  • SCMP API Field:
    terminal_compliance
  • Simple Order API Field:
    pos_terminalCompliance
pointOfSaleInformation

pointOfSaleInformation. terminalId

Terminal identifier assigned by the acquirer.
This value must be printed on the receipt.
This field is a request and response field.
This field is available only for
Cybersource
 integrations.
For requests, you can define this value yourself; however, you should consult the processor for requirements.
These processors have specific requirements:
FDC Nashville Global
To have your account configured to support this field, contact customer support. This value must be a value that
FDC Nashville Global
 issued to you.
Visa Platform Connect
A list of all possible values is stored in your account. When terminal ID validation is enabled for your account, the value you send for this field is validated against the list each time you include the field in a request. To enable or disable terminal ID validation, contact customer support.
When you do not include this field in a request, the default value in your account is used.

Specifications

  • Data Type:
     String
  • Data Length:
     8

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalId
  • SCMP API Field:
    terminal_id
  • Simple Order API Field:
    pos_terminalID
pointOfSaleInformation

pointOfSaleInformation. terminalInputCapability

Complete list of card input methods supported by the terminal.
Possible values:
  • Keyed
    : Terminal can accept card data that is entered manually.
  • Swiped
    : Terminal can accept card data from a magnetic stripe reader.
  • Contact:
    : Terminal can accept card data in EMV contact mode.
  • Contactless:
    : Terminal can accept card data in EMV contactless mode.
  • BarCode:
    : Terminal can read bar codes.
  • QRcode:
    : Terminal can read QR codes.
  • OCR:
    : Terminal can perform optical character recognition (OCR).
This field is available only for
Cybersource
 integrations.

Specifications

  • Data Type:
     String
  • Data Length:
     15

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalInputCapability
  • SCMP API Field:
    terminal_input_capabilities_#
  • Simple Order API Field:
    pos_terminalInputCapabilities_#
pointOfSaleInformation

pointOfSaleInformation. terminalOutputCapability

Indicates whether the terminal can print or display messages.
Possible values:
  • 1
    : Neither
  • 2
    : Print only
  • 3:
    Display only
  • 4:
    Print and display
This field is available only for
Cybersource
 integrations.
For Mastercard cashback transactions, you must send this field with the value of
5
 to indicate that the terminal supports purchase-only approvals.

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalOutputCapability
  • SCMP API Field:
    terminal_output_capability
  • Simple Order API Field:
    pos_terminalOutputCapability
pointOfSaleInformation

pointOfSaleInformation. terminalPinCapability

Maximum PIN length that the terminal can capture.
Possible values:
  • 0
    : No PIN capture capability
  • 1
    : PIN capture capability unknown
  • 2:
     PIN pad down.
  • 4:
     Four characters
  • 5:
     Five characters
  • 6:
     Six characters
  • 7:
     Seven characters
  • 8:
     Eight characters
  • 9:
     Nine characters
  • 10:
     Ten characters
  • 11:
     Eleven characters
  • 12:
     Twelve characters
This field is available only for
Cybersource
 integrations on the
Visa Platform Connect
 processor.
The value of this field corresponds to this data in the TC 33 capture file:
  • Record: CP01 TCR 1
  • Position: 15-16
  • Field: POS Entry Mode

Specifications

  • Data Type:
     String
  • Data Length:
     1

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalPinCapability
  • SCMP API Field:
    terminal_pin_capability
  • Simple Order API Field:
    pos_terminalPINcapability
pointOfSaleInformation

pointOfSaleInformation. terminalSerialNumber

Terminal serial number assigned by the hardware manufacturer.
This value is provided by the client software that is installed on the POS terminal.
This value is not sent to the processor. Instead, the value is forwarded to the
Cybersource
 reporting software.
This field is available only for
Cybersource
 integrations.

Specifications

  • Data Type:
     String
  • Data Length:
     32

Mapping Information

  • REST API Field:
    pointOfSaleInformation.terminalSerialNumber
  • SCMP API Field:
    terminal_serial_number
  • Simple Order API Field:
    pos_terminalSerialNumber
pointOfSaleInformation

pointOfSaleInformation. trackData

For card-present transactions, this field applies to the card’s track 1 and 2 data. For PIN debit transactions, this field applies to track 2 data from the debit card; the sentinels are required.
This field is available only for the
American Express Direct
,
Banque de France et Tresor Public
,
BNP Paribas France
,
Chase Paymentech Solutions
,
Credit Mutuel-CIC
,
FDC Nashville Global
,
FDMS Nashville
,
GPN
,
JCN Gateway
,
OmniPay Direct
,
Prosa
,
RBS WorldPay Atlanta
,
SIX
,
TSYS Acquiring Solutions
,
Visa Platform Connect
 and
Worldpay VAP
 processors.
Card-Present Transactions
FDMS Nashville
:
This value consists of one of the following:
  • Track 1 data
  • Data for both tracks 1 and 2
Other Processors:
This value consists of one of the following:
  • Track 1 data
  • Track 2 data
  • Data for both tracks 1 and 2
Example:
 
%B4111111111111111^SMITH/ JOHN ^2412101976110000868000000?;4111111111111111=24121019761186800000?
PIN Debit Transactions
In the following example, the card number is 4111111111111111, the expiration year is 16, and the expiration month is 12. The end sentinel (?) follows the final character of data recorded on the track.
Example:
 
;4111111111111111=16121019761186800000?

Specifications

  • Data Type:
     String
  • Data Length:
     119

Mapping Information

  • REST API Field:
    pointOfSaleInformation.trackData
  • SCMP API Field:
    track_data
  • Simple Order API Field:
    pos_trackData
pointOfSaleInformation