PayComplete™™ Help Center

The Connect on-Device installation folder contains configuration files with examples of settings for new features.

Connect on-Device folder structure

When you upgrade the software, new features and limits are not automatically added to the configuration files in the configurable folder of the installation folder structure. Check the release notes to find which features to use.

Open the configuration files in the installation folder and copy the new strings to the upgraded configuration files in the configurable folder.

Configured limits and settings for the added features are persistent. That is, when you upgrade the software the next time, the configured limits and settings are unaffected by the software upgrade.

A UUID is the unique identifier of a machine's Connect on-Device installation.

In Connect on-Device you set the machine UUID to identify individual machines, or Connect on-Device instances, in the communication with Connect.

The UUID is automatically generated the first time you start Connect on-Device.

These are the most common situations when you may want to change a UUID;

If you want the new machine to appear as the old, you need to copy the UUID of the old machine and then change the UUID of the new machine into that of the old machine.

You can change the UUID from within Connect on-Device, both manually and by scanning a QR code containing the UUID. From the Administration main menu in Connect on-Device, you can view the current UUID and print it.

You configure the UUID for a machine when you want to replace the machine, the computer, or the hard drive.

Prerequisites: You need an account with the following permissions:

You upgrade your license from Basic Edition to any other edition when you need to expand the functionality of your Connect on-Device.

In the Connect on-Device installation, configuration files are included. You can change the default configuration by editing the files in a text editor, such as Atom.

You configure languages for the display and receipts in the com.scancoin.core.userpref.UserPreference file.

# American English
operator.locale.lang=en
operator.locale.country=GB
user.locale.lang=en
user.locale.country=GB

# Spanish
#operator.locale.lang=es
#operator.locale.country=ES
#user.locale.lang=es
#user.locale.country=ES

# Swedish
#operator.locale.lang=sv
#operator.locale.country=SE
#user.locale.lang=sv
#user.locale.country=SE

# American English
#operator.locale.lang=en
#operator.locale.country=GB
#user.locale.lang=en
#user.locale.country=GB

# Spanish
operator.locale.lang=es
operator.locale.country=ES
user.locale.lang=es
user.locale.country=ES

# Spanish (Mexico)
#operator.locale.lang=es
#operator.locale.country=MX
#user.locale.lang=es
#user.locale.country=MX

Dispense limits limit the amount of money that can be dispensed from a machine. You can configure dispense limits for a group of machines. You can specify dispense limits for multiple currencies.

Important

Before defining dispense limits, you must enable dispense limits in the com.scancoin.common.remote.properties file.

Distributed dispense limits are dispense limits shared by all machines within one machine group. It is possible to configure distributed dispense limits on one machine in a machine group, and then all machines in that machine group get the same dispense limits.

From Connect, you can configure and combine distributed dispense limits for:

There are two available settings for dispense limits:

You configure the dispense limits in the com.scancoin.common.dispense.DispenseService file.

DailyDispenseLimit.role.{roleName}={Currency list}

DailyDispenseLimit.user.{userId}={Currency list}

A currency list consists of the currency, a colon symbol (:) and the total value. Entries are separated with commas, for example: EUR:10000, SEK:50000

It is possible to set a dispense limit per machine. The machine has an account of its own. The dispense limit per machine overrules the dispense limit set per user, for example:

DailyDispenseLimit.machine=EUR:10000

The daily dispense limit is, by default, reset every midnight.

To reset at any other hour set the DayBreakHour, for example:

DayBreakHour=15

To set the DayBreakHour for a certain user, for example:

DayBreakHour.user.(userID)=16

Use commas to separate transactions.

Possible values are:

Example: DEPOSIT and DISPENSE: TransactionTypesAffectingLimits=DEPOSIT,DISPENSE

DailyDispenseLimit.user.{cashierAnna}={EUR:150000}

The code has the following effect on Cashier Anna’s deposit and dispense actions during one day.

Example: DEPOSIT and DISPENSE: TransactionTypesAffectingLimits=DISPENSE

DailyDispenseLimit.user.{cashierAnna}={EUR:150000}

The code has the following effect on Cashier Anna’s deposit and dispense actions during one day.

Use commas to separate the transactions. Possible values are DISPENSE, DEPOSIT and DISPENSE. The default option is DISPENSE.

Example: DISPENSE, DEPOSIT: MachineLimitTransactionTypes=DISPENSE,DEPOSIT

DailyDispenseLimit.machine=EUR:15000

The code has the following effect on the machine deposit and dispense actions during one day.

Example: DISPENSE: MachineLimitTransactionTypes=DISPENSE

DailyDispenseLimit.machine=EUR:15000

The code has the following effect on the machine deposit and dispense actions during one day:

Use in conjunction with DayBreakHour=-1 to remove the daily renewal. ResettingTransactionTypes=END_OF_SHIFT

Set number of notes for MaxDispenseCountOfNotes.

Example: MaxDispenseCountOfNotes=80

Set canExceedInitial to false to limit the account to the initial value also when more than the initial value has been deposited.

When set to true, the deposit adds to the initial value and changes the dispense limit.

Example: canExceedInitial=true

DailyDispenseLimit.role.{cashier}={EUR:15000,DKR:1500} TransactionTypesAffectingLimits=Deposit DayBreakHour.user.cashier=20

DailyDispenseLimit.machine=EUR:300000 DayBreakHour=06

The code limits the dispense according to the description below.

Custom data entry is a method to add customer-defined data to different kinds of transactions.

You configure custom data entry in this file:

custom_data_entry.xml

The file is located in:

[installation folder]\resources\configurable\configuration\custom_data_entry.xml

The general structure of this document is:

<user_field_definitions>
    <entry-point start="id-of-first-step" />
    <steps>
        <step id="xxx" attributes />
        <step id="yyy" attributes />
    </steps>
</user_field_definitions> 

The entered custom data is included in the resulting RM Transaction message as: <key>=<value> pairs. For more information, see the Connect on-Device RM Protocol, Transaction on SCAN NET.

Custom data entry is available for inclusion on receipts from a custom_data node in the generated receipt context.

The table lists the defined entry points for custom data entry.

You can enable custom data entry for each flow with a defined entry point, except for deposit and dispense, which for legacy reasons still require permissions: DEPOSIT_CUSTOM_DATA and/or BAGDROP_CUSTOM_DATA and DISPENSE_CUSTOM_DATA respectively.

<-- Defines starting step for custom data deposit. Optional -->
<deposit start="start_deposit" />

<!-- Defines starting step for custom data dispense. Optional --> <dispense start="start_dispense"/>

These are the possible kinds of custom data entry steps:

Each step has an optional 'next' attribute for the ID of a following step. If no ID is provided, custom data entry is completed and the normal flow is resumed.

You can add an optional list of role ID(s) to limit access to different steps or choices, for example:

<step id="xxx" attributes>
    <role>req_role1</role>
    <role>req_role2</role>
</step>

<pure_storage id="start_deposit" key="kind"
value="AA" displayas="Kind" />

<pure_storage id="sxx" key="extra" value="XX">
    <role>admin</role>
    <role>admin2</role>
</pure_storage>

<enter_data id="enter_sid" key="sid" title="Enter SID">
<role>cit</role>
</enter_data>

<enter_data id="enter_txid" key="tx" title="Enter
transaction identifier" extra_text="Additional
message" numeric="true" decimals="0" maxchars="4"
displayas="TX" restart_here="true" />

<?xml version="1.0" encoding="US-ASCII" standalone="yes"?>
<user_field_definitions xmlns="http://www.w3.org/1999/xhtml"
                        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
                        xsi:noNamespaceSchemaLocation="file:custom_data_entry.xsd">
     <deposit start="enter_id" />
     <steps>
           <enter_data title="Enter custom id (AAA123)" key="custom_id" id="enter_id" regex="[A-Z]{3}[0-9]{3}" confirmation="true" confirmation_title="Enter custom id again" retries="2"/>
	</steps>
</user_field_definitions>

<heading>
    <td>#</td>
    <td>Description</td>
</heading>

<choice value="svc">
    <td>1.</td>
    <td>Service</td>
</choice>

In the example below, the user is assigned the permission to select a type from a predefined list of choices. Users with role “xtra” have an additional choice. The selected value is added to custom data as “typ” and is displayed on screen as for example: @ (AA)

<selection id="choose_deposit_type" key="typ" title="Choose
Deposit Type" displayas="@">
    <heading>
        <td>Available types</td>
    </heading>
    <choice value="AA" next="enter_sid">
        <td>Typ 1</td>
    </choice>
    <choice value="AB" next="enter_sid">
        <td>Typ 2</td>
    </choice>
    <choice value="BA" next="enter_sid">
        <td>Typ 3</td>
    </choice>
    <choice value="BB" next="enter_sid">
        <td>Typ 4</td>
    </choice>
    <choice value="XX" next="enter_tx">
        <td>Extra special</td>
        <role>xtra</role>
    </choice>
</selection>

<<source>
  <![CDATA[
  new BigInteger("${uuid}".split('-').last(), 16)
  ]]>
</source>

<script id="1" key="ident"
     <source>
     <![CDATA[
     "http://123.45.67.89:4321?x=${uuid}&u=${userId}".toURL().text
     ]]>
     </source>
</script>

Go to the Receipt Builder Configuration Guide to find information on how to build receipts.

The receipt above has the following information:

The information on a receipt, such as area code, machine ID, machine serial number, and so on, is defined in a properties file named machine.properties. You can edit this file using a text editor.

regional.number=28
rcs.function=S
machine.unique.id=01
machine.name=RCS 800
machine.serial.number=101
customer.name=ICA
customer.number=024171
store.name1=HG:MALMÖ
store.name2=117-GETAF1
store.number=2849

You can add custom logos to receipts.

The logo must meet the following requirements:

It is possible to dispense two or more different mixes to two or more tills with just one Mix selection on screen and with just one receipt. This feature can be used by cashiers to dispense both their till for the cash register and a till with additional change in one single operation. You configure Mix groups in the same configuration file as regular mixes (moneymixes.xml).

physicalcu name value (PUxxx) indicates the hopper position 1A-1D or 2A-2D. See the tables PU001-PU004.

<logicalcu thresholdstatus="LOW" number="3" cukind="DISPENSE"
cutype="COIN_CYL" unitid="00000" initcount="0" count="0"
status="OK" physicalname="PU001" depositcount="0"
dispensecount="0" rejectcount="0" >
    <cashtype kind="COIN" ccy="EUR" value="10" />
    <threshold full="4300" high="4200" low="200" empty="0" />
    <physicalcu name="PU001" unitid="00000" count="0
    " thresholdstatus="LOW" status="OK" >
    <threshold full="4300" high="4200" low="200" empty="0" />
    </physicalcu>
</logicalcu>

Full, default value is high value + 100, the physical limit of the hopper (how many coins it can hold). The denomination is rejected.

Low, default value 200, the desired number of coins left after dispense down to low level.

<logicalcu thresholdstatus="LOW" number="3" cukind="DISPENSE"
cutype="COIN_CYL" unitid="00000" initcount="0" count="0"
status="OK" physicalname="PU001" depositcount="0"
dispensecount="0" rejectcoun
    <cashtype kind="COIN" ccy="EUR" value="10" />
    <threshold full="4300" low="200" empty="0" />
    <physicalcu name="PU001" unitid="00000" count="0"
thresholdstatus="LOW" status="OK" >
    <threshold full="4300" low="200" empty="0" />
    </physicalcu>
</logicalcu>

Prerequisite: This task requires the SET_GLOBAL_ACCOUNTING_DATE permission.

Use Select global accounting date to define a different accounting date than the actual date for a dispense or deposit. The setting affects all users.

Prerequisite: This task requires the SET_SESSION_ACCOUNTING_DATE permission.

Use Session date to define a different date than the current date for a session. The setting expires at logout.

In the com.scancoin.flow.dispense.lv.internal.DispenseFlow file, you can set a global free float limit and a cash draw limit for each denomination. ([installation folder]\resources\configurable\configuration: com.scancoin.flow.dispense.lv.internal.DispenseFlow)

FreeFloatLimit limits the count on the Free float screen.

TillLimit limits the number of coins that fit into cups (RCS 400 only) or cash drawer. For more information, see Device properties.

Defined denominations as exponent value. that is, 50 = denomination of 50 cents,

To use Free Float you need FREE_FLOAT_XX permission.

In the Devices.properties file, you can configure settings for scanning at bag emptying, cleaning and service reminders on screens well as limits for number of coins for each outlet (for sw version 1.7.0 and later [Installation folder]\resources\configurable\configuration\Devices.properties).

MAX_DISPENSE for each outlet is used for distributing coins of the same denomination into different compartments in the cash drawer. It is used for machines with the same denomination in several coin dispensers.

In the example below, a machine is set up with six dispensers of the same denomination, that is, 1 SEK. With the settings in the example, 100x1 SEK are distributed into each compartment.

Without the MAX_DISPENSE limit, all 600x1 SEK would drop down into one of the compartments.

To enable that a new bag must be scanned before being placed in the machine, open the Devices.properties file ([installation folder]\resources\default\configuration\Devices.properties) and set CIMA.1.needsExternalIDWhenEmptying to true.

#Common device properties
# Device properties in static can be overridden here.
#

# Service and cleaning intervals for the CAM
#CAM.1.service_interval_count=1500000
#CAM.1.service_interval_days=180

#CAM.1.cleaning_interval_count=50000
#CAM.1.cleaning_interval_days=4

# Set to true to enable bar code scanning when emptying bag
CIMA.1.needsExternalIDWhenEmptying = false

PERCONTA.1.PU001.MAX_DISPENSE=100
PERCONTA.1.PU002.MAX_DISPENSE=100
PERCONTA.1.PU003.MAX_DISPENSE=100
PERCONTA.1.PU004.MAX_DISPENSE=100

PERCONTA.2.PU001.MAX_DISPENSE=100
PERCONTA.2.PU002.MAX_DISPENSE=100
PERCONTA.2.PU003.MAX_DISPENSE=100
PERCONTA.2.PU004.MAX_DISPENSE=100

An alternative way to scan a barcode when emptying a cash box or bag is to use a number that is incremented by 1 for each box- or bag-exchange.

You need to activate the implementation by setting the containerIdGenerator property to increment in the [installation folder]\resources\default\configuration\Misc.properties] file.

# By default, "external id when emptying" is retrieved from a scanned barcode.
# Another implementation is to use a number that is incremented by 1 for each exchange.
# the id is between 1-99999 and then goes back to 1. Set value to "increment".
containerIdGenerator=increment

In the com.scancoin.device.transportbox file the high and full settings for the transport box is configured (for Connect on-Device, version 1.7.0 and later [installation folder]\resources\configurable\configuration\ com.scancoin.device.transportbox).

Default values are:

If the high level is reached, a warning is displayed in idle mode indicating that the transport box should be emptied.

If the full level is reached and any of the coin hoppers are full, the coin deposit is disabled until the transport box is emptied

Use this procedure to configure supported currencies for bag drop.

Use this procedure to configure the bag size for manual refills.

The work unit permission tool is used to make it easier to manage a group that needs access to the same money mix(es). The unitgroup name is not displayed or printed or stored in the database.

Information about the unitname is shown, printed on the receipt, and is stored in the database.

Example 13. Example

The example shows what a user with access to the work unit permission (WORK_UNIT or WORK_UNIT_NO_CHECK) can see.

The example is based on a flight company. The employee selects the correct flight number and then the money mix for the group (unitname) is dispensed.

Note

If there are more than 12 options (unitname), the options are shown as a scroll list.

You can set a filter on a work unit or work unit group so that only users with certain roles can choose the unit.

Prerequisite: This task requires the EDIT_WORKUNITS permission.

To set the barcode scanner beam to continuous, follow the bar codes in the sequence listed below. The bar codes can also be found in the guide enclosed with the barcode scanner.

Description	Code	Bar code
Start configuration	%$+/3
Continuous/Auto Power ON	%0273
End Configuration	%$+/4
Save Parameters	%$+/0

In the Move coins menu, select Purge and follow the instruction at the display to remove all coins from selected dispensers.

You need to remove coins, for example, at service or when making an inventory of the machine.

A receipt with information about the number of coins in the dispensers, before and after the purge, and dispensed coins is printed.

Article 6 of European Central Bank (ECB) lays down measures necessary for the protection of euro banknotes against counterfeiting and obliges automated teller machine (ATM) operators within the euro area to withdraw from circulation all euro banknotes that they know or suspect to be counterfeit.

This document gives an overview of how PayComplete™ CDS and recyclers handle Article 6 requirements for HCM modules.

ECB Terms of Reference provide details on different note categories:

The basic requirement in the ECB regulations is that category 2 notes must not be returned and it should be possible to report who deposited the note. Category 2 notes are stored in a separate pocket and are never mixed with other notes.

Category 3 notes should not be returned but can be mixed with other notes. For category 3 notes, it should be possible to track who deposited the note if its later found to be false. Category 3 notes are mixed with other notes and are credited to the customer’s account just as if it was an authentic note.

In Connect on-Device, you can configure the flow so that it isn't possible to return notes when they are detected as category 3 notes. When category 2 notes are removed from the machine, a receipt is printed. The receipt contains information about the account/card used for the deposit.

You can activate Article 6 detection for some note devices.

The number, denomination, and value of suspected and detected counterfeits are printed on the receipt and displayed on the screen as:

The time-delay lock operates each time the safe is unlocked. You configure the lock in the units configuration file, for example, resources\static\configuration\com.scancoin.common.device.sds.

You can set three times:

In the example below, the delay time is 60 seconds and the time window to open the lock is 30 seconds. Missing the opening time window results in a new delay period.

The resetSecondsAfterFirstOpen is set to 0. This resets the timer and the previous process is applied as soon as the door is locked.

locktimer.SDS.1.SAFE=delay:60,reset:3,resetSecondsAfterFirstOpen:0

Use the Activation screen to generate a QR code and an 8-digit activation code that you can use to remotely activate machines in Connect. You can skip this step.

Use the activation codes screen in Connect on-Device to scan the QR code or copy the 8-digit activation code that you use to remotely activate machines in Connect. You can cancel this step.

You configure idle timeouts when you want to change how long Connect on-Device should wait for user input before canceling an ongoing operation. You configure idle timeout in the com.scancoin.core.userpref.UserPreference file.

You use lane allocation to associate a till to a work unit, such as a cash register.

The association takes place when you select the work unit and dispense a money mix. No other user can allocate an already allocated work unit.

Work units are sent to Connect when Connect on-Device is restarted. If two work units have identical names, they are identified per the site they belong to.

If Connect is used, the allocation information is sent from Connect on-Device to Connect in a transaction message. The transaction message contains the following information about the allocation:

The allocation information is sent to all the machines on the site the work unit belongs to. When the machines have received information about the allocation, the allocating user can't dispense any additional mixes from other machines in that work unit. The user can still make free float dispenses and deposits on other machines in the work unit.

Transaction messages are saved locally on each machine. If the machine the dispense was made from goes offline, synchronization is lost between the machines on that site and it is possible for another user to allocate the already allocated work unit from another machine. When the machine comes back online, it automatically synchronizes with other machines on that site and the locally saved transaction messages are sent to Connect.

You deallocate a lane to end the association between the work unit and a till.

The work unit is deallocated (closed) when one of the following occurs:

If Connect is used, the deallocation information is sent from Connect on-Device to Connect in a transaction message. The transaction message contains the following information on the deallocation:

The deallocation information is sent to all the machines on the site the work unit belongs to. When the machines have received information about the deallocation, it is possible for another user to allocate the work unit.

The following permissions are related to lane allocation:

For more information, see Permissions A-L and Permissions M–Z.

There are two types of allocation IDs:

You can activate allocation daybreak. Allocation daybreak automatically deallocates a work unit when daybreak occurs. For more information, see Configuring allocation daybreak.

You activate daybreak by setting a flag in the CashComplete\resources\configurable\configuration\Misc.properties file. The activation is valid for the Connect on-Device installation. You configure Connect on-Device.

In certain cases, such as self-checkout points, you may want to ignore allocation daybreak. To ignore daybreak, you set a flag on the work unit. The flag prevents the work unit from being deallocated at daybreak. For more information, see Configuring ignore allocation daybreak.

The files in this table are used for the lane allocation feature.

<allocations>
<allocation id="101" barcode="333101"
/>
<allocation id="102" barcode="333102"
/>
<allocation id="103" barcode="333103"
/>
<allocation id="104" barcode="333104"
/>
<allocation id="105" barcode="333105"
/>
<allocation id="106" barcode="333106"
/>
</allocations>

#Work Unit name (or Id) = Allocation Id + delimiter + allocation date
#Tue May 19 11:19:13 CEST 2020
JK457=Open\u00012020-05-19 11\:19
JK481=Open\u00012020-05-19 11\:19
JK456=Open\u00012020-05-19 11\:19
JK480=Open\u00012020-05-19 11\:19

{
"MESSAGE_TYPE": "Transaction",
"TYPE": "DISPENSE",
"ALLOCATION_ADDED": {
  "WORK_UNIT_NAME": "JK404",
  "BARCODE": "333103",
  "ID": "103"
}
}

{
"MESSAGE_TYPE": "Transaction",
"TYPE": "END_OF_SHIFT",
"ALLOCATION_REMOVED": {
  "WORK_UNIT_NAME": "JK404",
  "BARCODE": "333103",
  "ID": "103"
}
}

{
"TIME_ZONE_UTC_OFFSET": "+02:00",
"SEQUENCE": 0,
"MACHINE_ID": "RMTester",
"MESSAGE_TYPE": "Reply",
"VERSION": "2.00",
"DATE_TIME": "20200519 11:19:13.860",
"REPLY_CODE": 0,
"SETTINGS": {
  "SetWorkUnitAllocations": {
   "JK457": "Open",
   "JK456": "Open",
   "JK481": "Open",
   "JK480": "Open"
  }
},
"UUID": "935c99ef-9cad-4dea-8ee6-362ec40c0662",
"RECEIVER": "1001",
"KEEP_ALIVE": true,
"MESSAGE_SEQUENCE": 2547
}

"SETTINGS": {
  "SetWorkUnitAllocations": {
  }

{
"SETTINGS": {
  "AddWorkUnitAllocations": {
   "JK457": "Open",
   "JK480": "Open"
  }
}

{
"SETTINGS": {
  "RemoveWorkUnitAllocations": {
   "JK457": "Open",
   "JK480": "Open"
  }
}

{
"SETTINGS": {
  "SetUserAllocations": {
   "1234": "Open",
   "4001": "Open"
  }
}

{
"SETTINGS": {
  "RemoveUserAllocations": {
   "1234": "Open",
   "4001": "Open"
  }
}

{
"SETTINGS": {
  "AddUserAllocations": {
   "1234": "Open",
   "4001": "Open"
  }
}

Use user allocation to associate a till to a user, such as a cashier.

The association takes place when you select the user and dispense a money mix. No other user can allocate the same user to a till.

If Connect is used, the allocation information is sent from Connect on-Device to Connect in a transaction message. The transaction message contains the following information about the allocation:

The allocation information is sent to all the machines on the site the user belongs to. When the machines have received information about the allocation, the allocating user can't dispense any additional mixes from other machines on that site. The user can still make free float dispenses and deposits on other machines on the site.

Transaction messages are saved locally on each machine. If the machine the dispense was made from goes offline, synchronization is lost between the machines on that site and it is possible for another user to allocate the already allocated user from another machine. When the machine comes back online, it automatically synchronizes with other machines on that site and the locally saved transaction messages are sent to Connect.

You deallocate a user to end the association between the user and a till.

The user is deallocated (closed) when one of the following occurs:

If Connect is used, the deallocation information is sent from Connect on-Device to Connect in a transaction message. The transaction message contains the following information on the deallocation:

The deallocation information is sent to all the machines on the site the user belongs to. When the machines have received information about the deallocation, it is possible for someone else to allocate the user.

The following permissions are related to user allocation:

For more information, see Permissions A-L and Permissions M–Z.

There are two types of allocation IDs:

You can activate allocation daybreak. Allocation daybreak automatically deallocates a user when daybreak occurs. For more information, see Configuring allocation daybreak.

The files in this table are used for the user allocation feature.

<allocations>
<allocation id="101" barcode="333101"
/>
<allocation id="102" barcode="333102"
/>
<allocation id="103" barcode="333103"
/>
<allocation id="104" barcode="333104"
/>
<allocation id="105" barcode="333105"
/>
<allocation id="106" barcode="333106"
/>
</allocations>

You disable physical cash-level warnings from one, multiple, or all cash units on a device when you want Connect on-Device to ignore that cash-level information when determining whether or not to display a cash-level warning.

By default, a warning is displayed in Connect on-Device if the physical cash level in a cash unit is empty, low, high, or full.

You can disable the cash-level warnings for the following:

You can disable four types of physical cash-level warnings. The options are:

You would typically disable, for example, incorrectly sent cash-level warnings from physical cash units, such as an HCM's physical hoppers incorrect warnings on low cash levels.

When you set the disablePhysical[Empty/Low/High/Full]Warning property to true, Connect on-Device ignores the cash-level warning from the cash unit or units and instead relies on the count and other calculations to determine whether or not a hopper's cash level should generate a warning.

The disablePhysicalLowWarning property does not prevent low-level warnings from being displayed in Connect on-Device. It only ignores the physical cash unit or units when calculating whether or not the conditions for a warning have been fulfilled and a low-level warning should be displayed.

You completely disable cash-level warnings for one or multiple cash units when you don't want Connect on-Device to show the warnings.

These are the statements you need to set to true if you want to completely disable volume-level warnings:

You disable physical cash-level warnings from one, multiple, or all cash units on a device when you want Connect on-Device to ignore that cash-level information when determining whether or not to display a cash-level warning.

You completely disable cash-level warnings for one or multiple cash units when you don't want Connect on-Device to show the warnings.

The LucidPOS interface can handle payments in different currencies by calculating the exchange rates. The POS system sends an amount to be paid to Connect on-Device via LucidPOS. The result of the deposit of different supported currencies is reported back to the POS system. The POS system then calculates the paid amount using its own exchange rates. If the requested amount has been reached, the POS system instructs Connect on-Device (via LucidPOS) to end the deposit and possibly pay out any surplus. This is the preferred way because exchange rates may differ between the POS system and Connect on-Device.

Some POS systems don't have this functionality, so LucidPOS has been extended to accept several currencies during payment and return the correct surplus based on exchange rates.

The exchange rate service always uses a master currency. That is, the currency used for exchange rate calculations. The master currency is specified in the Locality step in in the Connect on-Device Studio wizard.

Exchange rates are stored in the following .xml file: [installation folder]\resources\configurable\configuration\exchangeRates.xml file.

<?xml version="1.0" encoding="utf-8"?>

<exchangerates>

  <mastercurrency currency="EUR">

    <rate currency="SEK">9.3067</rate>

    <rate currency="USD">1.5337</rate>

    <rate currency="DKK">7.4609</rate>

    <rate currency="NOK">7.8764</rate>

  </mastercurrency>

  <mastercurrency currency="SEK">

    <rate currency="EUR">0.1074</rate>

    <rate currency="USD">0.1715</rate>

    <rate currency="DKK">0.8301</rate>

    <rate currency="NOK">0.8611</rate>

  </mastercurrency>

  <mastercurrency currency="NOK">

    <rate currency="CHF">0.2016</rate>

    <rate currency="DKK">0.9292</rate>

    <rate currency="EUR">0.1246</rate>

    <rate currency="GBP">0.099</rate>

    <rate currency="JPY">20.905</rate>

    <rate currency="SEK">1.1665</rate>

    <rate currency="USD">0.1929</rate>

  </mastercurrency>

</exchangerates>

If you use 'external ID when emptying' when you empty a cash box, you must scan or manually enter the code of the new cash box or bag. The code is then associated with the cash box until the next time the cash box is emptied, and you scan or manually enter a new code.

To use enable bar code scanning when emptying, you must edit the [installation folder]\resources\configurable\configuration\Devices.properties file for the device on which you want scanning to be possible.

Text
# Set to true to enable bar code scanning when emptying bag
COMBINED_MEI.1.needsExternalIDWhenEmptying = true
ELECTRUM.1.needsExternalIDWhenEmptying = true
KUAN.1.needsExternalIDWhenEmptying = true
NGENE.1.needsExternalIDWhenEmptying = true
BNECDM.1.needsExternalIDWhenEmptying = true

Optionally, you can use 'Content Removal ID'. In this case, the cash box CONTAINER_ID is automatically incremented the by 1 for the new cash box every time the previous cash box has been emptied. If no previous value exists, the initial value is set to 1. That is, the first exchange transaction has REFERENCE set to 1 and CONTAINER_ID set to 2.

To use 'Content Removal ID', you must edit the [installation folder]resources\configurable\configuration\Misc.properties file. For more information, see Configuring automatic incrementation of CONTAINER_ID.

{
  "MESSAGE_TYPE": "Transaction",
  "USER": {/../},
  "SUB_TYPE": "OUT",
  /../
  "DEVICE_MOVEMENTS": [{
    "DEVICE_ID": "HCM.1",
    "BOX_MOVEMENTS": [{
      "MOVEMENT": [{
        "TOTAL": -1750,
        "REJECTS": 0,
        "VALUES": [/../],
        "TYPE": "NOTE"
      }],
      "RESULTING_CONTENT":[/../],
        "TYPE": "NOTE"
      }],
      "BOX_ID": "AB0",
      "CONTAINER_ID": "100"
    }]
  }],
  "VALUE_BAGS": [/../],
  "REFERENCE": "99",
  "TYPE": "EXCHANGE"
}

{
  "MESSAGE_TYPE": "Transaction",
  "USER": {/../},
  /../
  "DEVICE_MOVEMENTS": [{
    "DEVICE_ID": "HCM.1",
    "BOX_MOVEMENTS": [{
      "MOVEMENT": [{
        "TOTAL": 400,
        "REJECTS": 0,
        "VALUES": [/../],
        "TYPE": "NOTE"
      }],
      "RESULTING_CONTENT": [/../],
      "BOX_ID": "AB0",
      "CONTAINER_ID": "100"
    }]
  }],
  "VALUE_BAGS": [/../],
  "TYPE": "DEPOSIT"
}

{
  "MESSAGE_TYPE": "Transaction",
  "USER": {/../},
  "SUB_TYPE": "OUT",
  "DEVICE_MOVEMENTS": [{
    "DEVICE_ID": "HCM.1",
    "BOX_MOVEMENTS": [{
      "MOVEMENT": [{
        "TOTAL": -400,
        "REJECTS": 0,
        "VALUES": [/../],
        "TYPE": "NOTE"
      }],
      "RESULTING_CONTENT": [{
        "TOTAL": 0,
        "REJECTS": 0,
        "VALUES": [/../],
        "TYPE": "NOTE"
      }],
      "BOX_ID": "AB0",
      "CONTAINER_ID": "101"
    }]
  }],
  "VALUE_BAGS": [/../],
  "REFERENCE": "100",
  "TYPE": "EXCHANGE"
}

You configure a CONTAINER_ID to be automatically incremented by 1 when you don't want to force the user to scan or manually enter a code when emptying a cash box or bag.