About WalliPass
How It Works Behind the Scenes
- Secure collection: Students share only the essentials: name, campus ID, and a photo. The form intentionally avoids other personal questions.
- Short data journey: Those details are used immediately to assemble the pass. Temporary files exist only while it’s being built and are securely deleted afterward. No student data is sent to third-party marketing or analytics services.
- Mobile-first experience: The pass is designed for iPhone and Android phones. When someone tries to issue a pass from a laptop, we show a quick message explaining how to finish from a phone instead.
- Roadmap alignment: Today’s focus is on identity credentialing. We’re partnering with institutions to roll out deeper campus integrations, such as dining access. Door access will be coming soon.
- SUNY-first expansion: WalliPass is currently active at the University at Buffalo. We’re working with other SUNY campuses to make the service available statewide by the end of 2027.
Why campuses choose WalliPass
- Always with you: Students can easily pull up their ID and pay for food without reaching for their wallet or waiting for the GET App to load..
- Privacy-conscious: Data never leaves the institution’s environment except for pass generation, and it’s discarded once the credential is issued.
- Student-driven design: WalliPass was built by students who got tired of replacing bent, demagnetized, or forgotten IDs. That perspective keeps the UX simple and transparent.