Resta3

Set up Resta3 with ImaCash

Resta3 connects to ImaCash through its Firebird database. Prepare access with your Resta3 administrator before completing the fields.

Setup steps

1. Ask your Resta3 administrator for the Firebird server, TCP port, authorised read account and exact path of the active sales database. There is no confirmed universal filename.
2. In ImaCash open Configuration > Integration and select POS > Resta3.
3. Server IP: address of the computer running Firebird for Resta3. If the database is on another computer, use that server address.
4. Port: TCP port configured for the Firebird service. Have the provider confirm it; do not infer it from the initial value displayed by ImaCash.
5. Password: Private information provided by the administrator. Enter it only in ImaCash.
6. Transactions: enter the full path of the active database as it exists on the Firebird server. An alias configured and verified by the administrator on that server may also be used. IP and port have separate fields: do not add them to this path.
7. Close configuration and select Save. The check opens and closes the connection; it does not validate sales capture or a cash machine operation. Use the restart button when ImaCash requests it.

Which file to select in Transactions

This example is fictional: replace it with the confirmed path for your installation.

C:\DatosPOS\Ejemplo.fdb

If Firebird runs on another computer, locate the file on that server. The file picker shows the ImaCash computer; a remote database may require entering its path manually. Do not copy the database to the POS computer to connect.

Firebird databases commonly use .fdb or .gdb, but an extension or file size does not identify the active Resta3 database. The provider must confirm the file and Firebird service access.

Select the database, not a folder, backup, installer or configuration file. security.fdb, security2.fdb and security3.fdb contain Firebird users, not sales. Commented examples in aliases.conf and trace configuration do not identify a real database.

Integration scope

Capture reads sales from the synchronisation date and accepts those classified as cash by the source. Card transactions, products and shifts are not captured.

The query applies the salesperson filter. Before sharing one database across tills, confirm terminal isolation with support: the terminal catalogue alone does not establish that filtering.

Confirming or rejecting in ImaCash does not update the sale status in Resta3. Check the outcome in both applications during supervised commissioning.

The provider must confirm that the installed edition has the structure used by the connector. An open connection does not establish compatibility with every edition or a physical machine result.

This guide describes the Resta3 selection. If your previous configuration says Resta3 V2, check the mapping with support before changing it: the name alone does not guarantee that both variants use the same structure.

If connection fails or sales do not appear

Check server, port, credentials, path or alias, service permissions and active database with your Resta3 administrator. SERVIDOR may identify the destination without the file; firebird.conf may identify the port. An empty aliases.conf does not reveal the path. Do not create an empty database to fill the field.