Ontopsys

Integration modes

Choose the mode that matches your installation. Confirm the connector and its requirements with the provider before changing the setup.

• Automatic payment capture
• OntopsysEan

Ontopsys: automatic payment capture

The Ontopsys profile reads payment records from SQL Server. OntopsysEan uses a separate query requested by code. Choose the profile agreed for your installation; a successful connection does not prove a payment or compatibility with every edition of the program.

1. From Main, open Configuration > Integration, select the POS category and the Ontopsys profile. The corresponding permissions to view and modify Configuration are required.

2. Private connection details

   • IP: The SQL Server destination confirmed by the POS administrator. Do not discover servers or access details by trial and error.
   • Database name: The active database ImaCash must read; this is not a DSN.
   • User: A private account with the read permissions this integration needs.
   • Password: Private information provided by the administrator. Enter it only in ImaCash.

3. Windows authentication

   This option is available in Ontopsys, not OntopsysEan. Use it only if the administrator has prepared access for the Windows account running ImaCash; signing in as someone else does not establish that access.

4. Save and check

   Close Configuration with X and review the choice to save, keep editing or leave without saving pending changes. Saving happens in phases: discarding pending changes does not reverse phases already saved. An accepted connection only checks access; then compare the document, date, sign, amount and workstation with Ontopsys.

Which operations appear

Automatic reading accepts certain cash and card records. Card capture depends on it being enabled and does not confirm the payment terminal’s result. Do not assume a complete split-payment breakdown or that refunds follow the same path as payments.

Filters and period

Workstation and seller lists help identify the data. User filters limit the local ImaCash view and do not isolate global POS capture. The query applies date and time conditions; it does not guarantee recovery of the full history. Check the period and references before repeating a read.

Confirm or reject in ImaCash

These actions do not write a confirmation or cancellation to Ontopsys. Check the document in the POS and the device’s actual result before repeating, resynchronising or restarting an operation with an unclear outcome.

Integration scope

There is no exchange of items, stock, shifts or an independent banking total. The administrator must confirm the compatible edition and data structure and validate each intended workflow in the installation. This guide does not establish a physical test.

General Configuration and saving workflow

Official Ontopsys de México website

OntopsysEan: look up a sale by code

This profile does not capture sales in an automatic loop. It looks up a reference when requested by the EAN input configured in ImaCash.

1. In Configuration > Integration > POS, select OntopsysEan and complete the same four private SQL Server details. This profile uses the SQL account; there is no Windows authentication option.
2. Save through the closing workflow and check the connection. Ask the provider which exact reference the sale’s code must contain.
3. Read the code through the configured EAN input. A lookup by folio includes a current-date condition; recovery of old documents is not guaranteed.
4. Before taking payment, compare the displayed reference, date and retrieved amount with the Ontopsys document. This query presents the operation as cash; it does not prove the sale is paid or that its amount matches the total you expected.

There are no seller, workstation or shop catalogues, or automatic card reading. Confirming or rejecting does not modify the Ontopsys document either.

Private connection details and saving

General Configuration and saving workflow

Official Ontopsys de México website