soroush.asadi f368765419 fix(pos): charge the server amount, and don't book unconfirmed card payments ...

Two go-live money-correctness bugs in the POS pay flow (deferred TODO #1/#2):

#2 — pay against the server's amount, not a client recompute. The pay sheet
took `orderAmountDue(payTarget) || total`, so any time the server figure was
absent/zero it silently fell back to the POS's own 9% tax recompute. The backend
records whatever amount the client posts (it only uses its own order.Total to
decide closure), so a client/server mismatch books the wrong cash-drawer amount.
Now a real (server) order always charges orderAmountDue(serverOrder); only a
genuinely-local offline order — which has no server figure — uses the client
total.

#1 — don't record a card payment that wasn't confirmed. A connected terminal
that declines already throws POS_DEVICE_* and records nothing. But when no
terminal is wired up the request is "skipped" and the card was booked as paid
with zero proof it cleared. Now, when the card leg isn't machine-confirmed, the
cashier must confirm "card approved on the terminal?" before it's recorded;
cancel records nothing.

Also raise the shared AlertDialog to z-[80] so a confirmation renders above the
POS pay sheet (z-[60]) and its busy overlay (z-[70]); still below toasts.

tsc clean.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-06-25 13:13:21 +03:30

..

admin

fix(admin): don't prefill a fake phone on the admin login in production

2026-06-17 00:44:57 +03:30

dashboard

fix(pos): charge the server amount, and don't book unconfirmed card payments

2026-06-25 13:13:21 +03:30

koja

fix(brand): real transparent Meezi icon + guest-menu image placeholder

2026-06-15 18:17:52 +03:30

website

fix(seo): self-canonical + unique description on 6 pages that deduped to home

2026-06-24 21:32:08 +03:30