AdmitiQ · LogicLitz
AdmitiQ is a free, open-source library for signed, expiring tokens in QR codes, URLs, SMS, and NFC tags. No SaaS, no dashboard, no vendor lock-in.
Before you try it
A plain QR is just text: anyone can copy it, and it never expires. AdmitiQ signs the payload (HMAC-SHA256) and adds TTL expiry so old codes stop working. Optionally, it can enforce single-use so duplicates fail at the door.
The AdmitiQ case
01 · The copied QR problem
When a code is printed once and scanned later, copying becomes the easiest attack. Without a signature, you cannot distinguish a real token from forged text. Without expiry, a code can be reused long after the event date.
02 · What expiry fixes
TTL expiry means even a valid token becomes invalid after the window you choose. That turns “never expires” into “expires when it should” for tickets, check-ins, and one-time actions.
03 · How AdmitiQ works
AdmitiQ follows a practical flow: encode your fields, seal them with issued-at, expiry, and a unique id, then sign with HMAC-SHA256. Put the token into QR, URL, SMS, or an API response. Verification checks signature, time, and optional single-use rules.
04 · Security you can ship
Verification is cryptographic and can work offline for signature + expiry checks. That helps at venues and field locations where network is unreliable.
05 · Cross-language parity
Issue tokens in Python and verify in JavaScript, or vice versa. You get consistent wire formats across languages instead of reinventing custom HMAC implementations.
06 · Built for real use
AdmitiQ fits event tickets, attendance QR codes, parking permits, timed-entry passes, gym check-ins, hotel key links, coupon security, NDA/data-room invite links, beta access passes, and webhook replay guards.
If this sounds like you
The friction
“QR codes can be reused forever”
Invest in → TTL expiry that auto-rejects old tokens
Choose a time window and let verification stop reuse after the deadline—so you do not depend on “remembering to update QR destinations.”
The friction
“Forged codes are hard to block”
Invest in → Signature checks that prevent tampering
Tokens are signed (HMAC-SHA256). Verification rejects forged payloads so scans only succeed for tokens issued by your system.
The friction
“The same token can be scanned twice”
Invest in → Optional single-use enforcement via revocation store
Enable single-use by passing a revocation store (Redis, SQL, or in-memory). The first scan succeeds; repeats fail.
What you get back
HMAC
Forgery-resistant signature
TTL
Configurable expiry windows
0
No SaaS, no dashboard
2
Python + JavaScript support
LogicLitzFAQ
Straight answers about how we work, where we ship from, and what working with LogicLitz looks like.
Use AdmitiQ single-use mode: issue tokens with a unique id, then verify with a revocation store (Redis, SQL, or in-memory). The first scan succeeds; every repeat fails.
Install AdmitiQ and start issuing signed, expiring tokens.
