Companion operating system · Gentlemen's clubs · Nightclubs · Bars
NightLedger sits beside the venue's existing POS — it never replaces the register. It runs the dancer economy, the door, and every dollar the POS was never built to touch. And every money flow is reconciled against an independent source, so the owner never has to wonder who's stealing.
The club keeps its POS. NightLedger runs on its own iPad, its own printer, its own scanner — reading the POS one-way and owning the flows the POS ignores. No rip-and-replace, no fight over their processor.
A strip club runs both. A nightclub runs the door plus tickets and VIP tables. A bar runs the door alone. Same core, different switches.
| Feature set | Gentlemen's club | Nightclub | Bar |
|---|---|---|---|
| Entertainer economy | ● | — | — |
| Patron / door module | ● | ● | ● |
| VIP rooms / tables | ● | ● | — |
| Ticketing | — | ● | — |
| Taxi / driver payouts | ● | ● | — |
Every dollar-moving step carries its own fraud check: a second, independent source it must reconcile against. Nothing is trusted from a single hand-typed number.
Manager checks her in — timestamp, shift opens, house fee assigned (or waived, logged). Target: 50 dancers in under 10 minutes.
Customer buys dance dollars on your payment rail (card-paid = authoritative). Later the dancer cashes them out; the manager records the redemption under PIN. The app runs this economy — it doesn't beg the POS to tag it.
Room timer runs → gross captured → split into entertainer cut and house cut. Writes exactly one ledger entry; the session record is detail only, so the payout never double-counts.
Cab, limo, and rideshare drivers get paid per head they deliver ($25+, configurable). The doorman logs heads per driver; the club pays out cash.
Engine sums the ledger: gross − deductions = net (can be negative). Prints her signed receipt, saves the PDF, then finalizes and locks. Any amendment after that needs owner unlock + full audit. Whole night closed in under 30 minutes.
Every ID that comes through the door runs the same pipeline. The output is a status a doorman reads at a glance in the dark.
PDF417 barcode read off the license via the Bluetooth scanner.
AAMVA parse + fake-ID checks: barcode-vs-front, format, issuer validation.
Find or create the patron; pull visit history, spend, status.
Screen this org — and, opt-in, the cross-venue network.
One of three outcomes, sized for a loud dark room →
Age verified, no flags. Green. Wave them in.
Lifetime spend + visit count surface. Recognize the whale before he reaches the bar.
Full-screen red the instant it hits. Photo, reason, where and when. "Notify security" front and center.
Every money flow reconciles against an independent second source. This is the spine of the product, not a feature — it's what makes "the owner never wonders who's stealing" a true statement.
| Money flow | Entered by | Reconciled against | What it catches |
|---|---|---|---|
| Dancer dollars | Manager redemption | Card-paid sale (your rail) | Redemptions faked against dollars never bought |
| Taxi / driver | Doorman headcount | Actual door / ID scans | Phantom drop-offs split by doorman + "driver" |
| VIP rooms | Manager session | Ledger + POS order mirror | Off-book VIP time, skimmed room cuts |
| Payouts | Payout engine | Signed slip + finalize lock | Altered nets, "never paid" disputes |
| Off-book sales | Manager (on the POS) | App dancer allocations | VIP / dance-credit rung on the POS but never tied to a dancer — the "Orphaned Sale" catch |
| Every action | Any user | Manager PIN + hash-chain audit | Anonymous edits, silent tampering |
Revenue never depends on winning the club's processing. Every club pays on the software; processing is the upside when you can get it. That turns the market from "clubs I can flip" into "every club in the country."
Club moves to your rail.
$15K–30K/mo · big club (model)
Married to their POS for the bar — you run the dance-dollar payments.
software + volume(the Sapphire case)
Won't move any processing. Still pays — and still more than SmartTab offers (nothing).
SaaS + platform fees
The plumbing under every module. None of it is optional — it's what a system handling PII and cash in a cash-heavy, litigated vertical requires.
Legal name, DOB, ID number, phone, email — ciphertext at rest. Keys live in AWS KMS, never in the database. Searchable-while-encrypted via blind-index hashes.
Append-only. Corrections are reversing entries, never edits. Each audit row carries the hash of the last — tamper-evident against an insider with IT access.
One device owns finalization for the night. Works through an internet drop as provisional, replays and locks on reconnect. The night never stops at 3am.
Every query scoped by org and location — enforced at the app layer and with database row-level security. Defense in depth, no leaks across clubs.
Biometric consent captured by signature; ID-image retention set per jurisdiction. Defensibility built as a feature — reviewed by counsel before go-live.
Owner, manager, staff, auditor. JWT with refresh rotation, login lockout, rate limits. Every financial action confirmed by manager PIN.