ImaCash integration

Coaliment

Coaliment integration with ImaCash through Oracle or Access. Configuration, data location and access requirements.

Coaliment logo
POS

Coaliment configuration

In Configuration → Integration, select POS and Coaliment. Choose Coaliment Oracle for an Oracle POS; keep Coaliment for the legacy Access mode.

Coaliment Oracle: connection to the sales database

  1. Look next to Tpv.exe in the POS folder (for example C:\Caixa02\tpv) for a file such as XE.ora. Its name identifies the SID: XE. This file does not contain sales and is not selected as a database.
  2. Enter the server IP, port, Oracle SID, user and password. Private information provided by the administrator. Enter it only in ImaCash. and 1521 are initial values for a local installation and must be confirmed by the supplier. Use the server address if Oracle runs on another computer. Enter the SID without .ora.
  3. The supplier or administrator must provide a private read-only account with access to sales and payment methods. Do not copy passwords from POS DLLs. ImaCash includes the managed Oracle provider; this option does not require Access or an MDB file.
  4. Save the configuration and check the connection and receipt of an agreed test sale with the POS administrator before production use.

Coaliment with Access: legacy mode

  1. Sales Access file: Select the active .mdb or .accdb sales file specified by the supplier. Do not select Clientes.mdb from a Backup folder: it is a customer backup. If XE.ora is next to Tpv.exe, check the Coaliment Oracle option.
  2. Password: Private information provided by the administrator. Enter it only in ImaCash.
  3. Save the configuration and check the connection and receipt of an agreed test sale with the POS administrator before production use.

Requirements

  • The ImaCash computer needs 32-bit Microsoft ACE OLEDB 12.0 compatible with the POS Access database. The provider must confirm the database version and structure.
  • The Windows user must be able to read the active database and access its folder. The administrator must allow the shared locking permissions required by Access and ensure availability when using a network path.

Scope

Oracle mode captures closed cash sales and cash refunds. For split payments it captures only the cash portion; cards, credit and cancelled tickets are excluded. Access mode keeps its previous cash-sales contract.

This connection reads sales and does not confirm or cancel tickets in the POS. Coordinate with the supplier to prevent the POS sending the same payment to another machine controller. Check the connection and run a supervised test before production use.

Integration ready to move forward

If this integration matches your software, the next step is moving into real operation

We can help you validate the scope, confirm compatible hardware and prepare the next implementation step.