You keep the tag. You tap the guest.
A PartyPass is not something you hand out. It stays in your pocket, and you use it to invite people one tap at a time.
Tap a new PartyPass with your phone. It opens a claim page; sign in, assign it to your event, and it is yours. You can manage every tag you own from Dashboard → PartyPass.
The tag stays with you, not the guest. It can be a card on your keys, a key fob, or a custom shape with your organization’s branding. Every co-host carries their own.
When you meet someone you want at your event, hold your PartyPass to their phone. Their invitation opens right there. On iPhone it is an App Clip; on Android it is the event page in the browser. Nothing to install.
Each tap creates a brand-new invitation link for that one phone. The tag is never used up. Tap ten people or a thousand; every one of them gets their own link, and none of them can pass it on.
The invite opens in seconds, with nothing to install.
On iPhone, the tap launches a Luau App Clip: a small piece of the app that runs without a download or an account. The guest sees your event and three buttons: I'm going, Maybe, Can't make it. During check-in, the same screen becomes Check in now.
On Android, the tap opens the event page in the browser. Either way, first-time guests confirm a phone number with a text code, and that is the whole setup.
Organizations can brand both the tag and this screen.
Ask about custom branding
Each tap is a new link, checked by Luau, locked to one phone.
An ordinary NFC sticker opens the same web address every time, and an address can be copied. PartyPass is different in four ways.
The tag is an NXP NTAG 424 DNA chip. Each time it is tapped, it writes a different, encrypted web address that includes a tap counter and a cryptographic signature. The same tag never produces the same link twice, which means there is no fixed address for anyone to copy.
Our server recomputes the signature for each tap using NXP’s published procedure (AN12196) and compares it in constant time. A link that was edited, guessed, or produced by a chip we have not registered fails the check and is refused.
Every verified tap is recorded with its counter. If the same link arrives again, or a counter goes backwards, Luau answers “Tap already used.” So the link a guest could copy out of their browser has already been spent by the time they copy it.
A successful tap unlocks the event for that one device. Pasted into a text and opened on another phone, it returns “This link can only be used from the device that tapped the PartyPass.” Two locks, and a forwarded invite fails both.
For the engineering detail, read how PartyPass makes invites that can’t be forwarded.
Four settings, all in your event’s PartyPass Settings.
Turn on Require PartyPass Tap to RSVP and the event page is hidden from anyone who has not been tapped. Hosts and co-hosts always get through. The Share button disappears.
Give each invitation a window to respond: 15 minutes, 1 hour, 4 hours, or 24 hours after the tap. The guest sees a countdown, like holding a seat at the movies. When it expires, a fresh tap opens a fresh window.
One switch in your dashboard and that tag’s taps stop working. Every claim, assignment, release, and tap is logged, so you can see how many times each tag was used and when.
Unassign, reassign, or release a tag from Dashboard → PartyPass, or move all your tags to a new event at once. The same fobs serve your chapter or club all year.
Hosts who care exactly who shows up.
Members carry a branded key fob and tap the people they meet. The guest list is exactly who a member tapped, not whoever saw the group chat.
Invite people face to face. Each tap is that person’s invite, and it stays theirs.
Your team taps to invite in the weeks before, then taps guests in at the door on the night.
Reassign the same tags to next month’s event. The invite goes to the person, not the thread.
The same tag checks guests in.
Before the event, a tap invites. Once check-in opens, a tap records that the guest is here. You end up with a list of who actually came, not who said they would.
In the event’s PartyPass Settings, turn on Use PartyPass for Check-in and choose a lead time: at event start, or 30 minutes, 1 hour, 2 hours, or 4 hours before. From then until the event ends, a tap checks a guest in instead of inviting them.
A host or co-host at the door taps each guest’s phone. On iPhone the App Clip shows Check in now; in a browser it is I’m Here — Check In. Or mount a tag at the entrance and let guests tap it themselves.
A QR code that opens a form gets texted to friends who never showed up. A PartyPass check-in is a verified tap on one phone, tied to a signed-in account. If someone was not tapped, they were not there.
The event page shows who is checked in, how they got in, and who is still missing, with a Check in button next to each name. Two hours after check-in closes, you get a recap of who came, who walked in, and who did not show.
No tags? Luau also checks guests in with a printed QR code, or automatically by location for iPhone users who turn it on. See check-in and attendance tracking.
PartyPass, NFC invitation cards, and plain links.
Most digital invitations are a link, and anyone who has the link has the invite. NFC invitation cards are given to each guest and make opening that link easier, but the address on the chip never changes. PartyPass is a tag the host keeps, and every tap is checked.