Google Wallet
A record held by Google, a signed save link, and what that changes for you.
Google Wallet is the mirror image of Apple. There is no file: the pass is a record held by Google, and what the recipient receives is a signed “Add to Google Wallet” link. Updating it is a call to Google, and Google syncs every device that saved it.
A credential's Google channel
{
"channel": "google_wallet",
"state": "provisioned",
"externalRef": "…",
"installUrl": "https://pay.google.com/gp/v/save/…"
}installUrl is the save link. It is safe to put behind your own button, but prefer a distribution when you are handing the credential to a person: a distribution is tracked, can be revoked, and works for both wallets from one link.
GET/v1/credentials/{id}/channels/google_wallet/remote
What Google currently holds for this credential — the state on their side, not ours.
Your own issuer account
Objects can be created under your organisation's own Google Wallet issuer account rather than Nomi's. As with Apple, the credential is defined once and issued to both wallets — you do not maintain two designs.