Setting up Cashmatic in ImaCash
Before setup
- The provider must enable the Cashmatic HTTPS API and privately supply the address, port and authorised account. Confirm permissions for queries, payments, cancellations and withdrawals; there is no universal port or set of credentials.
- The computer requires .NET Framework 4.7.2 or later. Use a certificate valid for the configured address or a SHA-256 fingerprint confirmed by the provider through a trusted channel. Do not automatically accept the received certificate or disable verification.
- Dedicate the device to this ImaCash instance. Do not start cash movements from another application or Cashmatic administration while ImaCash is using it: service cancellation does not provide a lock against simultaneous third-party commands.
Steps in ImaCash
- Open Configuration → Machine and select Cashmatic. The connector is available in the beta channel; confirm the version and installation with the technical administrator.
- Enter the device or service address specified by the provider, the HTTPS port, private username and password. Do not confuse that address with the ImaCash computer address.
- In HTTPS certificate (SHA-256), leave the field blank if the certificate is already valid, or enter the authorised fingerprint of the device certificate. This field is not a folder or file.
- Choose the currency configured on the device. The selector accepts currencies with two decimal places; appearing in the list does not prove support by the model or firmware.
- Save and check the connection with the device idle. Information, status and inventory are read without starting a cash movement. A failed reading does not mean zero inventory or prove the complete payment cycle.
Beta connector functions
Includes manual and integrated payments, cancellation of an owned payment before the target amount is reached with a fully confirmed refund, refunds, withdrawals by amount, and recyclable and total inventory. The result requires confirmation of the owned operation, cash in and out, and completion; an acknowledgement or returning to idle is insufficient.
Refills, denomination changes, emptying, opening, free deposits, continuous acceptance and denomination selection are not enabled. Cash breakdowns are not reconstructed from inventory differences.
If the result remains pending
After communication loss, incomplete dispensing or a result that cannot be identified, review the operation and cash with the technical administrator. Do not repeat a payment, refund or withdrawal as a test, or restart to unblock it. The in-memory review is not persistently recovered between processes.
Model and commissioning
Before commercial use, the provider must confirm the model, firmware and API, including reference-based queries for an operation that is still active. A supervised test must then cover exact payment, change, cancellation, refund, withdrawal and communication loss, comparing physical cash and history. This guide and software tests do not establish certification or physical validation of a model.