Set up DibalEAN
DibalEAN obtains the amount from a ticket code prepared for this profile. The reader must preserve the complete code; the supplier confirms the template and installation currency.
Preparation and commissioning
- Prepare the installation. Ask the supplier for a test ticket with the expected format and amount. Confirm the reader, currency and handling of leading zeros.
- Select the profile. In Configuration > Integration, choose POS and then DibalEAN. This profile requires no additional server, SQL account, port or folder.
- Save the configuration. When closing, confirm saving if prompted and follow the proposed restart where applicable. Saving checks neither a scan nor a payment.
- Check the workflow. Before scanning, review the printed amount and currency. An accepted scan may start cash handling directly. Agree on a supervised test and compare the displayed amount and actual outcome before continuing.
Ticket code format
Use the specific 13-digit numeric format with an embedded amount. That length proves neither the template nor full ticket validation. Do not truncate or pad codes; product EAN scanning or QR links do not replace this format.
DibalEAN scope
The profile interprets the amount in the code without checking the ticket’s POS status. It does not retrieve sales by date or import products, terminals, operators, shifts or bank totals. Confirm refund and other payment workflows with the supplier.
Scanning does not confirm source payment
Recognising the code does not prove whether the ticket is pending, paid or closed. Local confirmation or rejection does not update Dibal; agree on checking and reconciling both applications.
Before scanning again
Repeating a code may create another operation. If the outcome is uncertain, review the ticket, ImaCash and actual cash before scanning again or restarting. Do not use a second scan to find out whether the first completed.