INTRO DUCTIO N TO SIM.DLL
AGENDA
SIM.DLL Overview and Features
SIM.DLL Requirements
Supported Terminals
Transaction Flow
Benefits
S I M . D L L O V E RV I E W
SIM stands for Secure Integration Method
The SIM controls the flow of all card sensitive data
(card, track, exp. date, KSN, Pin Block) without the
integrated application ever having to handle it, for
Secure Transactions
The SIM.DLL is an ActiveX DLL component that can
be used in a variety of programming language
environments
Eliminates the need for a separate integration to the
terminal and payment solution to minimize
development time
Shields the POS from sensitive card swipe and PIN
data
4
SYSTEM REQUIREMENTS
Windows Operating System only
Terminal connected to computer via serial or USB
Microsoft .NET Framework v. 3.0 or higher
The SIM.dll must reside on the same computer that
the terminal is connected to
Connectivity to a VeriFone payment solution, such as
PCCharge, PAYware PC, PAYware Transact or
IPCharge
5
F E AT U R E S
An extensive sample is provided to aide integrators with coding their
application
Supports all processors that are supported by the four payment
engines
Utilizes the features of Microsoft’s .NET 3.0 framework. This provides
less dependency on third party controls
BIN Management (Debit Encouragement) available *
Offline/SAF functionality available *
Signature Capture
Secure communications (SSL and HTTPS)
* Separate license required
6
S U P P O R T E D H A R D WA R E
PP1000SE
Mx830
Mx850
Mx860
Mx870
Mx760
Vx610
Vx570
7
TRANSACTION FLOW
8
B E N E F I T S O F S I M I N T E G R AT I O N
Simple: Eases integration to VeriFone devices and
payment processing solutions
Secure: Sensitive cardholder track data is protected
by the SIM
Support: Support for a wide variety of VeriFone
devices and Payment Solutions
Solutions: Many credit card processor choices
available
Speed: The benefits of quick transaction processing
via TCP/IP connection
9
C U S TO M E R B A S E
Integrators planning to launch a Windows based
payment solution are prime candidates for using SIM
in their solution.
This extends to everything from Brick and Mortar retail
to Direct Marketing customers
10
I M P L E M E N TAT I O N W I T H PAY WA R E
SIM both supports integration through the Device
Master (Device Key) and through a certified API
Application (Merchant Key).
SIM can support serial and TCP/IP communication
between the POS and the Device.
SIM can support TCP/IP, HTTPS Post, and Dial-up to
PAYware Connect.
11
VSP
Currently VSP requires that SIM integrate via the
Device Master and that the registered device has
VeriShield Protect enabled.
The Activation transaction for VSP must occur during
a valid sale to PAYware Connect. Failure to do so will
result in the encryption keys between CDMS and the
device to become out of sync.
12
T R O U B L E S H O O T I N G TO O L S
SIM outputs a log called SIMEvent.log.
This log records all communications between the
device and the POS, including communications
between the PC and PAYware Connect.
This log can contain almost any piece of information
needed to troubleshoot a SIM integration issue or
transaction failure.
13
S U M M A RY
PAYware SIM, providing a single interface to simply and securely integrate
Windows-based POS systems with VeriFone’s secure payment software
solutions and consumer activated acceptance devices.
The developer tool isolates sensitive cardholder data from the POS application,
and is designed to greatly reduce the complexity and associated costs of
achieving compliance with PCI and PA DSS requirements.
PAYware SIM—Secure Integration Method—provides developers with an easy to
integrate Windows DLL that allows their applications to seamlessly take
advantage of the breadth of VeriFone’s extensive card acceptance devices and
payment processing engines.
PAYware SIM enables POS developers to support VeriFone software-based
payment solutions, including IPCharge, PAYware Transact, PAYware PC, and
PCCharge, and to accommodate card acceptance solutions including the PINpad
1000SE, the MX800 Series and the Vx 810.
By providing this secure development tool, we’re also easing the effort to comply with PCI
DSS requirements for secure payment systems.
14