The transaction, from both sides
You open the POS on whatever's handy — the shop tablet, your phone, the dusty laptop by the till — and sign in with your OrbChain account. Ring up a sale: type the amount in your local fiat, and the POS mints a real payment and renders a QR. The customer scans with any wallet, and both screens track the payment live — you see it flip to paid, they see it too, no "did it go through?" stare-down. Fiat pricing means the register thinks in your currency while the customer pays in theirs; the rate is locked when the payment is created, per the usual mechanics.
For genuinely counter-speed trade, enable Lightning: sub-second settlement makes the coffee-shop scenario real rather than aspirational. On-chain coins fit the sales where a short wait is natural anyway — restaurant checks, service invoices, market stalls where people chat.
Why no hardware is the feature
- Zero capex, zero per-device anything. A second register is another browser tab. A pop-up stall at a weekend market costs nothing to equip.
- Nothing to update or brick. It's a hosted web app — the version at the counter is always current, and a dropped tablet is replaced by any other device with a browser.
- No custody at the counter. Staff devices display payment requests; they never hold keys or balances. A stolen register tablet is a stolen tablet, not a stolen wallet — and the account behind it can require TOTP for anything that moves money.
Same rails as your online sales
POS payments aren't a separate product with separate money: they land in the same balance, appear in the same dashboard and exports, fire the same webhooks if you've wired them, earn the same signed receipts, and follow your account's treasury policy — Auto Settle into stablecoin, auto-payout to your wallet. An operation selling online and in person reconciles one system, not two. The fee is the same flat 0.4%; compare that with the in-person card stack (terminal rental + 1.5–3% + monthly minimums) and the register that is a browser tab starts looking like the serious option, not the scrappy one.
Where it fits, honestly
The POS shines where sales are attended and amounts vary — markets, events, services, retail with a human at the counter. It is not a vending machine (unattended flows want the payment-link or API route) and not a queue-busting supermarket lane — confirmation UX at that speed wants Lightning, so enable it if throughput matters. For the long tail of businesses whose card terminal is their single largest payments cost: open the tab, prop up the tablet, and you're accepting crypto in person today.