Campus ID Overview
Stay organized with collections
Save and categorize content based on your preferences.
Campus IDs are closed-loop cards used to identify
users and grant building access.
Users can add their Campus ID to their
Android-powered phone to securely access university
buildings.
They can also use their Campus ID with Google Wallet to
pay for university products and services such as dining,
laundry,vending machines, books, and more.
Campus IDs also give users fast
access to information such as user details and
important university phone numbers.
Service Providers
Campus IDs are supported by participating universities in the US and Canada through the following
Service Providers:
These Service Providers integrate with Google to provision and manage Campus IDs the user's Google Wallet. If you're a developer at a university and would like to learn more, check with your Service Provider on their ability to
add Campus IDs to Google Wallet.
User prerequisites
For a user to use Campus IDs with Google Wallet, they need the following:
- The latest version of their Service Provider's app from Google
Play
- For a possibly more streamlined user experience, consider creating a Play
Instant App. All functionality in this guide for creating
Campus IDs from Android apps is compatible with Play
Instant Apps. For more information about Instant Apps, see the
Overview of Google Play Instant.
- A phone that runs Android 9.0 or higher, with NFC turned on
- The latest version of the Google Wallet app (recommended)
For more user support information, see the support
article
Save your Student ID to Google Wallet.
University prerequisites
For a university to support Campus IDs with Google Wallet, they need the following:
- NFC-enabled readers capable of receiving a user
account credential from Google Wallet through the
Service Provider's supported protocol.
Brand guidelines
The brand guidelines contain information on "Add to Google Wallet" button guidelines and Campus ID asset
requirements. A field mapping template is also available to show how data maps
to each field on a Campus ID.
Card provisioning and user experience
The Service Provider app links the user account to a
Google Account through the Add to Google Wallet flow. For details on the
steps of this integration, see
Provision a new card.
Terminology
The following table describes terms used in this documentation and their
meaning.
| Component Diagram Object Definitions |
| Access Reader |
NFC-enabled university readers. |
| Account |
Typically managed by universities that use a
Service Provider's management system.
|
| Account Hub |
Account Hubs have access to the information necessary to manage
the lifecycle of access cards and the required auth keys to authenticate
with access readers. The Account Hub also performs security and
risk activities in order to improve overall security of the system.
|
| Google Play Services |
The Google Play Services application and its device services, which
enable all Campus ID functionality. This component also
encompasses the Google Wallet app. For more information, see
the
Google Wallet structure page.
|
| Google Servers |
Google backend servers that implement several closed-loop APIs
supporting Campus ID.
|
| Service Provider |
Technology providers of university management
systems.
|
| University app |
An Android application created by a University (or
Service Provider) for user to manage their
account(s).
Also referred to as Service Provider app.
|
| Card Issuers |
The University that issues the cards.
|
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-03-12 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-12 UTC."],[[["\u003cp\u003eCampus IDs on Google Wallet offer secure building access, university purchases, and quick access to user information.\u003c/p\u003e\n"],["\u003cp\u003eUniversities in the US and Canada can support Campus IDs via Transact or CBORD, who integrate with Google Wallet.\u003c/p\u003e\n"],["\u003cp\u003eUsers need an updated Service Provider app, an Android phone running 9.0 or higher with NFC enabled, and the Google Wallet app.\u003c/p\u003e\n"],["\u003cp\u003eUniversities require NFC-enabled readers compatible with their Service Provider's protocol to support Campus IDs.\u003c/p\u003e\n"],["\u003cp\u003eDetailed brand guidelines, provisioning information, and terminology explanations are available for developers and universities.\u003c/p\u003e\n"]]],["Campus IDs, managed via Service Providers like Transact and CBORD, can be added to Android phones and Google Wallet for university building access and payments for services like dining and laundry. Users need the Service Provider's app, Android 9.0+, and NFC enabled. Universities require NFC-enabled readers. The Service Provider app links user accounts to Google Accounts, allowing card provisioning. Google services enable the functionality. Brand guidelines and a field mapping template are provided. There are definitions of terms like Account Hub, Access Reader, and Service Provider.\n"],null,["# Campus ID Overview\n\nCampus IDs are closed-loop cards used to identify\nusers and grant building access.\n\nUsers can add their Campus ID to their\nAndroid-powered phone to securely access university\nbuildings.\n\nThey can also use their Campus ID with Google Wallet to\npay for university products and services such as dining,\nlaundry,vending machines, books, and more.\n\nCampus IDs also give users fast\naccess to information such as user details and\nimportant university phone numbers.\n\nService Providers\n-----------------\n\nCampus IDs are supported by participating universities in the US and Canada through the following\nService Providers:\n\n- [Transact](https://www.transactcampus.com/solutions/campus-id-solutions)\n- [CBORD](https://www.cbord.com/industries/higher-education/solutions/card-credentials)\n\nThese Service Providers integrate with Google to provision and manage Campus IDs the user's Google Wallet. If you're a developer at a university and would like to learn more, check with your Service Provider on their ability to\nadd Campus IDs to Google Wallet.\n\nUser prerequisites\n------------------\n\nFor a user to use Campus IDs with Google Wallet, they need the following:\n\n- The latest version of their Service Provider's app from Google Play\n - For a possibly more streamlined user experience, consider creating a Play Instant App. All functionality in this guide for creating Campus IDs from Android apps is compatible with Play Instant Apps. For more information about Instant Apps, see the [Overview of Google Play Instant](https://developer.android.com/topic/google-play-instant/overview).\n- A phone that runs Android 9.0 or higher, with NFC turned on\n- The latest version of the Google Wallet app (recommended)\n\nFor more user support information, see the support\narticle\n[Save your Student ID to Google Wallet](https://support.google.com/wallet/answer/12059409).\n\nUniversity prerequisites\n------------------------\n\nFor a university to support Campus IDs with Google Wallet, they need the following:\n\n- NFC-enabled readers capable of receiving a user account credential from Google Wallet through the Service Provider's supported protocol.\n\nBrand guidelines\n----------------\n\nThe [brand guidelines](/wallet/access/campus-id/get-started/brand-guidelines) contain information on \"Add to Google Wallet\" button guidelines and Campus ID asset\nrequirements. A field mapping template is also available to show how data maps\nto each field on a Campus ID.\n\nCard provisioning and user experience\n-------------------------------------\n\nThe Service Provider app links the user account to a\nGoogle Account through the Add to Google Wallet flow. For details on the\nsteps of this integration, see\n[Provision a new card](/wallet/access/campus-id/get-started/provision).\n\nTerminology\n-----------\n\nThe following table describes terms used in this documentation and their\nmeaning.\n\n| Component Diagram Object Definitions ||\n| Access Reader | NFC-enabled university readers. |\n| Account | Typically managed by universities that use a Service Provider's management system. |\n| Account Hub | Account Hubs have access to the information necessary to manage the lifecycle of access cards and the required auth keys to authenticate with access readers. The Account Hub also performs security and risk activities in order to improve overall security of the system. |\n| Google Play Services | The Google Play Services application and its device services, which enable all Campus ID functionality. This component also encompasses the Google Wallet app. For more information, see the [Google Wallet structure](/wallet/access/campus-id/guides/google-wallet-structure) page. |\n| Google Servers | Google backend servers that implement several closed-loop APIs supporting Campus ID. |\n| Service Provider | Technology providers of university management systems. |\n| University app | An Android application created by a University (or Service Provider) for user to manage their account(s). \u003cbr /\u003e Also referred to as Service Provider app. |\n| Card Issuers | The University that issues the cards. |\n|----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|"]]
