Software Application for Self-Service Payment Kiosks

Software for eKassir® - Terminal for self-service payment kiosks is implemented on .NET. Framework. User interface is carried out on Flash (currently a version of user interface on html is being tested). A local database (sql express) is used to store data on a kiosk.

eKassir® software supports virtually all common peripherals, components and interfaces:

• Bill (banknote) acceptors;
• Dispensers, hoppers and other change dispensing devises;
• Receipt printers;
• Fiscal registers;
• Card readers and PIN pads;
• Watchdog timers;
• Bar code scanners;
• Other peripheral devices, which can be used for self-service kiosks.

A support of a new peripheral device be can be implemented in the system quite promptly (from 1 to 3 weeks) within the frames of the project or at our client’s request.

General Principles of eKassir® - Terminal Application Structure

In terms of architecture payment kiosk software application is arranged as follows. Payment scenario on kiosk consists of a set of “steps” like “entering number step”, “number verification step”, “bar code scanning step” and so on. The sequence of “steps” in a scenario and step contents (its settings, messages, data check and other) are described in kiosk configuration file (in xml format). A set of standard steps is big enough to implement the most sophisticated payment scenarios. Yet new “steps” appear in the course of the system development. All data and kiosk settings are stored in kiosk local database. All actions on a kiosk are recorded into log files. All information on payments accepted through the kiosk is also stored in a local database.

System administrator can easily add new services on a kiosk by editing xml configuration file. No involvement of the company –developer is needed.

Each kiosk may have an individual configuration file. Respectively each kiosk can have its own set of services for payment, commission rates and other specifics (including design of screen interface) depending on kiosk location and other requirements.

Bellow is a list of main “steps” comprising payment scenarios (a full list of “steps” is located in the client section of the web site):

• Step «Main menu»
• Step «Enter number or data»
• Step «Insert money»
• Step «Print receipt»
• Step «Scan bar code»
• Step «Display of information returned from server»
• Step «Structured help»
• Step «Enter alphanumeric information»
• Step «Enter meters values»
• Step «Enter amount»
• Step «Menu»

There are more than 20 different scenario “steps”. In the course of the system development the number of “steps” and their functionality are growing and more complex options appear like “draw prize step” or “work with subway map step” or other specialized “steps”.

Such ideology of the kiosk software development allows customer’s employees to independently implement their most daring ideas of payment acceptance through kiosks without addressing software developer for help.

User Interface

Practically any user interface design can be implemented based on eKassir® - Terminal application. Usually when this application is delivered two standard user interface templates are offered for your choice with further adjustments to the customer’s corporate style. This can be done either by customer or developer personnel. There is an option of developing a new user interface design. If necessary a customer is provided with original flash files of “steps” and is allowed to compile the “steps” created by its employees on the developer’s server. Thus, the client’s experts can develop and maintain their own user interface design of the payment kiosk.

Data Exchange between PaySystem Server and Monitoring Server

Data exchange between a kiosk and PaySystem server is conducted over eKassir V2 protocol. It is an open protocol, and its description is in the client section of the website. Payment kiosk can operate both in online mode (payment is accepted only if a number is successfully verified) and also in offline mode (payments are accepted without number verification and are sent to the server once the communication line is established). Except exchange of payment information there is an exchange of service information between PaySystem and a kiosk, for instance exchange of information on external commission limitation (pursuant to contract) for this or that payee.

Information exchange with Monitoring server is required for managing a kiosk, setting external commissions for payments, updating kiosk software, updating payments list being accepted and other things necessary for kiosk operation. All traffic of the information exchange is compressed on both ends, which ensures economic use of GPRS communications (e.g. when services are being updated).

So, eKassir® - Terminal software is a flexible tool for a Customer to solve the most versatile range of tasks from standard payments acceptance to specific projects of fuel (transport) card recharge and the like.