Nightly settlement to IBAN
At 23:00 the day's takings settle to the merchant's IBAN as one line. RO49 •••• 0421 in the demo. The accountant reconciles one number, not a list of payments.
Settlement batches as records
Every settlement is a batch with a name: tonight's sales ride B-0717-A, and each terminal shows its last batch and amount — B-0715-A at €312.40 on the studio-bar unit. A question about a payout starts from a batch ID, not a guess.
Takings by method, live
The split updates as payments land, so the day reads as one business with a method breakdown — not separate revenue streams in separate systems. When the mix moves, the merchant sees it the same afternoon, not in a month-end export.
The same order model as Gateway
The reference on the terminal is the same order format the hosted checkout uses, and the receipts match. A business running Gateway online and PoS at the counter runs one system with two surfaces, not two products.
Charges and refunds from the phone
New charge and refund live in the companion app, and the refund button sits on the sale itself. A refund points at the order — the same rule Gateway follows — so the merchant never has to remember how the customer paid before making it right.
Built to clear offline
Real venues lose connectivity at the worst moment. The terminals keep accepting offline — payments queue as deferred authorizations and submit with the next batch, deduplicated so reconnection never double-charges or loses a tap. A dead router is an inconvenience, not a closed till.
Terminal provisioning
A new terminal is registered from the fleet view, assigned a location, and retired the same way — the demo keeps a deactivated spare on the shelf. Devices carry their own IDs, so swapping hardware never confuses the books.
Remote diagnostics
Every terminal reports firmware, network, battery, and last-seen — and the fleet view can ping a device on demand. The studio-bar unit that went quiet on Jul 15 is diagnosed from a desk, not a drive across town.
Locations and pop-ups
Terminals carry locations — a front counter, a back office, a stand at Piața Amzei, two event kits marked on location. Reassigning a device to a weekend market is one action, and its takings still roll up to the same merchant.
Receipts three ways
Printed at the terminal, offered as a QR the customer scans, or sent from the app after the fact. The merchant copy has its own toggle, so the drawer does not fill with paper nobody asked for.
Cash in the picture
The split bar has a cash segment: €182.40 of the demo day. Cash sales are recorded alongside card payments, so today's €1,284.50 is actually today — not today minus the drawer.
Takings analytics
The fleet view keeps score beyond the total: 104 payments, an average ticket of €40.21 against €38.12 last week, takings per terminal. The merchant sees which counter earns before the month closes.
Staff accounts
The people behind the counter get their own accounts under the merchant, managed from the staff section. Who took a payment is a fact on the record, not a memory.
Customers on the sale
When the payer is known, the sale says so — A. Ionescu on the demo receipt. Payments connect to customers, so a regular's history is a lookup instead of a stack of anonymous tickets.
Search the fleet
Terminals are searchable by name or device ID, and payments by reference. When a customer calls about a charge, the answer starts with a search box, not a spreadsheet.
Exports
The fleet view and payment lists export to CSV as displayed. End-of-month is a download; the accountant never asks for screenshots.
Localization
The terminal speaks the counter's language — the language picker sits in the on-device settings. One fleet can serve venues that do not share a tongue.
An API for the counter
The developers section covers the counter too: payments and batches are queryable by API, so PoS data flows into whatever back office the merchant already runs.
Whitelabel terminals
Terminals run under your brand. The fleet, the app, and the receipts all follow — same hardware posture, your name on the screen.