terminal interface transaction flow scenarios
DESCRIPTION
Terminal Interface Transaction Flow Scenarios. MX Direct Transaction Flow. Serial or USB connection. ` Note: Upon transaction approval, the MX terminal can prompt for signature capture. The signature will be uploaded and stored in PAYware Connect along with the transaction. - PowerPoint PPT PresentationTRANSCRIPT
TERMINAL INTERFACE
TRANSACTION FLOW SCENARIOS
3. MX Direct submits txn toPAYware Connect
PAYware Connect Gateway
PAYware Connect
4. PAYware Connectsubmits transaction to
processor
5. Transactionresponse returned to
PAYware Connect
6. Transaction Responsereturned to MX Direct
7. Transaction
response returned toPOS
Serial or USB connection`
Note: Upon transaction approval,the MX terminal can prompt for
signature capture. The signaturewill be uploaded and stored in
PAYware Connect along with thetransaction.
-
Card ProcessingNetwork(s)
2. MX800 Terminal prompts for card
swipe (and PIN if applicable). Sensitivecard data is encrypted by VeriShieldProtect (VSP) at time of swipe on MX
terminal
1. POS applicatonsubmits to MX
terminal txn amount/type via STX/ETX
framed packet
MX DIRECT TRANSACTION FLOW
ModemBank
POS with SIM.DLLand TIM Service
installed
POS with SIM.DLLand TIM Serviceinstalled, modem
attached
SIM DLL Typical Store Layout
Overview:
This is an overview of a typical store setting. TheSIM.dll resides on all POS machines. Each POSwill have a VeriFone Mx device serially attached.The POS will direct the SIM to communicate withthe Mx device via that serial com port connection.The POS will direct the SIM to communicate withTIM which also installed on each POS. TIM will beconfigured to communicate with the PAYware
Modem
AT&T Data Center
PAYwareConnect
transaction type toSIM.DLL SIM.DLL
resides on each POSworkstation.
Card ProcessingNetwork(s)
6. SIM.DLL submits
transaction to PAYwareConnect
HTTPS Post
PAYware SIM.DLL Transaction Flow1. POS application
specifies transactionamount and
PAYware Connect Gateway
2. SIM.DLL sends txn amount/type to
MX800 terminal via Ethernet, Serial orUSB
4. Card data returnedto SIM.DLL
`
5. SIM.DLL buildstransaction message
Internet Connection
transaction responseis returned to
PAYware Connect
9. Transaction
response is returnedto SIM.dll/POS
-Windows only (no WindowsEmbedded)-Requires .NET Framework-Resides on each workstationthat has a terminal connected-Requires Internet access from
each workstation
7. PAYware Connectsubmits transaction to
processor
PAYware Connect
8. Upon completion,
)
Supported Terminals:Vx810 (serial/USB Vx810 Duet (serial/USB)
VSP200 (serial/USB)PP1000SE (serial/USB)
MX830MX850MX860MX870MX880MX760
3. MX800 Terminal prompts for cardswipe.
Note: Upon transaction approval, terminal canprompt for signature. Signature can be uploadedand stored in PAYware Connect along with theransaction approval.
`
VeriFone MX800
Terminal – Static IP,VSP enabled
POS application
eTIM
Card processingnetwork
prompts the appropriate MX forcard swipe and PIN (if applicable)
TCP/IP Socket
3. VSP encrypted card datareturned to eTIM
HTTPS Post
4. eTIMbuilds
transactionmessage
Enterprise Terminal InterfaceManager (eTIM)
ServerPOS
PAYware Connect
NetworkConnection
TCP/IP Socket
2. eTIM interprets the data and
TCP/IP Socket
1. POS sends non-
sensitive transaction datarequest to eTIM (client ID,terminal IP, txn type/amt)
NetworkConnection
Network
Connection
6. PAYware Connectsubmits transaction to
processor
7. Transaction responsereturned to PAYware
Connect
8. Transaction responsereturned to eTIM
Network
Connection
POS
5. eTIM submitstransaction to PAYware
Connect
TCP/IP Socket
9. Transaction responsereturned to terminal and
Note: Upon transaction approval, theterminal can prompt for signaturecapture. The signature can be
uploaded and stored in PAYwareConnect along with the approved
transactions.
-Centralized model; eTIM resides on a localserver-Requires MX terminal to be connected via IP (noserial, USB)-Additional network connection at each register/lane required-Credit, debit, gift, EBT supported-Supports use of multiple merchant accounts on asingle MX terminal-Designed specifically for PAYware Connect
Internet
Supported Terminals:MX830MX850
MX860MX870MX880MX760
`
Card ProcessingNetwork(s)
HTTPS Post
Vx Direct Transaction Flow
1. POS applicationsubmits to Vx
PAYware Connect
6. Transaction Responsereturned to Vx Direct
7. Transaction
response returned toPOS
terminal txn amount/type via STX/ETX
framed packet
Serial or USB
-Requires IP connectionavailability at each lane/register for the Vx terminal-Dial-up backup supported-Credit, debit and giftsupported
-Signature capture notavailable
PAYware Connect Gateway
4. PAYware Connectsubmits transaction to
processor
5. Transactionresponse returned to
PAYware Connect
2. Vx terminalprompts for cardswipe (and PIN if
applicable). All carddata is VSPencrypted
3. Vx Direct submits txn toPAYware Connect
Internet
Supported VxTerminals:Vx810 Duet
Vx510Vx520Vx570