ATM Hospital

Set up ATM Hospital with ImaCash

In ImaCash, this integration is selected as ATM. It connects to the SQL Server database prepared by the provider to read operations and report their confirmation or rejection.

Step-by-step setup

1. Ask the administrator for the SQL Server destination, database and a private account authorised to read the exchange and update its statuses. A read-only account does not cover the whole link. The provider must confirm the available edition and schema.
2. Open Configuration > Integration, select the POS category and then ATM. This profile has Server IP, Database name, User and Password fields.
3. Enter the SQL Server destination confirmed by the administrator and the exact database for that installation. Do not reuse addresses or names from other computers. This profile has no port field or Windows authentication checkbox; if the server requires an instance, confirm the full destination with the provider.
4. Enter the User and Password of the private SQL account supplied for this integration. Keep only the permissions required to read and update the exchange; do not use a shared administrator account or publish its details.
5. Save using the Windows account that will run ImaCash and follow any prompt to reopen it. A network check or a result when saving does not prove full read/write access or a cash operation.
6. With the provider, compare operations, amounts, dates, terminals and sellers, and check that confirmations and rejections reach the intended exchange. Verify the final result in both applications and the cash machine before normal use.

Payments, filters and scope

This profile presents the operations it reads as cash. The general card option does not establish a breakdown of card or mixed payments or change from the source. The provider must confirm which operations it prepares for this link.

Terminals and sellers are read from the source and can restrict capture; also review ImaCash display filters. Check the actual identifiers before filtering. A hidden operation does not prove it was not received.

The link does not import products or shifts. Resynchronisation depends on exchange dates and records and does not prove complete historical recovery. Reporting confirmation or rejection to the source does not by itself establish fiscal closure, a refund or stopping a physical cash payment.