Receipt registration

Integrating via

Receipt registration is the core task of the integration: your software sends eKasa the sale data, and eKasa validates the receipt, writes it to the storage, sends it to the eKasa system, issues it and returns the result. The whole process step by step is shown in How eKasa works. This page is an overview; you will find the details on the subpages.

A sample solution using the .NET library is in the ninedigit-ekasa-quickstart project on GitHub.

Receipt types

Each receipt type has its own API endpoint and its own request class in the library:

Receipt When Endpoint
Cash register receipt sale, return, correction POST /api/v1/requests/receipts/cash_register
Paragon recording a receipt issued during a cash register failure afterwards POST /api/v1/requests/receipts/paragon
Invoice payment paying an invoice at the point of sale POST /api/v1/requests/receipts/invoice
Invoice payment paragon recording an invoice payment from a failure afterwards POST /api/v1/requests/receipts/invoice_paragon
Receipt When Request for client.RegisterReceiptAsync()
Cash register receipt sale, return, correction RegisterCashRegisterReceiptRequest
Paragon recording a receipt issued during a cash register failure afterwards RegisterParagonReceiptRequest
Invoice payment paying an invoice at the point of sale RegisterInvoiceReceiptRequest
Invoice payment paragon recording an invoice payment from a failure afterwards RegisterInvoiceParagonReceiptRequest

Invalid receipts, deposits and withdrawals are no longer recorded from 1 January 2026, and eKasa does not support them from version 9. Customer details have not been stated on receipts since 2021, when the Constitutional Court of the Slovak Republic abolished them.

Request structure

A request through the HTTP API has three parts:

{
  "request": {
    "data": { /* … receipt data */ },
    "externalId": "order-2026-000123"
  },
  "print": {
    "printerName": "pos"
  }
}
Part Required Content
request.data yes receipt data: cash register code, items, payments, texts
request.externalId always send it your identifier that protects against recording a sale twice
print no how the receipt is issued: paper, PDF or e-mail. Paper by default.

In the .NET library, request corresponds to the request object and print to the RegisterReceiptPrintContext parameter.

Topics

Esc

↑↓ selectEnter openEsc close

Chýba vám niečo v dokumentácii?

Napíšte nám, s čím potrebujete pomôcť. Ozveme sa do pár hodín.

Údaje použijeme len na odpoveď. Viac v ochrane osobných údajov.