On this page:
The Simplify application is digitally signed to prevent the loading of unauthorized software
Files can be downloaded to MX PIN Pads by the following methods:
- via SCPGET (using FTP server hosted by merchant)
- MX Downloader
To avoid overwriting configured values, all downloads to Simplify PIN Pads must be specified as partial, unless instructed otherwise by Elavon.
Viewing Simplify Load Information
To view information on the Simplify load present in the PIN Pad, press 0 and ENTER when the PIN Pad is in a Closed state. The PIN Pad will return to the usual Idle screen after several seconds. The information on this screen may be requested by Elavon for troubleshooting purposes.
Sample Field Values
Note: The fields on this screen will vary by implementation. The following list contains a sample of the available fields:
- Merchant: Elavon
- Vers: 2.19.08 – 2.19.01
- OS Version: release-30811700
- CT Frame: 4.6.5-352
- CTLS Frame: 5.22.5-352
- P Addr: DHCP - xxx.xxx.xxx.158
- Current Date/Time02/15/2019 10:03:11
- EMVCert: 2.18
- Package: 2.19.08
- TndrVer: 2.19.00
- Serial: 169-005-255
- Kernal: L27.0.2
- EMV_Applications : 190214
- EMV_Keys : 170202
- PCI4 Device : No
The fields shown in the above sample define the following:
|Merchant:||Customer for whom load was built|
|Vers:||Simplify application and parameter version number|
|OS Vers:||Verifone OS version number|
|CT Frame:||Contact EMV framework version|
|CTLS Frame:||Contactless EMV framework version|
|IP Addr:||IP Mode and masked IP address of PIN Pad|
|Current Date/Time||Current date/time|
|Package:||ID of package used to build current load|
|Serial:||PIN Pad Serial Number|
|Kernal:||EMV Kernel version|
|EMV_Applications :||EMVParm version|
|EMV_Keys :||Cakeys version|
|PCI4 Device :||PCI4 compliant device?|
For purposes of security, a production Simplify application is digitally signed by assigning an Elavon-sponsored certificate to the application after it has been fully tested and is ready for production use. An unsigned application, or an application signed with a different certificate, will not be accepted by the PIN Pad.
VHQ is a Verifone terminal maintenance system. Please contact your Elavon representative for details.
Download Driven by POS Command
Simplify supports POS-driven downloads for MX PIN Pads running Simplify. If this functionality is implemented, Simplify PIN Pads will request and receive downloads via SCPGET in response to messages exchanged between the POS and Simplify. The description given in this section should allow Elavon customers to set up POS-driven downloads.
If this is set up, MX files will be downloaded in compressed form in a GZipped Tar File (.tgz) file from a SCPGET (secure file transfer) server using configuration values loaded in the PIN Pad. A .tgz file can contain any or all of the following: screens, form files, configuration, application, system upgrades/libraries. After a successful download, the PIN Pad will automatically expand the files in the .tgz, install the expanded files, and restart itself.
The Simplify API allows a merchant to control POS-driven MX downloads via SCPGET by providing/supporting two separate types of message exchange. These messages are used to:
- Perform version number inquiries (06 message exchange).
- Command the PIN Pad to download a new load (07 message exchange).
Combining these messages (see Fig. 16) allows Simplify to control PIN Pad downloads by using the data in the version number (06) response to determine whether a download request (07) should be sent:
The flow for a POS-driven download is as follows:
- The Version Number Inquiry (36-06) request and response is informational, and optional before the Load Simplify File via Secure File Transfer (36-07) request.
- When Simplify receives a Load Simplify File request , it requests a download from the download server via SCPGET, which responds by sending a .tgz containing the requested files.
- Simplify will only send a Load Simplify File response if there is an error involving the download.
In order to manage PIN Pads by messages sent between the POS and Simplify:
SCPGET server software must be loaded and installed on the file server (see below).
Simplify must be loaded and installed on the PIN Pad. This will automatically install SCPGET client capability on the PIN Pad.
Simplify SCPGET client software must be configured to allow Simplify to communicate with an SCPGET server (see below for overview; below under SCPGET Configuration for details).
POS code must be written to support the desired functionality: Programming a Version Number Inquiry request and storing the latest build number received from the host will allow the POS to obtain the application build number present in the PIN Pad and compare it with that received from the host. Programming a Load Simplify File request will allow the POS to initiate PIN Pad downloads from a configured SCPGET server. (See further under POS Coding below.)
SCPGET Server Installation and SCPGET Client Configuration
SCPGET server software must be present on the machine that will act as the file server for downloads. On Windows, this software will need to be downloaded and installed. Simplify customers typically use Bitvise WinSSHD for this purpose. On Linux, SCPGET is natively supported.
As part of Simplify installation, SCPGET client capability is automatically installed on the PIN Pad. Client software is delivered pre-configured, with settings (e.g. server address) that allow each PIN Pad to communicate with its configured SCPGET server and receive downloads. SCPGET configuration settings are stored in the parameter file parm.fil.
If you need to modify these settings, they can be edited using a text editor (see below under SCPGET Configuration for details). The modified parm.fil will need to be digitally signed by an appropriate authority and incorporated into a loadable .tgz; if desired, Elavon can help with this process.
Supported POS-Simplify Messaging
The following messages can be used to control PIN Pad updates:
- The POS can send a Version Number Inquiry (06) request to a PIN Pad whenever the lane is idle. The 06 response from the PIN Pad will contain the build number of the currently loaded PIN Pad application. This message exchange can be used as part of the update process (optional) or for informational purposes only.
- The POS can send a Load Simplify File via SCPGET (07) request to the PIN Pad whenever the lane is idle. This request commands the PIN Pad to request an application download from the configured SCPGET server. If the requested download is unsuccessful, the PIN Pad will send a 07 response indicating the reason for the download failure.
If 06 and 07 message support has been implemented, and the POS has been programmed to store the latest application build number received from the host, MX updates can be controlled from the POS by combining Version Number Inquiry (06) and Load and Load Simplify File via SCPGET (07) messages as follows:
- After sending a 06 request, check the application build number received in the response against the stored build number.
- Use an application build number mismatch as the trigger for sending a 07 request to the PIN Pad.
PIN Pad updates can also be controlled from the POS using just a 07 request, without a preceding 06 message exchange.
The following four bullet points summarize the POS coding required to control Simplify MX updates by combining 06 and 07 messages:
- Program the POS to store application build numbers received from the host covering each PIN Pad in the system. Update the stored numbers whenever new build numbers are received from the host providing this data. (Data maintenance details do not affect Simplify.)
- Program the Version Number Inquiry (06) request from the POS to the PIN Pad.
- Program a comparison between the build number received in the 06 response and the stored build number for the device.
- Program the POS to send a Load Simplify File via SCPGET (07) request to the PIN Pad if the build number in the 06 response does not match the corresponding stored value. The 07 request must specify a download (.tgz) file containing an application update; the download file must be specified by filename and location on the SCPGET server.
See Simplify Verifone Developer Guide under Version Number Inquiry Message and Load Simplify File via Secure File Transfer Message for message details.
SCPGET client capability is automatically installed on the PIN Pad by the Simplify installation process. Client software is delivered pre-configured, with settings on each PIN Pad that allow it to communicate with its configured SCPGET server and receive downloads from this server. These settings are stored in the PIN Pad parameter file parm.fil and define server location (IP Address or host name), server port, user ID and user password.
If any pre-configured SCPGET client setting needs to be modified, this can be done by editing parm.fil in a text editor. In order to prevent the loading of unauthorized software, the modified parm.fil will need to be digitally signed by an appropriate authority before incorporating the modified file into a loadable .tgz. If desired, Elavon can help with this process.
A sample of the section of parm.fil that controls SCPGET communications is shown below. The UserName and Password will be included in the download request from Simplify to the configured SCPGET server and used to authenticate this request.
\[SFTPVersionOptions\] SFTPIP=10.164.241.155 // IP address or host name of the SFTP server SFTPPort=22 // Port number for the SFTP server UserName=sshtest2 // Username for the SFTP server Password=Elavon11 // Password for the SFTP server
Using the MX Downloader
The Simplify application is delivered to the PIN Pad in compressed form as a .tgz file.
The MX Downloader is a PC application (downloaded from Verifone) that can be used to control the downloading of .tgz files to the MX manually. The Downloader must reside on the same machine as the .tgz files it will process.
Since the procedure to download a .tgz file to a MX PIN Pad requires actions to be performed on both the PIN Pad and the PC containing the Downloader application, the installer will need to have access to both devices.
To load a PIN Pad using the MX Downloader
From the Home screen under Verifone System Mode (Fig. 12), select the Transfer tab.
From the Transfer screen, select the Netloader tab. This will display a screen allowing the PIN Pad to receive a download (fig. 17):
On the machine where the MX Downloader has been installed, go to the Downloader and start the application. The Downloader window will be displayed (Fig. 18):
In order to download a .tgz to an MX PIN Pad, the Destination IP field must contain its IP address. To enter the address, click on the first text box under Destination IP and type the first part of the address. Then tab to the next 3 boxes and type the next 3 parts of the address. (Leading zeroes not required.)error_outline
The only fields that should be modified in this window are Destination IP and File to send. Download Type must be left as partial, unless instructed otherwise by Elavon.
To select the download file, click on the Browse button under File to send and navigate to the .tgz file you want to download. Click on the file to put it in the File to send field. Then Click on the Send button to send the selected file to the MX.
Download status will be displayed at the bottom of the screen. The sequence for a successful download is: Connect, Sending, Installing Files, Logging Off, Install Complete (Terminal Rebooting). The Installing Files and Install Complete (Terminal Rebooting) screens are shown below (Figs. 19-20):
When the download is complete, close the MX Downloader by clicking on Exit.
Go to the Home screen on the PIN Pad (Fig. 21, same as Fig. 12):
Press the Run App button on the Home screen (Fig. 21). The Simplify Initialization screen (Fig. 22, same as Fig. 2) will be displayed:
After connecting to Fusebox, an application-specific Idle screen will be displayed. The updated PIN Pad is now ready for use.