SECURE INTEGRATION METHOD

(SIM) Device Control

S I M D E V I C E C O N T R O L

The SIM controls the flow of all sensitive cardholder data (card, track, exp. date, KSN, Pin Block) without the integrated application ever having to handle it, or even see it

In essence, the integrator need only pass the amount and the transaction type, and the SIM will handle terminal prompting and gathering of informationAll transaction message building is done by the SIM, eliminating the need for an integrator to build an XML string manually

3

S E C U R E I N T E G R AT I O N F E AT U R E S

Supports SSL (Secure Socket Layer) connectivity to the PAYware PC and RiTA servers for added securitySupports secure HTTPS connectivity to IPCharge

The SIM is an ActiveX DLL component that can be used in various programming languages

Robust design allows developers to control the various functions of VeriFone terminalsProcess Credit, Debit, EBT, Gift and Settlement transactions to VeriFone’s four payment engine services: PAYware PC, PCCharge, TransAct, and IPCharge

4

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

Vast error handling

Contains optional, configurable logging as an additional troubleshooting tool

SIM S O FTWARE DEVELO PM ENT K I T

6

The easy to use SIM Software Development Kit is designed to take much of the integration of the devices and payment engines out of the developer’s hands

The SIM control handles all device communication, payment engine message building, and socket or HTTPS communications to the payment engine.

The developer is only responsible for setting the transaction type, merchant ID, device type, and communication properties

S U P P O R T E D V E R I F O N E T E R M I N A L S

V E R I F O N E P P 1 0 0 0 / 1 0 0 0 S E

V E R I F O N E 2 0 0 0

V E R I F O N E S C 5 0 0 0 *

V E R I F O N E M X 8 X X S E R I E S

V E R I F O N E V X 5 1 0 * *

7

* US Debit only** Only supported when configured with the correct terminal application

P S E U D O - C O D E

Along with a comprehensive fully functional sample application, pseudo-code is included for integration to the four payment engines:

‘Create the objectPrivate WithEvents Charge As New SIM.Charge (“COM1”, “1200” , “E”, “7”, SIM.Charge.DeviceType.ppdSC5000, “3”)

‘Gather Card Swipe Private Sub Charge_CardSwipe() Handles Charge.CardSwipeCard = Charge.GetCardExpDate = Charge.GetExpDateMember = Charge.GetMemberEnd Sub

This data can be saved for when the “Process” function is called. Private Sub Process()With Charge

‘Set the Payment Engine/Merchant Configuration properties‘For PCCharge.PaymentEngine = SIM.Charge.PaymentSoftware.PCCharge.MerchantNumber = “999999999911”.Processor = “NPC”.UserID = “User1”

8

S I M S A M P L E A P P L I C AT I O N

9

10

11

12

S E C U R E I N T E G R AT I O N M E T H O D R E V I E W

Allows integration to various VeriFone terminals such as the MX830 and MX850

Allows integration to the four VeriFone payment engines: IPCharge, PCCharge, PAYware PC, TransAct

Terminal is controlled by the SIM, integrator will not handle sensitive information

SSL and HTTPS security

Eliminates the need for integrator to manually create XML string to send transactions to the payment engine, therefore enhancing security

13