Whitepaper · v3.0
Blockchain-ready access control for real venues
PDV Access Control System — multi-merchant SaaS, Access NFTs, and Wiegand doors. Access-control only.
1. Abstract
PDV is a multi-merchant access control SaaS that connects physical doors to blockchain credentials.
Merchants create access products, mint Access NFTs, issue digital keys to visitor wallets, and open doors through industry Wiegand controllers. Door events are logged for audit. Ownership of credentials can be verified on-chain.
The system is DB-first for door speed (CardNO / QR privilege) and chain-backed for ownership (mint, transfer, burn). Built for real venues — offices, events, clubs, campuses — and open to further Web3 features and other chains through partnership.
2. Problem
Traditional access control is:
- Centralized — card numbers live only in a vendor database; ownership is hard to prove or transfer.
- Opaque — visitors cannot independently verify what they hold; operators cannot easily prove issuance history.
- Siloed — tickets, identity, and door hardware do not share a common credential layer.
Many “NFT ticket” demos stop at an image and a QR. They rarely integrate real door controllers, multi-merchant operations, and verifiable on-chain credentials in one product.
PDV closes that gap: hardware that works today, credentials that can live on-chain.
3. Solution overview
Access NFT / QR
Products · Cards · Door
Merchants · ops
tickets / logs
mint · transfer · burn
privilege · open · swipe
3.1 What ships today
| Layer | Role |
|---|---|
| Platform | Shared issuer; onboard merchants; ops tools |
| Merchant | Products, generate, issue cards, door settings, wallet bind, logs |
| Visitor | Wallet login, my cards, self-register, scan-window QR |
| Hardware | WG 1001 CloudServer + ESP32 / ESP door & QR bridges |
| Chain (current) | Access NFT mint / transfer / burn on Ergo |
3.2 Design principles
- Door first, chain async — opening a door must not wait on block confirmation.
- Multi-tenant SaaS — one shared stack, many merchants, JWT + API Key isolation.
- Auditable — hardware swipe logs plus settled entry records.
- Blockchain-ready, not chain-locked — Ergo today; other chains via partnership.
4. Actors and roles
| Role | Who | Primary actions |
|---|---|---|
| Platform admin | PDV operators | Create merchants, rotate API keys, inspect mint/burn |
| Merchant | Venue / event operators | Wallet, products, cards, door, visitor approvals |
| Visitor | Card / ticket holders | Wallet login, Access NFT, QR / scan window |
| Integrator | POS / booking | API Key issue, list products |
| Door controller | 1001 / ESP32 bridges | Privilege windows; QR / swipe paths |
5. Product flows
Generate → Issue → Open
- Generate — allocate Wiegand-safe CardNO → mint Access NFT → Available.
- Issue — attach visitor wallet → Assigned → async NFT transfer.
- Open — remote scan or on-site QR scan window → door privilege → audit log.
Door privilege is not always standing by default — merchants enable scan window (~5s) or standing privilege. Modes: online / always-open / always-closed + open delay.
Also supported: visitor self-register QR, block/unblock, expire, burn unused, wallet transfer.
6. Technical architecture
| Component | Technology |
|---|---|
| API | ASP.NET Core 8, JWT + X-Api-Key |
| Database | Microsoft SQL Server |
| Admin | React + Vite |
| Visitor app | Capacitor / React |
| Chain | Ergo — mint, transfer, burn |
| Door | WG 1001 CloudServer |
CardNO is authoritative for “can this open now?” Access NFT is authoritative for “who owns the credential?”
7. Blockchain role
Blockchain is a credential layer for access — not the product itself.
- Access NFTs — portable, transferable proof of a ticket / key
- Wallet login — cryptographic identity for visitors
- Auditability — SaaS door logs + optional on-chain ownership history
Current network: Ergo. Other chains welcome through partnership.
8. Use cases
- Events & venues — NFT access tickets; scan at door; transfer tickets
- Membership clubs — standing privilege; audit logs
- Offices / campuses — visitor self-register; temporary scan windows
- Integrators / POS — API Key issue from booking partners
- Multi-site operators — one platform, many door endpoints
9. Competitive position
| Approach | Gap | PDV |
|---|---|---|
| Classic ACS | No wallet ownership | Hardware + chain ownership |
| NFT ticket markets | Rarely talk to Wiegand doors | 1001 privilege + swipe settlement |
| Web3 access demos | Single tenant / mock doors | Multi-merchant + real door path |
| Pure on-chain gate | Too slow at the door | DB-first open + async chain |
10. Roadmap
Delivered
- Multi-merchant API + Admin
- Generate → issue Access NFTs
- CardNO QR, privileges, block/expire
- WG 1001 remote open + swipe sync
- ESP32 / ESP door & QR reader path
- Visitor wallet auth & self-register
- Integration surface (api/v1)
Near term
- Visitor app UX hardening
- Persist wallet sessions
- Staff permissions in Admin
- Operator & integrator docs
Later
- Broader hardware adapters
- Deeper POS / ticketing kits
- More access Web3 features
- Multi-chain adapters via partners
11. Partnerships & multi-chain
PDV is open to partnerships that extend the access control product:
- Door / ACS vendors, ESP32 installers, and integrators
- POS, booking, and ticketing platforms
- Wallet and identity providers
- Teams who want credentials on other chains
The access model is chain-agnostic at the product layer. Ergo is the first production backend; other chains are welcome through collaboration.
12. Team
| Member | Role | Background |
|---|---|---|
| Hero Koo | Founder | Security systems, FinTech, community. |
| C.S. Teh | Co-Founder | Operations & community. Prior manufacturing COO. |
| Joezone Joe | Hardware / IT | 10+ years alarm, CCTV, door access. |
| Jack | Full-stack | Full-stack programmer. End-to-end web systems. |
13. Risks and limitations
- Hardware dependency — door reliability depends on controller / network path.
- Async chain — NFT transfer can lag after a successful door open.
- Regulatory — access logs and visitor data; merchants are data controllers for venues.
- Current single-chain production — Ergo until additional adapters ship.
14. Conclusion
PDV is an access control system: wallets and Access NFTs become working door keys, backed by merchant SaaS and Wiegand hardware.
The product is blockchain-ready where it helps — ownership, transfer, audit — and remains practical at the door. Further features and other chains are an open collaboration surface.