Set up JumpSystem in ImaCash
This guide covers the JumpSystem profile in ImaCash. It connects through SQL Server; the provider must confirm that your installed edition and database support the exchange expected by this profile.
Before setup
Ask the JumpSystem administrator for the server address, database and a private SQL account with the required read access. They must prepare the service and check connectivity from the ImaCash workstation. Keep these details out of public material and screenshots. The profile name or a successful connection does not establish compatibility with every edition.
Setup steps
- Open Configuration > Integration using the identification and permissions required by your installation.
- Under Management software, select the POS category and then JumpSystem. Retail is the commercial classification of this page and also appears in the historical screenshot; the current selector uses POS.
- Enter the private address confirmed by the provider in the server field. The profile checks host reachability and then the SQL connection. Do not enter a web URL or assume a universal port: there is no separate port field, and the format must work with that installation.
- In Database name, enter the exact active database name supplied by the administrator. This field does not take a folder or an ODBC DSN.
- Fill in User and Password with the private SQL account supplied. Confirm its permissions with the administrator, without using published credentials or example values.
- When closing Configuration, choose Save to apply, Exit without saving to leave pending edits, or Continue editing to review them. Reopen the configuration and check the values actually saved.

What Save checks
Saving checks server reachability and opens the SQL connection; it does not take a payment or establish that the transaction query is compatible. Some data is persisted before the connection check: a later error or Exit without saving must not be treated as restoring previously saved values. Reopen the screen to check the result.
Operations and filters read
Reading starts at the specified date and time, including that instant, and selects only the payment criterion expected by this exchange. It does not automatically import all payment methods. Terminal filters use POS device names, and salesperson filters use its active users. The Shops list does not establish a separate shop filter: this reader applies terminal and salesperson filters. Confirm references, terminal identification, currency, sign and amount units; amounts use two decimal places with no automatic conversion from cents. Resynchronising reads again and does not guarantee a complete history or no duplicates.
Confirmation and exchange scope
Confirming or rejecting an operation in ImaCash does not write its payment or cancellation status to JumpSystem. This profile does not import products, stock, EANs or POS shifts and provides neither an independent bank total nor a payment-method catalogue. A read record alone does not establish a card payment, split payment, refund or physical outcome.
If the outcome is unclear
Compare the order reference in both programs and the actual cash before repeating, resynchronising or restarting. Do not use Save or a new read to force another payment. If the query fails or amounts differ, keep the outcome pending and ask the administrator to review the exchange setup.
Checks before use
The provider must confirm the edition, exchange format and payments to be read, and supervise a test of the full workflow. The HuiBaiTech logo comes from material supplied for this profile; it does not by itself establish the provider’s legal identity or compatible editions. This setup guide is not physical validation of an installation.