Cashu POS

• Name: Cashu POS
• URL: https://github.com/babdbtc/cashu-pos
• Category: mobile Cashu merchant terminal / NFC ecash point-of-sale / Nostr-synced offline merchant control plane
• Tags: bitcoin-ecosystem
• Summary: Cashu POS is a mobile merchant terminal for Cashu and Lightning with NFC checkout, offline queuing, and Nostr-synced multi-device operation. Not a new rail. It is checkout, local storage, sync, receipts, refunds, and device approval packaged into one merchant shell. Useful implementation, not an anchor.
• What it does:
  • Turns an iOS or Android device into a Cashu-enabled point-of-sale terminal with NFC tap-to-pay support
  • Accepts both Cashu ecash over NFC and Lightning invoice payments from the same checkout flow
  • Supports offline-first operation by queuing payments locally and processing when connectivity returns
  • Includes built-in merchant-wallet functionality for managing ecash balances
  • Provides product catalog, cart, tips, table-management, order-tracking, and kitchen-display features for merchant workflows
  • Generates printable receipts, supports full or partial refunds, exports transactions for accounting, and syncs multiple terminals over Nostr relays
• Key claims:
  • The official README calls Cashu POS a self-hosted payment processing system using Cashu ecash with Lightning-compatible payments and NFC tap-to-pay support
  • The README says the project is designed for mobile devices, requires Expo Go on iOS or Android, and does not support web browsers because of native dependencies like NFC and secure storage
  • The README lists dual payment support, offline queuing, built-in wallet integration, receipt printing, refunds, transaction export, multi-terminal sync, and device approval as first-class features
  • The README’s feature comparison says Cashu enables offline payments, native NFC tap-to-pay, better privacy through blind signatures, and not requiring the receiver to be online, while also explicitly acknowledging the trust-mint tradeoff versus direct Lightning self-custody
  • The README says terminals synchronize product and transaction data through Nostr relays, using local SQLite storage plus signed events published to public relays
  • The README documents operational sync settings like automatic sync, interval timing, retry delay, and a default relay set, showing this is a real multi-terminal merchant workflow rather than only a local wallet proof-of-concept
  • The package manifest confirms the shipped stack includes @cashu/cashu-ts, react-native-nfc-manager, nostr-tools, Expo SQLite, Expo Secure Store, optional Supabase integration, and receipt-printing support, which matches the README’s merchant-terminal claims
• Whitepaper: No canonical standalone Cashu POS whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official GitHub repository, the raw README, and the published package manifest; see ../whitepapers/cashu-pos-primary-sources-2026-05-02.md.
• Sources:
  • https://github.com/babdbtc/cashu-pos
  • https://raw.githubusercontent.com/babdbtc/cashu-pos/master/README.md
  • https://raw.githubusercontent.com/babdbtc/cashu-pos/master/package.json

Internal linkages

• Best upward comparison points: cashu and btcpay-server.

Control surface

• Practical authority sits in mint selection, local wallet state, Nostr relay choices, sync policy, refund handling, receipt and catalog defaults, and which devices get approved to participate.

• This is merchant-shell packaging over stronger Cashu and Lightning rails, not a protocol center.

• Last reviewed: 2026-06-04 UTC