Set up Gesden G5 with ImaCash
This guide covers the ImaCash Gesden profile for a supplier-confirmed G5 installation. Infomed distinguishes desktop G5 from Gesden ONE; this page does not validate ONE, every edition or every device combination.
Product information from Infomed
1. Prepare access
Ask the administrator for the complete SQL Server destination, active database and required read permissions on payments and users. The supplier must confirm edition, structure, network and installation scope. Do not use a shared administrator account or create an empty replacement database.
2. Select the profile
Open Settings > Integration, choose POS and select Gesden. Configure the cash device separately. This reader queries SQL: general file fields do not set up folder exchange.
3. Enter destination and database
Server IP takes the complete confirmed SQL destination, including its instance when applicable; Database name takes the active database. Instance name remains visible, but filling it separately does not replace the SQL destination in the first field. There is no separate port or DSN. Confirm these details with the administrator and keep them out of public screenshots and documents.
4. Choose authentication
With SQL authentication, User and Password take the administrator-provided private read account. If the supplier prepares Use Windows authentication, the actual Windows identity running ImaCash and its permissions are used; SQL account fields are disabled. Do not remove protection or share credentials for testing.
5. Save when closing
Close Settings and confirm saving when prompted; follow the suggested restart if applicable. Startup attempts to open and close SQL. Saving, ping or a connection indicator does not validate authentication, permissions, complete capture or payment.
6. Check captured payments
Capture starts at the synchronisation date and time, inclusive, retrieving payment reference, amount, date and user. The profile expects method 2 for cash and 6 for card: the supplier must confirm these mappings. There is no payment-method selector to discover them. Check currency, sign and refunds; card classification does not prove bank authorisation or split payments.
7. Verify users and filters
The list shows login names. With the supplier, check which user and reference actually enter capture when filtering and compare their identifiers; a list does not prove correct mapping. Fixed workstation and company values do not establish multiple tills, centres or isolation. Workstation or shop catalogues, items, shifts and bank total are not provided.
8. Check the actual outcome
Confirming or rejecting in ImaCash does not write a closure or cancellation in Gesden. Check both systems and the device in a supervised test, without actual patient data in examples. Do not assume complete history or duplicate-free resynchronisation. If the result is uncertain, check the operation and actual cash before repeating, resynchronising or restarting.
Historical configuration screenshot
