Can you put an employee badge in Google Wallet?

Yes, when your company issues it. An employee badge in Google Wallet is issued by the company’s access system to an employee’s Android phone, and the employee taps the phone on the door reader to get in.

A work badge in Google Wallet is not something an employee adds by scanning or copying a plastic card. It comes from the system that controls the doors. Here is what that looks like for IT, for facilities and for the people carrying the phones.

What an employee badge in Google Wallet is

It is a door credential stored in Google Wallet on an Android phone or watch. At the door, the person taps the phone or watch on the reader, and the door decides in under a second.

How a company puts an employee badge in Google Wallet

Add the person once. In the teamzPass platform, or through the teamzPass API from an HR system or directory, so joiners and leavers flow automatically.
The badge lands in Google Wallet on the employee’s phone, before day one.
Set which doors it opens where your doors are managed: in your current access control system with Credentials only, or in the teamzPass platform with the Complete solution.
Revoke in one click when someone leaves. The pass is removed from the phone and from every door.

What employees need

An Android phone with NFC and Google Wallet, or a supported watch.
A badge issued to them by their company. There is nothing for the employee to request from the door system themselves.

What IT should set up first

Pick a first group of people and a few doors, and keep their cards working while they switch.
Connect your directory, so joiners and leavers flow into teamzPass on their own.
Check which readers support wallet passes before the first badge goes out.
Tell people what to expect: the badge arrives in Google Wallet, and they tap the phone on the reader.
Decide who can revoke and reissue badges, and how a lost phone gets reported.

Teams with different phones

Many teams carry more than one kind of phone. teamzPass issues employee badges and access passes from one platform with one set of door rules, whatever phone people carry. Cards and fobs stay available for the few people who need them.

When an Android phone is lost or replaced

The administrator revokes the badge in teamzPass, which ends access at every door at once, and issues a new badge to the new phone. Because the badge is bound to that phone, there is no card to chase and nothing that can be handed to someone else.

Do the door readers need to change?

Only where they do not support wallet passes. Readers that already support wallet passes are configured to read teamzPass credentials; the others are replaced with wallet-ready readers. See do you need new door readers for phone badges for a door-by-door check.

Frequently asked questions

Can you put an employee badge in Google Wallet?

teamzPass issues employee badges and access passes to Google Wallet. The company issues the badge to the employee’s Android phone, and the employee taps the phone on the reader to open the door.

Can I add my work badge to Google Wallet myself?

teamzPass badges are issued by the company that manages the doors, not added by the employee from a plastic card. If your company uses teamzPass, your administrator issues the badge to your phone.

What happens if I lose my Android phone?

teamzPass lets your administrator revoke the badge for every door at once and issue a new one to your new phone.

Can one system cover a team with different phones?

teamzPass issues badges to different phones from the same platform, so one set of door rules covers everyone. Cards and fobs stay available for people who need them.

Why a badge in Google Wallet instead of a plastic card?

teamzPass puts the badge in Google Wallet on the phone people already carry: issued remotely, bound to that phone so it cannot be lent like a card, and revoked from every door in one click.

Planning badges for an Android team, or a mixed one? Schedule a call and we will walk through your doors and your current system with you.