Configure Gesmabit with ImaCash
The Gesmabit profile reads payment records from a MySQL database prepared by the provider. The brand identifies the product; it does not establish support for every edition, app or combination of cash devices.
Gesmabit information on the provider’s website
1. Prepare access
Ask the provider to confirm the supported edition, structure and active database. The administrator supplies the destination and a private read account with the necessary permissions for payment records and their lists. Do not use a shared administrative account or create an empty database as a substitute.
2. Select the profile
Open Settings > Integration, choose POS and select Gesmabit. Configure the cash device separately. This profile queries MySQL; it requires neither a DSN nor an exchange folder.
3. Enter the five private settings
Server IP takes the MySQL destination; Port, the confirmed numeric port; Database name, the active database; User and Password, the private read account. The administrator supplies every value: there is no universal port, database name or account. Do not publish them in screenshots or documents.
4. Save when closing
Close Settings and confirm saving when prompted; follow the proposed restart if applicable. Startup attempts to connect to MySQL. Saving, ping or a connection indicator does not establish authentication, permissions, complete reading or payment.
5. Check the date and documents
Reads payments from invoices and delivery notes not yet exported, starting at midnight on the selected day, inclusive; the time does not limit this reading. Check reference, amount, sign, currency and date. A paid flag at the source is not proof of cash delivered. Check that a delivery note becoming an invoice does not process the same operation twice; do not assume complete history or references that can always be recovered.
6. Check filter scope
Terminal, user and company lists do not prove that filters limit the query. Confirm with the provider how names and identifiers correspond and which records actually enter. Do not use that selection to isolate tills or companies: access must be limited to the authorised database and scope.
7. Confirm payment methods
The provider must confirm which codes mean cash and card; this profile has no payment method selector. A card classification does not establish bank authorisation or mixed payments. Products, shifts and a bank total are not provided.
8. Check the actual result
Confirming or rejecting in ImaCash does not write a closure or cancellation in Gesmabit. Validate both systems and the cash device through a supervised test. If the result is uncertain, check the operation and actual cash before repeating, resynchronising or restarting. A connection or this guide does not establish physical validation.