You have built and tested the integration in the integration environment. Before you deploy it at a business, go through this list. Each item links to the article that explains it.
Environment and storage
- A real storage instead of In-Memory. In production eKasa runs with a CHDÚ storage (CHDU Lite, CHDU-SK or SwissBit); In-Memory forgets receipts after a restart (Storage and hardware).
- Production initialization package. The storage holds the business’s identification and authentication data for
its real cash register code, not the integration set
888123456…(Initialization package). - Environment from the data. Let the environment be determined automatically from the identification data, so a production cash register is not sent to the integration environment (Invalid data message signature).
- A valid certificate. Authentication data are valid for 2 years. Check that the certificate is valid and has enough time left (System status).
Receipt and printing
externalIdon every receipt. Without it, the same sale is recorded twice when a response is lost (Duplicate protection).- Print test on the real printer. Print a receipt and a copy, check diacritics and the layout of your own texts (Encoding and special characters, Printer info).
- Cash rounding. For cash payments send
roundingAmount(Payments and rounding). - Cancellation and returns. Try a cancellation and a return of goods with a reference to the original receipt (Cancellation and returns).
Result handling
- Three registration results. Your software tells apart
isSuccessfultrue,null(offline) andfalse(rejected) and shows the cashier what happened (Registration result). - Do not send an offline receipt again. With
nullthe receipt is registered and printed; eKasa sends it by itself (How eKasa works). - Printing error. With
-502: PrintReceiptErrorthe receipt is registered: print a copy for the customer, or cancel the receipt and issue a new one. - Your software’s timeout. When it times out, repeat the receipt with the same
externalId, not as a new one (Duplicate protection).
Status checks
- Status at start and regularly. Your software checks the eKasa status when it starts and then regularly, and warns the cashier about problems (System status).
- Queue of unsent messages. Data messages must be sent within 96 hours. The cashier should know that something is waiting in the queue (System status).
- Paper and storage. Show the cashier a low paper roll and a filling storage in time.
If you use them
- QR payments. The settings hold the business’s notification account, and your software prints the payment failure notice (QR payments).
- Portable cash register. Register the location before sales start (Location registration).
- Network access. If you connect to eKasa from another station or from the cloud, turn on login and HTTPS or Expose (Connection and security).
After going live
- Updates. Follow the changelog and keep eKasa up to date; fixes also concern the communication with the eKasa system.
- Logs when there is a problem. If something does not work, attach the service logs to your question (Troubleshooting).