Aardvark Paylink - Processing Sequences

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 40 of 71
Processing
Credit Card Sequencing
Note that for each function CurrentState will normally return the transient state CR_BUSY before
becoming the state shown in the table.
The following table shows the normal sequence of states taken by CurrentState during a typical credit
card transaction:
State
Normally Entered Because:
CR_NO_UNIT
System Startup
CR_DISABLED
Paylink discovers the cashless unit
CR_IDLE
Application Calls CashlessEnable or CashlessReset
CR_AVAILABLE
Credit Card Presented
CR_AVAILABLE_IDLE
System idle with e.g. MDB Level 3 "always Idle" processing
enabled.
CR_CONFIRMED
Application Calls CashlessRequestCredit and the credit is
available.
CR_TAKEN
Application Calls CashlessTakeCredit
CR_REFUSED
Application Calls CashlessRequestCredit and the credit is
not available.
CR_CANCELLED
Application Calls CashlessCancel
The State "CR_AVAILABLE_IDLE" should in general be processed in exactly the same way as
"CR_AVAILABLE", the only difference being that it is the normal state of the unit and the value in
Ticket Sequencing
The following table shows the normal sequence of states taken by CurrentState during a typical ticket
transaction:
State
Normally Entered Because:
CR_NO_UNIT
System Startup
CR_IDLE
Paylink discovers the cashless unit or CashlessReset
CR_AVAILABLE
Application calls SubmitTicket with a valid ticket reference
CR_CONFIRMED
Application Calls CashlessRequestCredit for the value on
the ticket.
CR_TAKEN
Application Calls CashlessTakeCredit
CR_REFUSED
Application Calls CashlessRequestCredit and the credit is
not avaiable.
CR_CANCELLED
Application Calls CashlessCancel
Abnormal Processing
The above table represent the normal way that credit acquisition proceeds. Paylink however includes
facilities to handle abnormal situations. These situations use the fields: TotalAcquisitions and
TotalCredit.