Apple Wallet and Google Wallet Student IDs and Alumni Cards, Issued From One Salesforce Record
Kemicard issues the student ID and the alumni card from records your institution already keeps in Salesforce. Re-enrollment refreshes the card in both wallets, and a withdrawal deactivates it within seconds.
Try on AppExchangeEvery Card Your Campus Issues, Managed by One Admin in Salesforce
All card programs count toward the same license and the same annual volume. So a university can start with alumni membership cards and add mobile student IDs the next term without opening another procurement cycle.
Mobile Student ID Cards
A digital student ID card issued straight from the Salesforce enrollment record, valid in Apple Wallet and Google Wallet the day admission completes. Every campus scan logs back to the student record.
Alumni Membership Cards
Alumni association membership cards that outlive every address change. Class year and member status stay current from the alumni record, so a move or a name change never means a reprint.
One Record, Both Wallets
One Salesforce template issues the Apple Wallet student ID and the Google Wallet version together. A single status change updates both, so there is no second design to maintain.
The Digital Student ID Card in Salesforce That Updates Itself Every Term
The card is a view of the Salesforce record, so it never drifts out of date. Re-enrollment refreshes validity in Apple Wallet and Google Wallet, and a withdrawal revokes the card within seconds.
- Issued From the Enrollment Record. The Flow fires when admission completes, and the student adds the ID in one tap before orientation week. No card desk, no appointment slot.
- Every Scan Checked Against the Live Record. Each ID carries a unique serial that Kemicard validates against Salesforce at the moment of the scan, so a forwarded screenshot or a duplicate gets rejected.
- Lost Phone, Same Student ID. The card is reissued to the new device from the student record in a few clicks. No replacement fee, no trip to the card office, no gap in access.
- Install Rates by Delivery Channel. Reporting shows how many admitted students actually added the ID, split by SMS, email, and QR. Intake communications get tuned on evidence rather than guesswork.
Campus Messages Students Actually See
Students ignore email; they never ignore the lock screen. The student ID pass doubles as the campus channel for the messages that matter.
- Event and athletics pushes. Game-day reminders and student-section entry details go to every ID holder — attendance scans measure what worked.
- Service updates. Library hours, registration deadlines, and campus alerts reach students where they look first.
- Lifecycle moments. Graduation flips the student ID to an alumni card with a welcome push — the advancement channel starts on day one.
- Geofenced check-ins. Orientation stations and exam halls surface the ID as students arrive.
Every message here is a template — sent automatically from a Salesforce Flow, a Bulk Action, or a single record, at no per-message cost.
Student Union Building
Austin, TX 78712
Weekends: 9:00 AM – midnight
The Back of the ID: Campus Essentials
Emergency numbers, service hours, and key links — on the ID every student already carries.
Every row is a back-of-pass field configured in Kemicard Studio — plain text, tappable links, and phone numbers, all mapped to Salesforce data. Exam-period library hours or a new helpdesk number reach every student without a single email.
The Alumni Digital ID Card Platform Your Advancement Team Can Run Without Developers
An alumni membership card gets issued once and stays right for decades. A name change or a chapter move is an edit to the record, and the card follows within seconds.
Graduation Turns the Student ID Into an Alumni Card
One Flow deactivates the ID and issues the membership card on the same record, so commencement does not create a data project.
Life Membership and Dues Status On the Card Face
Active, lapsed, or life renders as a field. An upgrade to life membership is a record edit, and the card reflects it in seconds.
Engagement Scoring Built From Card Activity
Card opens, scans, and notification clicks write back to the alumni Contact, which gives advancement a behavioural signal between gifts.
Volunteer and Board Roles as Access Levels
Chapter leaders and class agents carry a role field on the card that opens board meetings and volunteer check-in.
Every Card Current, Every Scan Counted
- Term-driven automation — status changes (enrolled, graduated, lapsed) update or expire cards through Flows.
- Secure member photos — dynamic thumbnails with secure private image support on Google Wallet.
- Self-service re-download — students recover their card on a new phone from the same add-to-wallet link.
- Event engagement — geofenced reminders on event day, and post-event journeys built from attendance data.
Northgate University
Westfield College Alumni
Manage Ticketing for Campus Events and Keep Every Check-In on the Attendee Record
Campus event registrations become wallet tickets automatically, with capacity and section pulled from Salesforce fields. Every scan at the gate writes back to the person who walked through it.
- Ticket Tiers. Student, faculty, and community has different access levels on the same template, so the scan decides admission rather than a staffer reading a badge colour.
- Reassigning a Ticket Without Reissuing It. Change who the registration belongs to and the pass follows the record, which handles the parent who hands their seat to a sibling.
- Sponsor Placement on the Pass Itself. Event passes carry sponsor branding as configured inventory, which gives sponsorship teams a digital asset to sell alongside signage.
- One Events Setup Serving Several Departments. Athletics, admissions, and advancement all issue from the same configuration, which stops three teams buying three tools for the same job.
Education, in practice
Campus life is a stack of cards: student ID, event tickets, library access, alumni membership, athletics passes. Kemicard consolidates them into wallet passes driven by the systems of record your institution already syncs to Salesforce — one template per use case, one add-to-wallet link per student.
Student IDs issue automatically on enrollment via Flow, carry the student photo, program, and a scannable ID, and deactivate just as automatically on withdrawal — no plastic card office, no replacement fees, no stale credentials in circulation. Event and athletics tickets check students in at the door with attendance flowing back to Salesforce, where advising and engagement teams can actually see it.
The alumni transition is where wallet passes earn their keep: the day a student graduates, the same record that drove the student ID drives the alumni membership card — automatically, with a push notification welcoming them to the association. Advancement teams get a living channel to every alumnus's lock screen for reunion invitations, giving campaigns, and geofenced messages when alumni return to campus. Universities like Towson run exactly this pattern on Salesforce today.
Frequently Asked Questions
Anything that reads a QR or barcode will scan it, including the handheld units most libraries and gyms already own. Proximity and magstripe door readers are a different matter, since those need hardware that reads NFC or a feed into your access controller through the API.
The wallet pass needs a phone, so most institutions keep a small plastic run for the handful of students who need one. The volume drops far enough that the card office stops being a printing operation.
No. Kemicard reads whatever record already represents the student, so the SIS or Education Cloud stays the source, and the card is an output of it.
It stays in your Salesforce org, because Kemicard runs inside it rather than on a separate server. Field-level security and permission sets you already configured govern who sees what, and no student record is copied to an outside database.
An admin can build and preview a working template in an afternoon. The longer part is agreeing which record and which fields the card binds to, which is usually a data-model conversation rather than a technical one.
Yes. Institutions commonly leave the arena contract alone and run orientation, reunions, and departmental events on Kemicard, since those are the ones where attendance needs to land back on the student or alumni record.
Apple Wallet and Google Wallet work in the markets your graduates live in, so an alum in Singapore carries the same card as one in Toronto. Push messages reach both.
Existing passes stay on holders' phones but stop receiving updates, so a status change no longer reaches the card. Your Salesforce data is unaffected, since it never left your org.
Plans are sized by cards issued per year rather than by staff seats, which suits institutions issuing thousands at intake. Nonprofit organizations receive a 10% discount on every plan, and the full tier table is on the pricing page.
Education — the brochure
A one-page summary for a conference table or an email, or the six-page version for the colleague who has to approve it. Both cover what you can issue, how it works, and the push and back-of-card examples for education.
