Set up Cuiner with ImaCash
Cuiner provides sales and management software for hospitality. With this connection, Cuiner sends operations to a TCP listener opened by ImaCash. The technician prepares both ends and configures the cash device separately.
Prepare and save the connection
- Confirm the Cuiner edition, exchange interface, currency, amounts, operation types and identifiers with the provider. Use a private network and authorise only the required computers; do not expose this listener to the Internet.
- In ImaCash, open Configuration > Integration and select POS > Cuiner. This mode shows Server IP and Server port; it does not request a database, username, password or sales file.
- In Server IP, enter the private value confirmed for listening on the computer running ImaCash. The administrator must check that it is valid on that computer; do not copy another server address or an old screenshot.
- In Server port, enter the local TCP port agreed with the technician. Cuiner must send its operations to the destination prepared in ImaCash. The port must be available and allowed by the network policy; no universal value has been validated.
- Close the configuration and choose Save in the changes prompt. The check may open the TCP listener: do this with the technician and with no pending operations. Review the result and use the restart option shown by ImaCash only when appropriate. Saving does not prove that Cuiner has exchanged an operation.
- Before commercial use, the technician must supervise the complete flow from Cuiner through ImaCash and the device to the result in Cuiner. Confirm receipt and completion of the same operation; this guide does not certify a physical test.
What to check during use
The connector receives new operations while their connection is available. It does not retrieve past sales by querying a date, or provide product catalogues, shifts or a bank card total.
The terminal, operator and operation type come from the data sent by Cuiner. The provider must confirm their mapping, amounts and signs. Do not assume a card or mixed-payment breakdown, or integration with other Cuiner modules simply because they share a brand.
Confirmation or cancellation requires the connection that originated the operation to remain available. A sent response alone does not prove that the POS has saved the result or closed the document.
Rejecting an operation locally does not confirm its cancellation in Cuiner. If the outcome is uncertain, review the operation and actual cash with support before repeating, resynchronising or restarting.
The Cuiner edition, version and interface and the installed cash device must be validated for each installation. This setup does not establish compatibility with every edition or device.