Set up DB2Cash Socket
DB2Cash Socket is an ImaCash mode that listens for TCP requests from the POS program on an authorised network. ImaCash receives the connection; the POS client connects to the computer running ImaCash. Configure the cash machine separately.
Preparation and commissioning
- Prepare the connection with the supplier. Confirm the POS client, the Windows computer running ImaCash, its local network interface and an available TCP port agreed with the administrator. Authorise only the necessary sources in the network and firewall; do not expose the receiver to the Internet.
- Select DB2Cash Socket. In Configuration > Integration, choose DB2Cash Socket, the exact selector name. Set up the POS client to connect to the computer running ImaCash and the same port. Confirm the cash machine and currency separately.
- Save the configuration. When closing, confirm saving if prompted and follow the proposed restart where applicable. Saving prepares the listener; an open connection does not prove that a request has been recorded or a sale has been paid.
- Check the complete workflow. Before commercial use, agree on a supervised test of the sale reference, terminal, salesperson, amount, sign and payment method. Compare the outcome in ImaCash, the POS and actual cash. The supplier must coordinate and check each source; connecting one workstation does not validate simultaneous use by several POS terminals.
Listening address and port
- Server IP
- Enter the IPv4 address of a local interface on the computer running ImaCash, supplied by the administrator. This is not the cash machine address or the address of a remote POS. This field does not accept a URL or server name.
- Server port
- Enter the available numeric TCP port agreed with the administrator and supplier. It must match the destination set in the POS client. There is no universal port for every installation.
Leaving the address empty makes the listener cover all IPv4 interfaces on the computer. Specify the authorised local interface and restrict connection sources with the administrator.
Reception and payment require separate checks
This profile sends the POS neither a request acknowledgement nor a final payment or cancellation confirmation. A local confirmation or rejection does not write that closure to the source program either. Agree with the supplier on reconciling the outcome; the absence of a response proves neither payment nor rejection.
Payment methods and scope
Card handling depends on the type sent and Accept cards. An unknown type or a card with this option disabled is not added as a sale; classifying an operation as card does not prove bank payment. The profile does not import product, salesperson, store or terminal catalogues, shifts or bank totals. The supplier must confirm mixed payments and refunds.
Waiting does not authorise another payment
The profile receives new requests and does not retrieve sales by date. Resynchronising does not rebuild lost requests, and retaining a reference does not guarantee prevention of all duplicates. If there is a wait, disconnection or uncertain outcome, review the operation in the POS and ImaCash and check the cash before resending, restarting or opening another sale.
Installation validation
This guide describes the profile; it does not establish universal compatibility or physical validation. The supplier must confirm the POS, client, equipment and workflows before commercial use. DB2Cash DLL is a separate profile whose instructions do not replace those for Socket.