Set up diTPV
ImaCash reads orders from Diakros diTPV through SQL Server. The supplier must confirm the installed edition, active database and authorised access. Configure the cash machine separately.
Preparation and commissioning
- Prepare access with the supplier. Confirm the SQL server, active database and a private account with read permission for this integration. Check access from the Windows computer running ImaCash; do not expose the database or its credentials to the Internet.
- Select diTPV. In Configuration > Integration, choose POS and then diTPV, the exact selector name. Complete the four fields using the details supplied by the administrator.
- Save the configuration. When closing, confirm saving if prompted and follow the proposed restart where applicable. Saving prepares the connection; the connection indicator alone proves neither correct order retrieval nor payment.
- Check a complete order. Agree on a supervised test with the supplier: reference, date, company, terminal, operator, amount, sign and payment method. Compare the outcome in diTPV, ImaCash and actual cash. In Settings, check terminal and operator filters against the names used by the installation.
Private SQL Server details
- Field “Server IP”
- Enter the SQL Server destination confirmed by the administrator, including the instance where applicable. This is the diTPV database server, not the cash machine address. Do not invent a port or change working access.
- Field “Database name”
- Enter the exact active database name supplied by the provider. This is not a folder, sales file or DSN; there is no universal name for all installations.
- Field “User”
- Use the private SQL account authorised to read this integration. This is neither the cashier nor the Windows account; there is no public setup username.
- Field “Password”
- Enter the private password for that account only in ImaCash. The administrator supplies it; it is not available in this guide and must not be shared in screenshots.
Reading and closure require separate checks
The query includes recorded and open orders from the synchronisation date. Seeing an order does not prove it is paid or closed. A local confirmation or rejection writes neither confirmation nor cancellation to diTPV; agree with the supplier on reconciling both programs.
Terminals, operators and payment methods
Terminals come from recorded orders and operators from the supplier’s catalogue; they are not the cash machine. The amount comes from the order total and the payment method is inferred from its sale type. Confirm cash, card, mixed-payment and refund mapping: a breakdown by payment method is not guaranteed. Accept cards does not prove bank payment. Products, shifts and bank totals are not imported.
Review the scope before resynchronising
Reading again by date does not establish a complete history or authorise another payment. Also review the transition from an open to a recorded order. If the outcome is uncertain, compare diTPV, ImaCash and the cash before resynchronising, repeating an operation or restarting.
Installation validation
The supplier must confirm the installation’s version, structure and permissions and check the workflows before commercial use. This guide does not establish universal compatibility or physical equipment validation.