Google Pay for business: in-store, online, and in-app setup

Google Pay for business is a smaller job than most owners expect. In a store, a customer taps an Android phone on your terminal and the payment runs through your processor like any contactless card. On a website or in an Android app, your payment gateway connects to the Google Pay API. Google's developer FAQ says Google doesn't charge users, merchants, or developers additional fees to use the Google Pay API for payments. You keep paying your processor, the same as for every other card sale.

So the useful questions are practical. Is Google Pay switched on for every terminal you own? Does your checkout show the button? Is a "wallet fee" sitting on your statement that shouldn't be there? We'll take them channel by channel. If you've read our guide to Apple Pay for business, the counter part will feel familiar. The online setup is where the two wallets part ways. Facts here are current as of October 2026.

How does Google Pay work for a business?

Google Pay puts the customer's card on their phone, and your processor sees an ordinary card sale. The customer adds a credit or debit card to Google Wallet on an Android phone. To pay in a store, Google's help page says the phone needs to be unlocked, with the back of it held near the payment reader. They don't need to open the app first.

What reaches your terminal isn't the real card number. Google's Android guide says tap to pay sends a virtual account number and keeps the actual card number confidential. You may also notice two names: Google's in-store help lives under Google Wallet, while the checkout button and the developer tools are called Google Pay. For a merchant, both names mean a customer paying with a card they've saved with Google.

What doesn't change matters more than what does:

• The card behind the phone sets the price. A Mastercard debit card in Google Wallet shows up on your statement as a Mastercard debit sale.
• Google isn't a second processor. For online and in-app payments, Google's FAQ says Google Pay is not in the money flow; it passes the customer's encrypted credential to your payment provider, which approves and settles the sale.
• Disputes follow the card network's usual rules. A customer who paid by phone can still dispute the charge later, and our guide to how a chargeback works walks through what happens next.

How do you accept Google Pay in store?

You need a terminal that takes contactless payments, with wallets turned on at your processor. Google's documentation for card issuers says the merchant terminal must support NFC and ISO 14443. In plain terms: if your terminal already takes a tapped card, it's built to take a tapped phone. Google tells customers they can pay wherever they see the contactless or Google Pay symbol on the terminal or register.

Here's the setup, start to finish:

1. Look for the contactless symbol on every terminal and reader you own, including the spare one in the drawer.
2. Ask your processor, in writing, whether digital wallets are enabled on your merchant account and whether any wallet fee applies.
3. Test with an Android phone: run a small sale, then refund it to the same phone.
4. Tell customers. A contactless decal at the door and one on the counter do the job.
5. Teach staff the step Android users forget: the phone has to be unlocked. If a tap fails, ask the customer to check that it's unlocked and hold the back of the phone over the reader again.

Clearo's POS terminals accept Google Pay and Apple Pay along with Interac, Visa, and Mastercard, and they read chip, tap, and swipe. Selling away from the counter? Our mobile payments include tap to pay and mobile card readers, and our guide to taking card payments on your phone covers using an Android phone as the payment device.

Why does a Google Pay tap fail at the counter?

Usually the phone, not your terminal. Start with the two usual suspects: a locked screen, or a phone held away from the reader. If the same phone fails twice, ask for a card and keep the line moving; troubleshooting a stranger's phone at a busy register helps nobody. If every phone fails on one terminal, the contactless setting on that device may be off, and your processor should look at it the same day.

Our guide to NFC payments explains the short-range radio link behind every tap, card or phone.

How do you accept Google Pay on your website?

Through your payment gateway, using the Google Pay API. Your checkout shows a Google Pay button. Google returns the customer's encrypted payment details. Your gateway sends them to your processor for approval, like any other online card payment.

If your gateway or hosted checkout already lists Google Pay as a feature, start there and ask what's left for you to do. If you or a developer connect to the API directly, Google's request object reference sets out the main settings:

1. Gateway tokenization. You enter the gateway name and the gateway merchant ID your payment provider gives you. Those values come from your provider, not from Google.
2. A Google Pay merchant ID from the Google Pay & Wallet Console. Google says it's required in the production environment and ignored in the test environment.
3. The card authentication methods you'll accept, covered in the next section.
4. A full run-through in the test environment before you switch to production.

A Google Pay payment on your website is still a card-not-present sale. It's priced that way, and your usual online fraud checks still apply. Our online payments include hosted checkout, gateway integration, and fraud screening with AVS, CVV checks, and velocity rules. For how the gateway fits between your site and your processor, see our guide to what a payment gateway is.

Does online Google Pay always send a token?

No, and few merchants are told this. Google's documentation describes two authentication methods. Under PAN_ONLY, the card is stored on file with the customer's Google Account, and the payment data your gateway receives includes the actual card number and its expiry. Under CRYPTOGRAM_3DS, the card is an Android device token, and the data carries a cryptogram generated on the device.

Why care? A PAN_ONLY payment is a real card number arriving through a nicer button, so your fraud screening should treat it like one. Ask your gateway which methods your checkout accepts and how it screens each. Our guide to payment tokenization explains the different token types and why they matter for your PCI scope.

How do you accept Google Pay in an Android app?

With the Android version of the same API. Google publishes a separate Android tutorial for the Google Pay API, and the settings follow the same pattern as the web: gateway values from your payment provider, and a merchant ID for production. Treat it as a developer task and hand your developer your gateway's Google Pay instructions before the work starts. An in-app payment is card-not-present, the same as your website.

How much does Google Pay cost a business?

Whatever the card behind the phone costs. Google's FAQ says merchants keep paying processing fees to their payment processor, with no added Google fee for using the API. In a store, a Google Pay tap is priced as a card-present sale. On your website or in your app, it's card-not-present, which costs more.

Here's the gap on a $45 sale paid with a Visa debit card from a bank that's exempt from the federal debit cap, at rates from the Visa USA interchange schedule as of October 2026:

Now make it a month. Say a running shop in Austin takes 600 Google Pay taps at a $45 average, all on exempt Visa debit cards. Interchange is 600 times $0.51, or $306. If the same 600 sales came through its website, interchange would be 600 times $0.8925, or $535.50. The wallet didn't move either number. Where the customer paid did.

Interchange is only the first layer; network fees and your processor's markup sit on top. With interchange-plus pricing, each layer shows up as its own line, and our guide to what interchange fees are explains how the categories work. Google's no-fee statement covers the API. For taps at your counter, the price is whatever your processing agreement says, so if you see a line for "wallets" or "Google Pay," ask your processor what it pays for.

Can you add a surcharge to a Google Pay sale?

Only when the card behind the phone is a credit card, and only within the network and state rules. Visa caps US credit card surcharges at the lesser of your merchant discount rate or 3%, with 30 days' notice to your acquirer. On Mastercard credit cards, the most you can add is the lesser of your average effective merchant discount rate or 4%. A debit or prepaid card behind the phone can't be surcharged on either network.

A phone gives your cashier no clue which kind of card is inside it, so your terminal has to detect the card type before adding anything. Clearo's surcharging program handles compliance, disclosure, and setup. State law adds its own layer; our guide to surcharging rules by state and our US locations hub cover where you sell.

Google Pay vs Apple Pay: what changes for the merchant?

At the counter, almost nothing. Online, the setup work is different. Here's the side-by-side:

The Apple column comes from Apple's payment authorization guide, its security overview, its page on configuring Apple Pay on the web, and its advice to businesses to contact their payment provider. Our Apple Pay guide covers each step.

Our view: turn both on. They're the same tap at your terminal, and leaving one off turns away every customer carrying the other kind of phone.

Is accepting Google Pay worth it for a small business?

At the counter, yes, with no real downside. If your terminal already takes taps, Google Pay shouldn't cost you anything beyond the normal price of the card behind it. If your processor wants an extra fee to switch it on, ask why in writing.

Online, it depends on how your checkout is built. If your gateway offers Google Pay as a switch, turn it on: shoppers on Android phones skip typing sixteen digits on a small keyboard. If your site runs on a custom checkout and adding the button means a developer project, compare that bill with how many of your customers actually pay on your website. A landscaping company in Denver that bills 30 customers a month will get more out of a payment link in each invoice than a wallet button on a checkout page nobody visits.

Google Pay setup checklist

1. Confirm every terminal and reader takes contactless payments.
2. Get written confirmation from your processor that wallets are enabled, and whether any wallet fee applies.
3. Test a sale and a refund with an Android phone on each device.
4. Train staff: unlocked phone, back of the phone to the reader, then a card if it fails twice.
5. Online: ask your gateway whether Google Pay is included, what it costs, and which authentication methods it accepts.
6. If you connect to the API yourself, get the gateway values from your provider and a merchant ID from the Google Pay & Wallet Console before you go to production.
7. Surcharging credit cards? Make sure the terminal and the checkout both detect a debit card hiding behind the wallet.
8. Check your first statement and confirm Google Pay sales are priced like the cards behind them.

Common Google Pay mistakes

• Assuming you need a deal with Google to take phone taps in your store. The work is with your processor and your terminal.
• Turning on Apple Pay and forgetting Google Pay, or the other way around.
• Treating every online Google Pay payment as a token when your checkout accepts PAN_ONLY.
• Paying a monthly "wallet" fee nobody can explain.
• Adding a surcharge to a phone tap without checking whether the card inside is debit.
• Switching off fraud screening for wallet payments on your website because they "look safer."

Google Pay for business in Canada

In Canada, a phone tap is often a debit payment. Interac says customers can tap a debit card, phone, or wearable at checkout, so an Android phone tapped at a café in Vancouver can just as easily be an Interac Debit sale as a credit card sale. Interac Debit has its own flat pricing and tap limits. Our guide to tap to pay in Canada covers limits on cards and phones, and our Interac Flash guide covers contactless debit pricing.

Next step

Already taking cards? Find out what you're paying on wallet sales. Send us a recent statement for a free statement review, and we'll show you what Google Pay and Apple Pay sales cost you by card type and channel, and whether any wallet fee is tucked in there. Or contact us if you'd like a rep to look at your terminals and online checkout with you.