Fordham ID in Wallet FAQs

Fordham ID in Wallet is intended for eligible Fordham students, faculty, and staff whose Fordham accounts are enabled for the service and who have a supported device. Eligibility is controlled by the Fordham account/credential system; simply having Apple Wallet or Google Wallet does not make an account eligible.

If the enrollment page does not offer Get Started or Migrate to Fordham ID in Wallet and you believe you should be eligible, check View My ID Status and contact IT Service Desk rather than creating another account or trying a second device.

Go to the Fordham ID management/enrollment page and sign in with your Fordham username and password. Complete Duo authentication if prompted, then follow the enrollment option shown for your account.

You do not need to open a separate Fordham app every time you use the credential. Once enrollment is complete, the credential lives in Apple Wallet or Google Wallet and is presented from the phone at supported readers. Use the Apple or Google step-by-step guide if you want screenshots of the full setup flow.

You need a reliable internet connection while enrolling and adding the credential to Apple Wallet or Google Wallet. After the credential has been added, presenting it at a supported campus reader uses the phone's contactless capability; you do not need to keep the Fordham enrollment webpage open.

If enrollment is failing, verify that the phone has a stable internet connection before retrying.

Yes. The account used during Wallet provisioning needs to match the account on the phone that will hold the credential.

• Apple: use the Apple Account currently signed in to iCloud on the iPhone that will receive the credential.
• Google: use the Google Account associated with Google Wallet on the Android phone that will receive the credential. If you begin on a computer, sign in with that same Google Account during the computer-to-phone handoff.

Your Apple/Google account is separate from your Fordham login. You still use your Fordham username/password and Duo to access the Fordham ID enrollment page.

Yes. Fordham's tested enrollment flow can be started on a computer or on the phone that will hold the credential. Keep the target phone nearby.

Apple:
continue through the Apple sign-in/device-selection flow and choose the iPhone that will receive the credential.

Google:
the computer flow may present a QR code or Copy Link handoff. Open that handoff on the Android phone that will hold the credential and use the same Google Account that is active in Google Wallet on that phone. Keep the original browser page open until provisioning finishes.

Most users should be able to complete setup in a few minutes when their Fordham account, photo, and phone are ready.

Important: once you reach the Add to Apple Wallet or Add to Google Wallet portion of enrollment, continue without delay. Fordham's current provisioning flow uses a time-limited invitation that may expire after approximately five minutes. If the invitation expires or the process becomes incomplete, return to View My ID Status and use the approved continue/retry option once. Do not start a second enrollment on another phone.

Use your Fordham credentials to access the Fordham ID enrollment/management page and complete Duo authentication when prompted. Apple Account or Google Account authentication is a separate step used by the Wallet platform; it does not replace Fordham sign-in or Duo.

A valid ID photo is part of the Fordham credential record. If the enrollment flow cannot use an existing acceptable photo, it may prompt you to upload one before Wallet provisioning can continue.

If you already have a valid Fordham photo but are unexpectedly required to upload another one, capture the screen and contact IT Service Desk if you cannot continue. Do not repeatedly restart enrollment. Whether a specific user's existing photo should be reused is a Fordham data/process question rather than an Apple or Google Wallet setting.

First open View My ID Status and confirm your current ID type and status. Refresh the page once and make sure you are signed in with the correct Fordham account.

If you believe you are eligible but the enrollment/migration option is still missing, contact the IT Service Desk and provide a screenshot of View My ID Status. Do not create a second account or try enrollment from another phone.

Migration replaces your existing Fordham in-app/eID credential with the new credential stored in Apple Wallet or Google Wallet. The goal is to move your active campus credential to the supported Wallet experience.

Complete the migration only on the phone you intend to use. Once the Wallet credential is successfully issued, do not try to maintain duplicate mobile credentials or begin enrollment on another phone.

There is no normal self-service process to switch back after a successful Wallet migration. If Fordham ID in Wallet cannot be used because of an unsupported device or a technical issue, contact IT Service Desk. Any exception or return to another credential method is handled manually by the support/ID team.

Do not remove your Wallet credential or try to rebuild the old eID on your own.

Incomplete means enrollment started but did not finish successfully. This can happen if the time-limited Add to Wallet step expires, the browser flow is interrupted, or provisioning does not complete.

Return to View My ID Status and use the approved continue/retry option once. If the status remains Incomplete, capture a screenshot and contact IT Service Desk instead of beginning enrollment again on a second device.

The system believes a Wallet credential has already been issued or linked to a device. First check Apple Wallet or Google Wallet on the phone used during enrollment and then check View My ID Status.

If the card is still missing, do not enroll on another phone or repeatedly select Add to Wallet. Capture the Wallet screen and ID status and contact IT Service Desk so the credential/device state can be reviewed.

Apple Wallet: iPhone SE, iPhone 6s/6s Plus or newer running iOS 15.6 or later. Users must accept Apple and iCloud Terms & Conditions, enable Passcode, Face ID, or Touch ID, and have Two-Factor Authentication (2FA) enabled for their Apple Account.

Google Wallet: Android device with NFC enabled, running Android 12 or later, with the Google Wallet app installed. Google Wallet Partner Terms & Conditions must also be accepted. Student IDs are supported on eligible devices purchased in the U.S., Canada, and Australia.

If your device does not meet these requirements or you cannot use Fordham ID in Wallet for an approved reason, contact IT Service Desk.

No. Fordham's current process supports one active mobile credential/device at a time. Do not attempt to enroll the same Fordham credential on a second phone while it is active on another device.

If you are replacing your phone, lose access to the current phone, or accidentally start enrollment on a second phone, stop and contact IT Service Desk so the existing credential/device state can be reviewed.

Do not plan to use a tablet as the Fordham ID in Wallet device. Fordham's rollout and support process is built around a supported iPhone or Android phone that can present the mobile credential to campus readers. Apple and Google's public Student ID guidance is phone focused rather than a Fordham-supported tablet workflow.

Use a supported phone for enrollment. If you cannot use a supported phone, contact IT Service Desk.

Use your Fordham ID in Wallet at Fordham access points and campus services where you are authorized to use your Fordham ID, including supported building and door entrances, residence halls/dorms, parking and vehicle entrances, libraries, gyms and fitness/recreation facilities, dining halls and cafeterias, meal plan locations, printing, and other Fordham locations and services that accept the credential.

Your Fordham ID in Wallet carries the same access, permissions, and privileges assigned to your Fordham account. Adding your ID to Apple Wallet or Google Wallet does not give you access to a building, residence hall, parking area, dining service, or other location that you are not otherwise authorized to use.

If your Fordham ID in Wallet works at some locations but does not work at a location or service where you are authorized, please report the issue to IT Service Desk. Include the campus, specific building/location, door/reader/register/parking entrance or service, date and approximate time, what occurred, and any error message or screenshot available. This information helps determine whether the issue is related to your access permissions, a specific reader, or another downstream system or service.

Yes. You can use your Fordham ID in Wallet at Fordham libraries, gyms, fitness and recreation facilities, and other campus access points where you are authorized to enter or use the service.

Your Fordham ID in Wallet carries the same access permissions and privileges associated with your Fordham account. It does not provide additional access to locations or services that you are not otherwise authorized to use.

If your Fordham ID in Wallet does not work at a library, gym, fitness/recreation facility, or other location where you are authorized, report the issue to IT Service Desk. Include the campus, specific building/location and reader, date and approximate time, what occurred, and any error message or screenshot available so the team can determine whether the issue is related to your access permissions, the specific reader, or another system.

Yes. You can use your Fordham ID in Wallet at parking and vehicle access points where you are authorized to enter, just as you would use your Fordham credential at other supported campus access points. Your Fordham ID in Wallet carries the access permissions associated with your Fordham account and does not provide additional parking or vehicle access beyond what you are authorized to have.

If your Fordham ID in Wallet works at other Fordham locations but does not work at a parking or vehicle entrance where you are authorized, report the issue to IT Service Desk. Include the campus, specific entrance or reader, date and approximate time, and what occurred so the team can determine whether the issue is related to your access permissions or the specific reader/access point.

Present the phone correctly at the reader once and wait briefly for a response. On iPhone, hold the top of the iPhone near the contactless reader. On Android, make sure NFC is enabled and slowly present the back of the phone near the reader because antenna placement varies by model.

If there is still no beep, light, message, or other reader response, do not keep tapping repeatedly. Confirm whether the Fordham ID in Wallet works at another supported reader. Then report the exact campus, building, door/reader, date, approximate time, phone model, and Wallet platform to IT Service Desk. A complete lack of reader response can indicate reader/antenna placement, reader configuration, or another location-specific issue rather than an access-level denial.

Use the message/reader behavior to help identify the problem:

• Access Denied:
  the reader detected your credential, but the access permission or downstream access data may need review.
• Reader beeps but the door stays locked:
  report the exact door/reader because the issue may be specific to the access point or door hardware.
• No beep/no response:
  present the phone correctly once (and confirm NFC is on for Android). If there is still no response, report the exact reader.
• One door works but another does not:
  your Wallet credential is likely functioning; report both the working and failing locations so the access/reader configuration can be compared.

Include the date/time and whether the credential works somewhere else. Do not repeatedly revoke or re-enroll the credential to fix a single-door problem.

Fordham ID in Wallet provisioning and downstream campus services do not all update through the same system at the same moment. A credential may begin working for building access while dining (Transact) or printing (PaperCut) is still synchronizing the new credential/card information.

For dining, if the Wallet credential works at doors but a register reports that the card is not in the system, allow the documented synchronization window and verify the HID/Card/RFID value against Transact before treating it as a Wallet-provisioning failure. For printing, allow the documented overnight/next-business-day synchronization period and use the available manual-login workaround if needed.

If the service still fails after the expected synchronization period, report the specific dining register or printer, date/time, and error. Do not revoke/re-enroll the Fordham ID in Wallet just because one downstream service has not synchronized.

No. Moving the credential into Apple Wallet or Google Wallet does not itself grant new Fordham permissions. Fordham ID in Wallet should represent the access already assigned to your Fordham credential/role.

If Fordham ID in Wallet works at some locations but you receive Access Denied at a location you believe you should be authorized to enter, report the exact campus, building, door/reader, date and time. Access levels are handled by Fordham's downstream access-control systems, not by the act of provisioning the credential into Wallet.

If the phone is still powered on and the Wallet credential is available, a low battery by itself does not necessarily prevent a normal reader tap. Make sure the phone has enough power to remain operational.

On supported iPhones, an eligible Student ID with Express Mode on may continue to work in Power Reserve for up to about five hours after the iPhone needs to be charged. If the iPhone is manually powered off, Power Reserve is not available. Google does not publish an equivalent Student ID Power Reserve feature for a fully depleted Android phone.

Yes. You can use your Fordham ID in Wallet at Fordham dining halls, cafeterias, and other dining locations where you are authorized to use your Fordham ID or meal plan. Your Fordham ID in Wallet carries the dining privileges associated with your Fordham account; it does not add or change your meal plan or dining eligibility. After initially adding or migrating to Fordham ID in Wallet, dining access may take additional time to synchronize with Transact. Building access may work before dining because they are processed through different downstream systems. If dining still does not work after the expected synchronization period, report the campus, dining location/register, date and approximate time, error message (such as “Card Not in System”), and what occurred to IT Service Desk. Do not revoke or re-enroll your Fordham ID in Wallet solely because dining has not synchronized yet.

Your meal plan/account remains associated with your Fordham account, but the newly issued Wallet credential number may need time to synchronize to the dining/Transact system. Immediately after migration, building access may work before dining does.

Allow up to about 24 hours under the current rollout process. If the problem continues after that window, report the exact dining location/register and time. Support can compare the credential/Card number in HID with the value in Transact to determine whether the Wallet credential provisioned correctly and whether the remaining issue is downstream.

If the expected synchronization window has passed and the meal plan/balance itself is incorrect, report the exact dining location and transaction time.

If one register works and another does not, include both the working and failing register/location. That comparison can indicate a register-specific or downstream dining issue rather than a Wallet provisioning problem.

Yes. You can use your Fordham ID in Wallet at Fordham printers where you are authorized to use Fordham printing services. After initially adding or migrating to Fordham ID in Wallet, PaperCut may require additional time to synchronize the new credential information, so printing may not become available at exactly the same time as building access. If needed during the synchronization period, use the available manual login option to release your print job. If printing still does not work after the expected overnight/next-business-day synchronization period, report the campus, building/location, specific printer, date and approximate time, and exact error message (such as “Invalid Login”) to IT Service Desk. If one printer works and another does not, include that information because it can help identify a printer/reader-specific issue. Do not revoke or re-enroll Fordham ID in Wallet solely because printing has not synchronized.

Timing depends on the service:

• Building/door access: expected to work immediately where your Fordham account already has permission.
• Dining: the new credential may need downstream synchronization before registers recognize it; allow up to about 24 hours based on the current rollout process.
• Printing: the new credential may not be recognized until the overnight synchronization completes; if you enrolled today, try again the next business day.

If a service is still not working after its expected synchronization window, contact IT Service Desk with the exact location and time.

Printing may not recognize a newly issued Wallet credential until the overnight synchronization completes. If you enrolled today, try again the next business day.

Until the Wallet credential is recognized, use the printer's manual sign-in option with your Fordham username and password to release the job when that option is available.

If printing still fails the next business day, contact IT Service Desk with the printer name/location, date/time, and whether manual username/password release worked.

Report the exact name/location of the printer that fails and, if possible, the printer/location that works. If the same Wallet credential works at one printer but not another, the issue may be specific to that printer or reader rather than the credential itself.

Do not assume the campus credential will restore through iCloud, Google backup, or a general phone-migration tool.

Google specifically states that Student IDs do not automatically appear on a new device. Google recommends removing the Student ID from the old phone and then setting it up again on the new phone. Fordham also enforces a one-active-device process, so contact IT Service Desk before changing phones if the existing credential cannot be cleanly removed or the old device is unavailable.

For Apple/Fordham recovery, follow the Fordham support process rather than repeatedly re-enrolling.

Stop before completing enrollment on the second phone. Do not remove or revoke the working credential as a first troubleshooting step.

Contact IT Service Desk and explain which phone currently has (or previously had) the active credential and which phone you accidentally started using. Support can review the current credential/device state before you continue.

Do not move your Fordham ID in Wallet back and forth between phones. Fordham supports one active mobile credential/device at a time. If you are changing phones, use the Fordham ID Self-Service page to revoke the credential from your previous device before enrolling on the new device. If you are unable to complete the process or need assistance, contact IT Service Desk.

No. A warranty replacement, device exchange, major repair, or factory reset should be treated as a device-change scenario. Even if the replacement is the same make and model, it may be recognized as a different device for credential purposes. Do not assume your Fordham ID in Wallet will automatically transfer or restore from a backup. Use the Fordham ID Self-Service page to revoke the existing mobile credential before enrolling on the replacement or reset device. If you are unable to complete the process or need assistance, contact the IT Service Desk.

If your phone is lost or stolen, take action immediately. Use the Fordham ID Self-Service page to temporarily suspend or revoke your Fordham ID in Wallet. Apple: You can also use Find My to mark your iPhone as lost, which suspends access to Apple Wallet cards and passes on that device. Google: Google recommends removing the Student ID through your school account when a phone is lost or stolen. If you are unable to manage the credential through Fordham Self-Service or need assistance, contact the IT Service Desk.

Apple Wallet and Google Wallet do not use exactly the same card layout, and some details may appear only when you open/expand the credential. Your photo, role label, and other information may therefore be positioned differently depending on platform and card version.

A visual difference by itself does not mean your credential is invalid. If the information is actually incorrect—not just displayed differently—contact IT Service Desk.

No. The Fordham credential design, name, branding, and fields are controlled by Fordham and the Wallet platform. Users cannot independently rename, redesign, or customize the issued campus credential.

The Fordham Wallet credential displays Fordham identity information associated with the credential. The exact presentation can differ between Apple Wallet and Google Wallet and by role/template. In Apple Wallet, Card Details can show Fordham information and settings such as Express Mode, Show Updates, Privacy Policy, Terms and Conditions, and card-management options; role-specific information/photo placement may appear in the expanded details rather than on the front of the card.

Do not use visual differences alone to decide whether a credential is valid. If your name, role, ID information, or photo is incorrect, report the specific field and include a screenshot with sensitive information handled appropriately.

Fordham ID in Wallet is the primary credential. Physical IDs are handled through an approved exception/request process for users who cannot use Fordham ID in Wallet or have another approved need.

Contact IT Service Desk to begin the Physical ID process. Do not direct yourself to an ID Center or use an old public exemption form. If the request is approved, Strategic Sourcing/ID Services will contact you with the appropriate next steps and pickup information.

The existing Physical ID will not remain active or be used as a simultaneous backup after moving to Fordham ID in Wallet.

If you need a Physical ID exception after your Wallet migration, contact IT Service Desk. 

No. Your Fordham login and your Apple/Google account authentication are separate. Apple or Google handles authentication to its own account; Fordham does not need your Apple Account password or Google Account password.

Never send your Fordham password, Duo approval, phone unlock code, Apple Account password, or Google password to support. IT Service Desk may ask for screenshots, error text, device details, and the approximate time of an issue.

The mobile credential is designed to be tied to the approved device/Wallet environment and is not meant to be copied or exported like a screenshot or barcode.

Do not lend your phone or credential to another person so they can enter a building or use your Fordham services. Your Fordham ID in Wallet is personal and carries your own access permissions. Never share your Fordham password, Duo approval, phone unlock code, or Apple/Google password.

If your phone is lost or stolen, take action immediately to protect your Fordham ID in Wallet. Use the Fordham ID Self-Service page to suspend or revoke your mobile credential. Apple: You can also use Find My to mark your iPhone as lost; Lost Mode suspends access to cards and passes in Apple Wallet, including Student IDs. Google: Google recommends removing your Student ID through your school account if your phone is lost or stolen. If you are unable to suspend or revoke the credential through Fordham Self-Service or need assistance, contact the IT Service Desk.

Do not keep clicking the same action.

1. Wait briefly and refresh the page once.
2. Check View My ID Status.
3. If appropriate, open one fresh browser session and retry the documented step once.
4. If Add to Wallet, Retry, Cancel, Revoke, or another action still fails—or the status shows Issuing, Cancel Failed, Suspended, or another non-completed state—stop and capture a screenshot and the approximate time.
5. Contact IT Service Desk with the phone platform/model, what you were trying to do, the exact status/error, and the screenshot.

Do not remove/revoke the credential, reset the phone, or start enrollment on a second device as a generic troubleshooting step.

Keep the current browser session open while the credential is being issued and complete the Add to Wallet handoff promptly. If the invitation expires, the browser closes, or an unexpected Token ID/intermediate screen appears, do not copy/share the token or start a second enrollment.

Return to View My ID Status and use the approved continue/retry option once. If the process remains stuck, capture the screen and approximate time and contact IT Service Desk.

Temporarily suspend your Mobile ID if you expect to regain access to your phone or credential. Revoke it if your phone is lost, stolen, replaced, or permanently unavailable.

Lost or stolen Mobile IDs can be suspended or revoked through Fordham’s self-service ID portal without contacting IT Service Desk. Refer to the Fordham ID Management Portal to temporarily suspend or revoke your Fordham ID in Wallet.

If you are unsure which option to select or need assistance, contact IT Service Desk.

Use what works and what fails to narrow the issue down.

• If Fordham ID in Wallet works at one door/service but not another, the credential itself may be provisioned correctly and the issue may be a specific reader, access level, or downstream system.
• If the reader responds but shows Access Denied, report it as a possible access/authorization issue.
• If the reader beeps/accepts the credential but the door stays locked, report the physical door/reader location because the credential may have been read successfully.
• If there is no reader response at all, confirm phone positioning and the relevant phone setting (Express Mode on iPhone; NFC on Android), then report the exact reader if it continues.
• If building access works but dining or printing does not, treat that as a service/downstream synchronization issue rather than assuming the Wallet credential failed.

When contacting IT Service Desk, include platform, phone model, OS version, campus/building/service, exact reader or register/printer, date/approximate time, error message, and screenshot when available.

Where the credential works can help identify the type of issue. If your Fordham ID in Wallet works at some Fordham locations but not at another location where you are authorized, the credential itself may be provisioned correctly and the issue may be related to your access permissions, the specific reader/access point, or another campus system. If a reader displays Access Denied, report the location as a possible access/authorization issue. If the reader responds or beeps but the door does not unlock, report the exact door/reader. If there is no response from the reader at all, confirm the appropriate phone setting and positioning—such as Express Mode/reader positioning on iPhone or NFC/reader positioning on Android—and report the reader if the issue continues. If building access works but dining or printing does not, the issue may be related to downstream synchronization with Transact or PaperCut rather than the Fordham ID in Wallet itself.

To help IT Service Desk troubleshoot the issue as quickly as possible, provide: (1) Apple Wallet or Google Wallet, (2) device make and model, (3) operating system version, (4) the specific campus, building/location and door, reader, dining register, printer, parking entrance, or service involved, (5) the date and approximate time of the issue, (6) a clear description of what happened and what you expected to happen, and (7) the exact error message and a screenshot when applicable. Also mention whether your Fordham ID in Wallet works successfully at other locations or services, since that can help determine whether the issue is related to the credential, access permissions, a specific reader, or a downstream system.

Not as a general troubleshooting step. Do not remove, revoke, or repeatedly re-enroll your Fordham ID in Wallet simply because a door, dining register, printer, or other service is not working. If the credential works elsewhere, the problem may be related to the specific reader, your access permissions, or a downstream system rather than the credential itself. Repeatedly removing or re-enrolling the credential can create additional provisioning/device-state issues. Follow the troubleshooting guidance for the specific problem first. If the issue requires the credential to be revoked, removed, or re-enrolled, IT Service Desk can provide the appropriate next steps.