To integrate AhoraTPV with ImaCash, an active module from Ahora TPV is required to enable communication between systems. Once it is active, the technician must complete the connection details.
Steps to follow
1- Open the integration configuration:
- In ImaCash, open Configuration > Integration > AhoraTPV.
2- Select the POS system:
- Select the POS category, in this case Retail.
- Then select AhoraTPV from the dropdown menu
3- Complete the connection details:
- Web URL: enter the base URL with the service's exact protocol, http:// or https://, and the verified host. Do not include a port, trailing slash, /api/Imacash paths, parameters, username or password.
- Port: enter the service's actual port separately. Example: Web URL https://192.168.1.20 and Port 8443, only if this is the authorised HTTPS endpoint.
- User: an account authorised by AhoraTPV for the ImaCash module, with permission to query and confirm transactions.
- Password: this account's password, in its dedicated field only. Never include credentials in the URL or share them in screenshots or logs.
- ImaCash ID: the identifier assigned to this installation in AhoraTPV. It corresponds to the internal Puestos field and must match the value configured in the AhoraTPV module.
4- Save the configuration:
- Click the Save button (disk icon) in the lower left corner
Prerequisite: AhoraTPV's ImaCash module must be enabled. Confirm the protocol, host, port, authorised account and ImaCash ID with its administrator before saving.
HTTPS, certificates and redirects
ImaCash 4.4.3.1263 accepts private or self-signed certificates exclusively for AhoraTPV's local or private HTTPS endpoint. This exception does not apply to public servers or disable certificate validation globally. It does not automatically switch from HTTPS to HTTP when TLS fails.
ImaCash 4.4.3.1264: build validated; release availability still to be confirmed. It blocks redirects from HTTPS to HTTP, to another host and to another port within the same protocol. It allows HTTP to HTTPS on the same host and preserves local HTTPS. Do not assume 4.4.3.1263 provides this additional protection; check the installed version and release availability before updating.
A TLS failure or rejected redirect does not prove that the password is incorrect or require changing the AhoraTPV service. For local certificates, configure the verified final HTTPS URL and its port directly, without relying on redirects.
If a redirect points to another host, first verify the destination's identity and authorisation with the AhoraTPV administrator. Explicitly configure its final base URL and port in ImaCash; do not send credentials to an unverified destination or add a username or password to the URL.
When ImaCash fails, do not disable Windows security, antivirus, the firewall or global TLS validation, and do not modify the server to work around a client defect. Check the version and connection settings first. Configure HTTP explicitly only if it is the actual authorised protocol, never as an automatic fallback for an HTTPS error.
Checks before production
From the ImaCash computer, verify access to the authorised host and port; save the configuration and confirm successful login and loading of users and tills. If this fails, check the enabled module, ID, credentials and sanitised diagnostics without disclosing passwords or tokens.
In a controlled test, check that a sale is received and its status is returned to AhoraTPV. The integration queries transactions and confirms completion, error or cancellation through PUT /api/Imacash/transaccion; only an HTTP 2xx response confirms that submission. A timeout or HTTP error does not prove confirmation: check both systems before repeating a cash operation. This documentation does not replace validation at the actual installation.
