Does your system have too much downtime and you don’t even know it? Are your customers running away to your competitors without your knowledge?
The answer may be YES if your system experiences regular downtime and worst of all you may not even be aware of the extent of the damage until your reputation has been irreparably tarnished.
The term ‘downtime’ derives from when a system, combination of systems, or any application or service is unable to perform a desired operation. Downtime can be expected and scheduled, such as planned maintenance, or it can be an unintended interruption of service such as a server overload or device failure.
This article is intended to help broaden your thinking about the costs and types of system downtime.
Now that you’ve decided to dispense cash from your kiosk with a bill recycler I want to make you aware of the pitfalls to avoid. Dispensing cash can be invaluable for making change to your customers like a human cashier, but also introduces several new challenges which we’ll address in this article.
Most people familiar with bill acceptors think of a bill recycler as simply an add-on component which dispenses cash, but this is far from the case.
Dispensing bills greatly increases the complexity of the device and the logic required by your kiosk application in order to gracefully complete a cash transaction.
Kiosk software is a security application specifically designed to transform a PC or tablet into a self-service kiosk. The kiosk software is also responsible for locking down your kiosks operating system to prevent malicious user tampering, which is why kiosk software is often referred to as “kiosk lockdown software.”
Some common features of kiosk software include:
Ensures that your kiosk application is always running
In most cases the kiosk operator will desire to deliver their content in the form of a website or native application running on their kiosk. An example of a native application for a kiosk running Microsoft Windows would be a .NET WPF application. For the sake of brevity, for the remainder of this article I’m going to refer to the website or native application running on your kiosk as “your kiosk application.”
What’s the difference between EMV compliance and PCI compliance? The short answer is they’re both guidelines for protecting cardholder data for the purpose preventing fraud, but they focus on different elements of the credit card transaction.
We’ve made it easy to start accepting cash and credit card payments from your self-service kiosk by using the KioskSimple kiosk SDK. Our kiosk SDK abstracts the complicated logic of several popular payment devices and greatly lowers the learning curve thereby saving you significant development costs.
Benefits of the KioskSimple kiosk SDK:
Speeds up development to save you time and money
Allows you to switch between supported payment devices with little to no code rework
Bill jams are commonplace when your kiosk accepts cash payments. No matter how advanced the bill acceptor, there’s always that guy that inserts a bill covered in mud, or something worse, and gums up the device.
Here are just a few examples of the sort of kiosk devices our API supports: