Set up Loomis Pay with ImaCash
Loomis Pay is the commercial name; the ImaCash profile is called LoomisPay. It receives operations through a local API and uses an exchange database. It is separate from the Cloud REST API, and a Loomis name alone does not establish terminal compatibility.
Before configuration
Ask the provider for the supported version and mode, exchange destination, read and write permissions, HTTP port and a dedicated private token. The connection creates or updates exchange data: read-only access is insufficient. Keep a backup and review pending operations before changing the destination.
- Open Main > Configuration > Integration and select POS > LoomisPay with Configuration permission. POS is the selector group; it does not change the listing’s commercial category.
- Enter the private installation details in Server IP, Port, Database name, User and Password. Port refers to the database. Do not copy screenshot values or change ImaCash’s database mode to try to establish a connection.
- Service name takes the exchange HTTP server port, separate from the SQL port. Agree it with the provider; it is neither a Windows service name nor a timeout.
- This profile reuses the terminal field (Puestos in Spanish) for the private Bearer token. Enter the value agreed with the provider, who must configure the same token in the sender; do not enter a list of tills or the SQL password.
- When leaving with pending changes, choose Save in the prompt and review the checks for each phase. Continue editing returns to the form; Exit without saving discards pending changes without undoing phases already saved. A connection indicator does not prove POS delivery, a payment or a refund.
Connection scope
Depending on the Windows context, the server may be accessible only from the same computer. Confirm the necessary network scope with the responsible administrator. The token authenticates requests but does not encrypt HTTP: do not expose this service to the Internet or reuse keys from other systems.
What is exchanged
The profile receives one operation per request, provides status queries and accepts cancellation requests. The sender must confirm the reference, date, till, cashier, company, type and sign of the amount in cents. Do not assume batches, cards, mixed payments or every refund type; agree and check the specific flow.
Dates and filters
Reading searches for pending operations from the inclusive date and time. Till, company and cashier filters need values consistent with the sender; opening a filter does not validate its lists or isolation from another till. Resynchronisation does not rebuild a complete history.
Result and cancellation
Acceptance confirms that a request was recorded, not that cash was delivered. A query reflects the exchange status; a requested cancellation does not prove a refund or cancellation of the document in Loomis Pay. Check both programs and the actual cash before resending, repeating or restarting after an uncertain result.
Limits and verification
This profile adds no items, stock, shifts, machine inventory or independent bank total. Confirm the version, mode and a supervised physical test before commercial use; this guide does not establish compatibility with every Loomis Pay device or service.