Use your own Google Wallet account in Omniwallet

Step-by-step guide to connect your own Google Service Account and sign your Google Wallet cards with your account, instead of the shared Omniwallet account.

⏱ 10–15 minutes  ·  👤 Team with access to Google Cloud + panel administrator  ·  💶 Free

Before you start: what is this and why do it?

In Apple Wallet, a certificate is used. In Google Wallet, the equivalent is not a certificate: it is a Service Account with a key in JSON format. This is what you will create and upload in this guide.

By default, your Google Wallet cards already work signed with the shared Omniwallet account. You don't have to do anything for them to work.

Bringing your own Service Account is optional and gives you:

• Your own Google quota: the traffic from your cards counts against your project, not against a shared one. Useful if you have a lot of volume.
• Greater independence and isolation: your wallet activity goes through your Google account.

Summary of steps

1. Create (or choose) a project in Google Cloud Console.
2. Enable the Google Wallet API in that project.
3. Create a Service Account.
4. Generate and download its JSON key.
5. Upload that JSON file in the Omniwallet panel.
6. Check that it has been configured.

Steps 1–4 are done in Google Cloud Console. Steps 5–6 are done in your Omniwallet panel.

Step 1 — Create (or choose) a project in Google Cloud

A project is the Google container where your credentials and quota will reside.

1. Go to console.cloud.google.com with your company's Google account.
2. If you already have a project you want to use, skip to Step 2. To create a new one, go to Create project.
3. Give it a recognizable name, for example wallet-{my-company}, and click Create.
4. Make sure to have that project selected in the selector at the top before continuing.

New Project Form in Google Cloud Console.

Step 2 — Enable the Google Wallet API

This is what allows your project to issue cards and for the quota to be counted in your name.

1. Go to the Google Wallet API in the API library (with your project selected).
2. Click the Enable button.
3. Wait a few seconds for it to activate.

Google Wallet API card with Enable button.

Step 3 — Create the Service Account

The Service Account is the "technical identity" that will sign your cards.

1. Go to Service Accounts, with your project selected.
2. Click + Create service account at the top.
3. Give it an identifiable name, for example omniwallet-wallet. The ID will auto-fill. The description is optional.
4. Click Create and continue. In the roles step, you do not need to add any: click Continue and then Done.

Create service account form.

Step 4 — Create and download the JSON key

Now you generate the file that you will upload to Omniwallet.

1. Click on the service account you just created and open the Keys tab.
2. Click Add key → Create new key.
3. Select the JSON format and click Create.
4. The browser will automatically download a .json file. Save it in a secure place.

Select JSON and click Create.

After clicking Create, the browser downloads the file and the console confirms it:

Confirmation that the key was downloaded.

Step 5 — Upload the file in the Omniwallet panel

1. Log into your Omniwallet panel as an administrator.
2. In the side menu, go to Program → Card.
3. Open the Certificates tab and scroll down to the "Service Account Google Wallet" block (next to the "Apple Wallet Certificate" one).
4. Select the JSON file you downloaded in Step 4 and click Save.

Upon saving, Omniwallet checks that the key is valid and connects it to your program automatically. It may take a few seconds.

"Service Account Google Wallet" block in Card → Certificates.

Step 6 — Check that it has been set up correctly

If everything went well, the block will show a green notice "Service account configured" with the email of your service account (the one ending in ...iam.gserviceaccount.com).

From that moment on, your new cards and updates are signed with your Google account. The already installed cards continue to work normally.

Green banner "Service account configured".

Does the JSON key expire?

It does not have an expiration date. However, you can rotate it whenever you want.