Set up EanConti with ImaCash
EanConti is the ImaCash profile name for the ticket format prepared by the provider. Confirm the installation and supported operations before use; configure the cash machine separately.
Prepare the installation
The provider must confirm the code format, cashier identifier, complete notification service address and authorization requirements. Check access under the actual ImaCash Windows user. Supply details through a private channel, without copying examples or screenshots.
Select the profile
Open Configuration > Integration, select POS and then EanConti. The Retail category in an old screenshot does not replace the current selection.
Complete the private fields
Database name takes the confirmed cashier identifier, not an SQL database. Stations takes the complete service address prepared by the provider, not a station list. Port is a legacy label: it is not a TCP port and does not prove that authorization data is applied to the request. Review this requirement with support before commercial use; there are no universal values.
Save when closing
Close Configuration and confirm saving when prompted. Follow any proposed restart when applicable. Saving or seeing a connected indicator does not check the service, its authentication or receipt of a notification.
Read the prepared ticket
The profile interprets a specific eighteen-position format containing a reference and amount; length alone does not validate it or make it a generic retail EAN. Keep leading zeros. An accepted scan can start a cash operation in the main workflow: check the ticket, reference, amount, sign and currency before scanning. It does not prove a bank payment or a breakdown of card or mixed payments.
Check the outcome
When confirming an operation that was not canceled, the profile attempts to notify the service. Local confirmation does not prove that the source recorded it; a local cancellation does not send a cancellation to the service. Check both systems and the actual cash before scanning again, resending or restarting when the outcome is uncertain. No history query by date, product catalog, shifts or bank total is validated. This guide proves neither absence of duplicates nor physical validation.