General Guidelines

The following general guidelines apply to Simplify running on Ingenico PIN Pads:

  1. IMPORTANT: PCI DSS Compliance: The customer is responsible for securely deleting the encrypted data and making it unrecoverable after authorization using a method that supports PCI DSS secure delete standards (PCI DSS 3.0 Requirement 3.2).

  2. If the POS process receives any response while not expecting a response, it disregards that response.

  3. For all responses, the POS process validates that the response received matches the last request sent. It matches the reference number in the request and response.

  4. If multiple POS workstations can be associated with a single PIN Pad and a TCP/IP connection is used, Simplify assumes that the POS process ensures that there is only one outstanding transaction per PIN Pad.

  5. The POS process needs to maintain a timer associated with each PIN Pad. If this timer expires while waiting for a response to a Sale Authorization transaction, the POS process needs to send an Inquiry message to that PIN Pad. The POS process must wait for a response to the Inquiry message and continue processing based on the response to the Inquiry message.

  6. See “Transaction Type Detail – Transaction Inquiry” in the Elavon Gateway Message Getting Started Guide for more information.

  7. Simplify is capable of doing limited Stand-in Processing based on parameter settings. Some Stand-in Responses must be followed by an Inquiry. See Stand-in Processing for more information.

  8. The encrypted account number or token might be available to the POS. The POS can send a request with the account information to Simplify. Account information is identified as Field 3.

  9. PIN Pad maintenance (downloads) are managed using Ingenico’s IngEstate software.

  10. For support purposes, Elavon requires that the POS logs all messages received from and sent to Simplify. For chargeback, the POS must retain the EMV response messages.

  11. Simplify supports contactless electronic payments using MSD emulation. Supported implementations include Apple Pay, Google Wallet and Softcard.

  12. If the data in Field 2 (Amount) or any other amount field does not include a decimal point, the decimal point will be assumed. (e.g., a value of 2000 in this field should be read as 20.00).

  13. Simplify supports Pay@Table transactions. See Pay-At-Table for more information.

  14. If a transaction refers back to a previous transaction (e.g. Void, Prior Auth) and includes a token, the request for the subsequent transaction must follow the Fusebox Integration Guide, including POS data code (API field 47).

  15. Fields in messages sent to the POS will not necessarily appear in order by field number. E.g. the following sequence of fields is possible:

API Field #, Value Description
0001,36 Transaction Type
5001,010003888 Non-Financial Data
0011,14123010000?V102.18B01803 User Data