Email capture slows the queue
Asking for an address, spelling it out and correcting mistakes wastes staff time and creates privacy concerns.
Digital receipts without the friction
Tap. Get the receipt. Done.
Beep Receipt turns an ordinary POS receipt output into a secure digital receipt customers can collect with one NFC tap-no app download, no email spelling and no paper required.
✓ Works beside existing POS
✓ No customer app required
✓ Built for split bills
Hold phone here
Designed to sit between the POS and the customer
Raw TCP printing
Port 9001 / configurable
ESC/POS receipt data
NFC tap
QR fallback
API-ready
The receipt process is broken
Paper is easy for the POS. Everything after that is not.
Customers lose receipts. Staff mistype email addresses. Split bills produce confusion. Finance teams manually match transactions. Beep Receipt removes the friction without forcing merchants to replace the POS they already use.
Paper receipts disappear
Customers often lose them before expense reporting, returns, tax claims or warranty support.
Split bills break context
Multiple payers may need one receipt, separate allocations or a record that clearly explains who paid for what.
Reconciliation stays manual
Card charges, receipts and accounting records are often matched later by humans using dates, totals and guesswork.
How Beep Receipt works
The merchant keeps printing. Beep Receipt makes the receipt digital.
The Beep Receipt device presents itself as a network receipt printer, receives the receipt payload and creates a unique tap experience for the next customer.
1
POS sends receipt
The POS prints to Beep Receipt over the local network using a configurable raw TCP printer endpoint.
2
Beep Receipt creates a unique receipt
The device parses the print job, associates it with a short-lived token and prepares the NFC target.
3
Customer taps
The phone opens a secure receipt link using NFC. A QR code can provide a fallback for unsupported devices.
4
Receipt is saved or shared
The customer can keep a local copy, email it, export it or send it into connected accounting workflows.
Interactive demonstration
Try the customer journey
This demo simulates a receipt arriving from the POS and a customer collecting it with a tap.
Merchant device
Press the button to simulate a print job from the POS.
TAP
Ready for the next receipt
Beep Receipt is listening on the configured printer port.
Customer receipt
A clean digital copy can be stored locally or sent where it is needed.
Harbour Table
Receipt #SWP-4821
21 Jul 2026
09:42
09:42
| 2 × Breakfast Bowl | $36.00 |
| 2 × Flat White | $12.00 |
| 1 × Fresh Juice | $8.40 |
| Service | $10.00 |
| Tax | $20.00 |
| Total | $86.40 |
Complete platform
More than a digital copy of paper
Beep Receipt creates structured, usable receipt data that can support customers, merchants and finance teams after the transaction.
Tap-to-receive
Customers collect the correct receipt by tapping the merchant device immediately after payment.
QR fallback
A visible QR option keeps the experience usable when NFC is disabled or unsupported.
Unique receipt links
Each receipt receives a hard-to-guess token with configurable expiry, access rules and invalidation.
Portable receipt copies
Save a clean PDF, share a web copy or export structured data into another system.
Merchant API
Push metadata, retrieve receipts, receive events and connect receipt workflows to existing software.
Split bill support
Associate multiple customers and payment amounts with the same receipt while preserving the full context.
Reconciliation support
Match totals, timestamps, merchant data and payment references to reduce manual finance work.
Multi-location management
Manage devices, stores, receipt volumes and configuration from one merchant portal.
No forced app install
The receipt opens in the browser first. A mobile app can add history, automation and loyalty features later.
Split bills without losing the receipt
One table. Multiple payers. One complete record.
Beep Receipt can preserve the original merchant receipt while allowing each participant to retain the amount they paid and the items or share assigned to them.
✓Equal split, custom amount or item-level allocation
✓Each participant receives a copy linked to the full receipt
✓Payment references can remain attached for later matching
✓Useful for restaurants, group travel, events and shared business expenses
Harbour Table
Table 14 • 4 guests
AMJTSKRL
Breakfast Bowl × 2AM + JT$36.00
Flat White × 2SK$12.00
Fresh JuiceRL$8.40
Tax + serviceAll$30.00
Merchant-side architecture
Built to work with the POS, not replace it
The core device can be implemented with an ESP32-S3, an ST25DV NFC interface and secure software that handles the receipt lifecycle.
Existing POSPrints the receipt as normal
Printer endpointConfigurable network port
ESP32-S3Receives and processes print data
ST25DVPresents the unique receipt target
Receipt serviceSecure web view, exports and APIs
Local-first receipt handoff
The device can retain enough local state to serve the current receipt even when internet access is unstable.
Configurable printer emulation
Support can be adapted for raw TCP, ESC/POS-like data and common POS printer output patterns.
Short-lived access tokens
Links can expire automatically, become single-use or remain available under merchant policy.
Integrations and automation
Turn receipt data into something useful
The same receipt can feed accounting, expense, loyalty, refund, warranty and merchant analytics workflows without asking the customer to re-enter the transaction.
✓Xero and accounting export pathways
✓Card charge and receipt reconciliation
✓Expense management and corporate travel
✓Loyalty and merchant CRM with consent
✓Returns, warranty and support verification
Beep Receipt
Receipt API
Receipt API
Xero
Accounting
Expense Apps
Loyalty
POS Systems
Payments
Why Beep Receipt
A cleaner experience than paper, email or app-only receipts
| Capability | Beep Receipt | Paper | Email receipt | App-only receipt |
|---|---|---|---|---|
| No typing at checkout | Yes | Yes | No | Sometimes |
| No app required | Yes | Yes | Yes | No |
| Can be shared instantly | Yes | No | Yes | Yes |
| Supports split bill context | Yes | No | Limited | Varies |
| Machine-readable data | Yes | No | Limited | Yes |
| Works beside existing POS | Yes | Yes | Often | Depends |
| Reduces receipt paper | Yes | No | Yes | Yes |
Merchant ROI calculator
Estimate the operational impact
Change the assumptions to estimate annual paper usage and staff time spent manually capturing customer email addresses.
This calculator is illustrative. Actual savings depend on receipt length, paper cost, wages, usage and deployment configuration.
Paper receipts avoided81,900
Staff hours recovered500
Illustrative annual value$17,686
Security and privacy by design
Collect the receipt, not unnecessary personal data
Beep Receipt can deliver the receipt without requiring a customer to disclose an email address or create an account.
Minimal customer data
The base tap flow can work without a name, account or email address. Additional services should use clear customer consent.
Expiring receipt tokens
Receipt URLs can use cryptographically strong random tokens, limited validity and immediate revocation after use.
No card data requirement
The receipt workflow can operate without collecting or storing full payment-card details.
Merchant controls
Retention, export, access and device policies can be managed by store, group or enterprise account.
Encrypted transport
Cloud receipt access and merchant APIs should use modern TLS with signed requests and auditable device credentials.
Operational audit trail
Receipt creation, tap access, exports and administrative changes can be logged for support and compliance workflows.
Where Beep Receipt fits
Anywhere a receipt is printed and later needed
Hospitality
Restaurants, bars and cafés
Retail
Stores, kiosks and pop-ups
Travel
Hotels, transport and tourism
Services
Repairs, health and professional services
Events
Venues, ticketing and group payments
Enterprise
Multi-site merchant groups
Corporate
Expense and travel programs
Platforms
POS vendors and payment partners
Commercial options
Start with one counter. Scale to every location.
Final pricing can be based on devices, locations, receipt volume, integrations and support requirements.
Pilot
Custom / short deployment
Validate compatibility and customer flow in a real store.
- 1–3 devices
- POS print compatibility review
- Merchant setup and monitoring
- Receipt web experience
- Pilot outcome report
Merchant
Custom / location
For operational use across one or more stores.
- Device fleet management
- Receipt history and exports
- Split bill workflows
- Merchant dashboard
- Standard API access
- Email support
Platform & Enterprise
Custom / agreement
For POS vendors, payment providers and large merchant groups.
- Custom device profile
- Advanced integrations
- SSO and enterprise controls
- Custom retention policies
- Priority support and SLA
- Co-branding or white-label options
Deployment plan
From printer test to live merchant rollout
Compatibility
Capture sample print jobs, confirm encoding and map receipt fields.
Bench pilot
Connect the Beep Receipt device to a test POS and validate tap behavior.
Live store
Deploy at one counter, monitor reliability and collect staff feedback.
Scale
Standardise configuration, reporting, support and device provisioning.
Frequently asked questions
What merchants usually ask first
Does the customer need the Beep Receipt app?
No. The core receipt experience opens in the phone browser. A future or optional app can provide receipt history, automatic accounting export and other advanced features.
Does Beep Receipt replace the POS?
No. It is designed to behave like a receipt output target beside the current POS. The merchant can route receipts to Beep Receipt, a physical printer or both.
What printer protocol does it use?
The intended device listens as a configurable network receipt printer, including a raw TCP endpoint such as port 9001. Compatibility adapters can be created for different POS outputs and ESC/POS-style data.
How is each receipt link kept unique?
When a new receipt arrives, the system creates a random, hard-to-guess token tied to that receipt. The NFC target is updated to the current token. The token can expire, become single-use or be revoked after collection.
What happens if another customer taps too late?
The receipt lifecycle should lock or expire the previous token when the next receipt is received, subject to the merchant policy. A short confirmation window can prevent accidental access to the wrong receipt.
What happens if the internet is unavailable?
The device can retain local state and provide a local receipt handoff or queue cloud synchronisation until connectivity returns, depending on deployment design.
Can the merchant still print paper?
Yes. Beep Receipt can be introduced as digital-first, paper-on-request or parallel output. The merchant controls the workflow.
How do split bills work?
The original receipt remains intact while multiple participants can be associated with amounts, percentages or item allocations. Each participant receives a linked copy showing their share and the original transaction context.
Can Beep Receipt send receipts to Xero?
The platform is designed to support accounting exports and integrations. Exact Xero behaviour depends on the merchant’s account structure, authentication and desired reconciliation workflow.
Does Beep Receipt store card numbers?
It does not need full card data to provide a receipt. Payment references, masked details or transaction identifiers may be attached only when required for reconciliation and permitted by the merchant’s payment provider.
Can Beep Receipt work across many stores?
Yes. The merchant platform can manage devices, locations, printer settings, receipt volume, health status and access policies centrally.
Is the hardware locked to one POS brand?
No. The device approach is intended to be adaptable. A compatibility profile is required for each POS output format or printer interface.
Put Beep Receipt beside a real POS.
Start with a controlled merchant pilot, prove the receipt flow and measure paper reduction, customer adoption and staff impact.