IPC Environments

The following sections show how IPC can be used in different environments.

IPC for Retail

IPC implements the standard transaction types for retail applications like Sale and Refunds and can be configured for cash back transactions if required. When a merchant requests the option for pay with cashback then IPC asks for the amount if the card supports the function.

IPC provides multiple mechanisms for cancelling previously performed Sale transactions. Available methods are cancel and refund.

In UK and Ireland, the cancel transaction should be called before the end of day settlement to the processor, typically midnight. A transaction cannot be cancelled if the settlement processing has completed.

The WPT central service creates a batch for every terminal called FCR (Financial Control Record). The FCR is a logical grouping of all the transactions performed by a terminal in a day. By default all batches are closed at midnight: alternatively 04:00 batch closure, or terminal managed batch closure can be configured by request.

A terminal will have only 2 open batches at any given time. Once a batch is closed no other transactions can be added to that batch and a new batch is created for the next transaction.

IPC also provides X and Z totals reports to download the latest totals on the current batch. The Z-report will close a WPT batch and can be used to report terminal activity in shifts.

For United States, IPC supports both Credit and Debit transactions. The Credit transactions are settled through the batch settlement process similar to UK. The Debit transactions are settled as Host Data Capture, i.e. they are settled in real-time.

Note: Settlement processing starts at 00:04 GMT for all customers. All transactions executed before 00:04 GMT will be included on the days Settlement file. Alternatively customers can be configured for a later settlement run at 04:00 GMT.

IPC for Semi-Attended

IPC implements the standard transaction type sale for semi-attended applications. The PEDs and modes supported for this environment are:

PEDs : iPP350 (UK & ROI), Vx820 (UK , ROI and US) , P400(UK and ROI)

Modes : Contact and Contactless

IPC - Semi Attended

Run IPC Application as Service

IPC may be run as a Windows service when using HostedEVT mode i.e. IPC communicates with POS using IntraMessages and no IPC UI is displayed.

When IPC runs as Windows Service the merchant application is enabled to start and stop IPC or to abort execution of IPC by using scripted commands.

To enable this option, IPC should be configured with options Run IPC as Service and Is HostedEVT selected in theHosted IPCtab.

Windows

Steps to run IPC as Service

  1. Run Emboss set up the same as normal IPC Application
  2. Select IPC as a Service option present in Hosted IPC tab in YESEFT Configuration
  3. Select Pinpad
  4. Go to bin folder
    • Run installIPCService.bat to install Application Service
    • Run startIPCService.bat to start IPC and check yescps.log and wrapper.log (for console logs) in YESEFT\logs folder
    • Run stopIPCService.bat to exit IPC Application
    • Run uninstallIPCService.bat to uninstall Application Service

YESEFT Folder contents:

IPC as a Windows service works through the Yet Another Java Service wrapper i.e. yajsw software. The yajsw jars (i.e. wrapper and wrapperApp jars) are found in the YESEFT folder.

YESEFT/bin Folder

This folder contains some additional necessary scripts used for running IPC application as service.

The following Windows bat files are inside this folder:

  • installIPCService: To install the IPC application and register it as windows service. Check task manager as shown below:

Task manager screenshot

  • IPCServiceSetenv: This file is called from installIPCService.bat file for setting necessary environment and configuration parameters
  • startIPCService: To start IPC Application as windows service. Check task manager as for installIPCService.

If configuration changes are made, the IPC application must be restarted for the changes to take effect.

  • stopIPCService: To stop IPC Application as windows service. This will remove PID of service from task manager.
  • uninstallIPCService: To uninstall IPC application and de-register it as windows service. This will remove service from task manager.
  • Wrapper and wrapperw: To include necessary jars for running wrapper.
Properties Folder

The following property and configuration files are present inside the properties folder:

  • evt.properties: Added Boolean key RUN_AS_IPC_SERVICE.
  • Ipcprocessid.txt: This contains process id of the running IPC Service.
  • wrapper.conf: This is the main configuration file of the wrapper to set all the functional parameters of the service.
Logs Folder

The following log files are present in logs folder:

  • wrapper.log: Log file to which all output to the console will be logged.
  • yescps.log: Logs related to the flow of IPC application.
YESEFT Configuration Changes

Please see below configuration changes related to run IPC as service.

  • When Is HostedEVT in the Hosted IPC tab is selected then software and firmware upgrade checks are selected and no further changes are allowed
  • If the IPC As a Service checkbox with hosted EVT inside the Hosted IPC tab is selected then:
    • EnableGUI present inside LooknFeel tab is disabled
    • The Printer dropdown and Print Receipt checkbox inside the Receipt tab is disabled
    • AutoSensing COM port inside the General tab is selected and no further changes are allowed