Signature Capture
The Signature Capture feature electronically captures a signature when required for a network sale.
GLOSSARY OF TERMS
The following terms and definitions will assist the reader with understanding the content of the Feature Reference.
MOP
Method of Payment
PetroPAY
Verifone PetroPAY is the base PIN pad application for the MX 800 Series terminals, which are used with the Ruby and Topaz workstations.
PINpad
Customer keypad used for entering a personal identification number (PIN).
POS System
Includes the POS (Point of Sale) terminals, site controller and the Electronic Payment System (EPS).
Signature Capture
Ectronically captures a signature when required for a network sale.
SMS
Site Management Suite for Commander Sapphire Management Suite for Sapphire.
ViperPAY
Verifone ViperPAY is the base PIN pad application that is used with the Viper EPS Payment application which runs on the MX 830*, MX 850*, MX 860, MX 870, MX 880 and on all MX 900 Series hardware platforms.
Overview
Feature Description
The Signature Capture feature electronically captures a signature when required for a network sale.
Signature Capture Attributes
When a card is used and a signature is required, the customer is prompted for a signature on the MX Series PINpad.
The printed receipt does not include a signature line, but depending on the configuration settings, may include the signature image.
Signature Capture saves receipt paper by allowing the cashier to decide whether or not to print a merchant and customer copy.
Signature Capture only applies when a signature is required.
Devices and Requirements
MX Series Device Requirements
supported on the MX 830*, MX 850*, MX 860, MX 870, MX 880 and on all MX 900 Series
the MX 830 and MX 850 support is based on the following part numbers:
MX 830: M090-307-04-R
MX 850: M090-207-01-R, M090-409-01-R, M094-209-01
requires ViperPAY base 1.04.05 and higher for the MX 800 Series PINpads; base 2.0.0 and higher for MX 900 Series PINpads
requires a 64 MB unit
Supported Hardware Configurations
Commander Site Controller with Topaz / Ruby2
RubyCi with Topaz / Ruby2
POS Requirements
All POS versions for Commander and ViperPay versions support Signature Capture.
Configuring Signature Capture
MX ViperPAY Configuration
Configuring Ethernet Settings on MX Series PINpads
Use the ViperPAY User's Guide to access the Configuration screen on the MX Series PINpad.
Select the [Network Settings] option (no serial settings).

Ethernet Settings
IP Address
192.168.31.126 for station one. 192.168.31.127 for station two. For each additional station, increment the last octet of the IP address plus one.
TCP Port
4000
Mask
255.255.255.0
Gateway
192.168.31.31
Select [Apply].
The settings are saved and the terminal reboots.
For detailed instructions see the ViperPAY User's Guide.
Configuring Signature Capture on Configuration Client
From the Configuration Client, go to: Payment Controller > EPS Configuration > EPS Global Configuration.

The EPS Global Configuration window displays.

EPS Tab

From EPS Global Configuration, select the [EPS] tab.
Configure the Signature Capture parameters:
Signature Capture
Signature Capture Enabled
Enables the Signature Capture feature.
Cashier Verify Signature
Enables prompting the cashier to verify the signature.
Print Signature on Receipts
Enables printing a signature on all receipts.
Select [Save] to accept, or [Cancel] to exit without saving changes.
For changes to take effect, exit out and log back in on each POS.
From EPS Global Configuration, select the [POP] tab.

Click to select and check the [Signature Capture Enabled] checkbox for each configured POP ID.
Select [Save] to accept, or [Cancel] to exit without saving changes.
To apply new settings, go to: Configuration Client > Tools > Refresh Configuration.

Using Signature Capture
General Transaction Steps
When Signature Capture is enabled, the transaction steps are as follows:
The customer signs their signature on the MX Series PINpad.

The signature from the MX Series PINpad will display in a window on the POS.

The cashier acknowledges the signature by selecting [OK].
A receipt prints with the signature image.
All three transaction steps are optional and depend on the site's configuration.
The signature image file is stored in the Commander transaction log as an image file, and is available for subsequent review.
In-House Accounts are local to the POS and are excluded from Signature Capture.
Reporting
Transaction Viewer
To view the total signature count for further analysis go to the Transaction Viewer and check the image files stored in the Transaction Set Logs.
Multiple transactions may be selected for viewing. If necessary, the signature data may be printed and saved from the Transaction Viewer.

If signature data needs to be viewed or printed outside of the Transaction Viewer, the TIFF data must be converted to a GIF format so that the signature is viewable. To convert the data, a third party program of the user's choice must be used.
If any T-Logs require archiving, select the transactions, click on Tools from the menu bar and select Archive All Transactions.

A pop up window will appear to select the location the T-Logs will be saved to.

After the location has been selected, click [OK].
This is not an automatic process. Frequent log ins are required to archive the T-Logs.
Last updated
Was this helpful?
