Campus Card Systems and Services: A 2026 Buyer's Guide
Every modern university card program rests on three layers: a card management platform, the credential and reader hardware, and the services that connect them to SIS, access control, and dining. This guide compares the platforms (Transact, CBORD, Atrium, Heartland, Blackboard, TouchNet), explains the hardware choices, and helps procurement teams pick the right stack.
The Five Major Campus Card Platforms
North American higher-ed card systems consolidated heavily after the 2019 Transact / Blackboard Transact merger. Today, five platforms cover the overwhelming majority of US and Canadian campuses, with regional players in EU and APAC.
Transact (Transact Campus + IDX)
Largest US footprint — 1,300+ universities
- •Apple Wallet & Google Wallet provisioning via IDX
- •Native integration with Banner, PeopleSoft, Workday SIS
- •Strong vending and dining rails
Ideal for: Mid-to-large US universities prioritizing mobile credentials
CBORD GET / Odyssey PCS
Strong in dining-heavy campuses, healthcare adjacent
- •Tight POS integration for residential dining halls
- •Robust meal-plan accounting
- •Mobile ordering and food delivery built into GET app
Ideal for: Universities where dining services drive the card program
Atrium (Heartland)
Mid-market private colleges, growing community-college share
- •Lower TCO vs Transact/CBORD for sub-10k enrollment
- •Cloud-hosted with predictable subscription pricing
- •Open API for SIS and access-control integrations
Ideal for: Smaller institutions wanting modern infrastructure without enterprise pricing
Blackboard Transact (legacy)
Now consolidated under Transact Campus
- •Existing deployments still active at many R1 universities
- •Long-tenured integrations with HID, Allegion, dormakaba readers
Ideal for: Institutions on legacy Blackboard contracts considering migration
TouchNet OneCard
Bursar-led deployments where tuition payments link to ID
- •Native Banner/Ellucian integration
- •Strong financial-aid disbursement workflow
Ideal for: Schools where the card program lives under the bursar, not auxiliary services
Hardware: Which Chip Should Your Campus Card Use?
The card management platform decides what software runs your program. The chip on the card decides how secure, durable, and future-proof it is. Here's how the four credentials we manufacture stack up.
| Chip | Encryption | Anti-Cloning | Cost | Best For |
|---|---|---|---|---|
| MIFARE DESFire EV3 | AES-128 with mutual authentication | Anti-cloning via diversified keys | $ | EU universities, mid-size US schools, TCO-sensitive deployments |
| HID iCLASS SEOS | Secure Identity Object (SIO) over AES | Anti-cloning via SIO + license-bound issuance | $$ | Large US universities standardizing on HID readers |
| MIFARE Plus EV2 | AES-128 (Security Level 3) | Anti-cloning + sector encryption | $ | Migrations from MIFARE Classic without full reader replacement |
| Multi-tech (DESFire + 125kHz + magstripe) | Per-frequency | Limited on legacy frequencies | $$ | Bridging old door hardware while transitioning to encrypted access |
Need a deeper comparison? Read our DESFire EV3 vs iClass SEOS technical breakdown.
Services: What a Full Campus Card Program Actually Includes
Card Issuance & Personalization
Photo capture, encoding, printing, lamination, and on-demand reissue. Most universities run this in-house with desktop printers; high-volume programs outsource to manufacturers like CampusRFID for laminated and pre-encoded batches.
Reader Infrastructure
Door readers (HID multiCLASS, iCLASS SE), POS terminals (Squadron, Verifone), library and printing readers. Dining and vending rails are usually procured separately from the card platform.
SIS & Identity Integration
Banner, PeopleSoft, Workday Student, Ellucian Colleague feeding the card platform with enrollment, status, and dining-plan data — typically over SFTP or REST.
Mobile Credential Provisioning
Apple Wallet (VAS) and Google Wallet (Smart Tap) provisioning. Requires platform-specific certifications and reader firmware that supports Apple VAS and Google Smart Tap.
Access Control Integration
LenelS2, Genetec Synergis, Software House C·CURE, Honeywell Pro-Watch. The card platform publishes credentials; the ACS handles door decisions.
Help Desk & Lifecycle Support
Lost-card workflow, mobile credential troubleshooting, reader provisioning, and 24/7 incident response. The biggest hidden cost in any deployment.
How to Choose: Procurement Decision Framework
1. Anchor on the dominant use case. If dining drives the program, CBORD wins. If mobile credentials are the priority, Transact IDX is ahead. If TCO is the constraint, Atrium is competitive on the mid-market.
2. Audit your reader installed base. Replacing readers is more expensive than replacing cards. If your access control runs on HID multiCLASS SE, lean toward iCLASS SEOS credentials. If you're on a generic ISO 14443A stack, DESFire EV3 gives the best security-to-cost ratio.
3. Validate SIS integration up front. Demand a working integration POC against your live SIS during the RFP, not after contract signature. Banner-Transact and Workday-Transact integrations are mature; less common pairings still hit edge cases.
4. Pilot mobile credentials early. If Apple Wallet or Google Wallet matters to your students, write the SLA into the contract. Mobile provisioning depends on reader firmware that not every campus has.
5. Budget for cards, not just software. A 20,000-student campus burns through 25–30k cards a year between new students, replacements, and staff. Multi-year card pricing matters more than the platform license at scale.
Frequently Asked Questions
What is a campus card system?
A campus card system is the integrated stack of hardware (RFID cards, readers, controllers), software (card management platform like Transact or CBORD), and services (issuance, support, integrations) that lets a university use a single credential for student ID, building access, dining, library, payments, and transit.
Which campus card system is best for US universities?
Transact Campus has the largest US installed base and the most mature Apple Wallet / Google Wallet integration. CBORD GET is the strongest fit for dining-led programs. Atrium fits private colleges and community colleges that need modern infrastructure without enterprise pricing.
How do campus card systems integrate with access control?
Card platforms publish credential data to access control systems (LenelS2, Genetec, Software House C·CURE) via OSDP, OPC, or proprietary connectors. The card platform owns issuance and lifecycle; the ACS owns the door decision. Most modern deployments use multiCLASS or PIVCLASS readers to bridge legacy and modern credentials.
What hardware works with Transact, CBORD, and Atrium?
All three support ISO 14443A readers (HID, Identiv, Elatec, Smartrac). On the credential side, DESFire EV3 and HID SEOS are the dominant chips; multi-technology cards add 125 kHz Prox or magstripe for legacy door panels. CampusRFID manufactures cards encoded for any of these platforms.
How long does a campus card system implementation take?
Typical implementations run 4–9 months: 1–2 months for procurement and contracting, 2–4 months for SIS integration and reader provisioning, 1–2 months for pilot, and 1 month for full rollout. Mobile credential pilots add another 2–3 months.