Milan / Paylink System Manual Issue 1.5 29 January 2020
CONFIDENTIAL
Not to be disclosed without prior written permission from Aardvark Embedded Solutions Ltd
Page 39 of 71
Cashless Processing
Background
There are a number of cashless systems available that are supported by Paylink. These include:
Credit Card Acceptance and Ticket In / Out applications for AWP systems.
Paylink provides an interface to support this for acquiring credit (from a ticket or from a credit card).
In all cases, the remote processing runs autonomously, and Paylink provides a structure that reflect
the processing of the remote unit, which should be regularly polled by application in order to
determine what is happening.
Facilities for "disposing" of credit (e.g. a Ticket printing system) require no special processing and are
handled as another dispenser.
Data is transferred to and from the Paylink system using a Cashless Object, and control of the
process is via a number of functions, whose names start Cashless...
The most import property of the Cashless object is the current state, which allows the application to
see where the cashless system is up to.
The Values for the CurrentState item are duplicated here:
No appropriate unit connected
The device has become non operational
The device has become non operational
Idle, but prepared for Credit Requests
These are only valid during Credit Input operations
Arbitrary Credit Available
Credit Request from Application Accepted
Credit Actually Taken for remote source
Credit Request from Application Refused
Application has successfully cancelled the transaction
The device failed during processing - no credit taken
The device failed during processing - credit was taken
To Next Page
Loading...