The payment goes through, but no receipt is issued
The terminal beeps, the register remains open, and the waiter promises to send the receipt. An hour later, the guest writes that he needs the receipt for his company’s accounting. Meanwhile, the printer has printed three copies, none of which were handed out.
At the table, it’s even tighter: Google Pay or card payment via a mobile POS, the tip, and the fiscal receipt must all be generated in a single transaction closure. Otherwise, you’ll have the revenue in the bank but a gap in eKasa.
What Ellipse processes at once
Both the cash register and Ellipse POS generate the fiscal receipt via eKasa—Portos or FiskalPRO—at the moment of payment. The electronic receipt has a public link and an QR code. The guest opens it on their phone; you don’t have to explain it to them from a copy in a drawer.
SoftPOS on a mobile device covers tables without a fixed terminal. Pay by Square handles the transfer when a guest doesn’t want to use a card. In both cases, the receipt isn’t generated “sometime later,” but at the same time as the payment.
- Fiscal receipt issued the moment the bill is settled
- Email or QR instead of searching for a paper receipt
- A mobile POS where there’s no counter
- Pay by Square when the payment is made via bank transfer
Why this matters even outside of restaurants
Hotel bills, minibar charges, and wellness center access all end with the same question: where’s the receipt? If you can send it directly from the register, the front desk doesn’t have to sort through a basket of receipts, and the guest doesn’t have to wait for a copy “until the shift manager returns.”
