What Is a Digital Wallet? Apple Pay and Google Pay for Merchants
What is a digital wallet? See how Apple Pay and Google Pay payments are processed and priced, and how tokens and biometrics cut fraud at checkout.
On this page 6 sections
- What Is a Digital Wallet? Two Kinds That Bill You Differently
- How Apple Pay and Google Pay Process a Payment
- Digital Wallet Fees Follow the Card Underneath
- Apple Pay for Merchants Online: A Worked Checkout Example
- Where Mobile Wallet Payments Cut Fraud, and Where They Don't
- How to Start Accepting Apple Pay and Google Pay
A digital wallet is an app that stores a customer's payment cards on a phone or smartwatch and pays with them, either by a tap at your terminal or a button at your online checkout. For a merchant, the answer to "what is a digital wallet" comes down to one fact. Apple Pay and Google Pay run on the same Visa, Mastercard, American Express and Discover networks as the plastic card in the customer's pocket. You accept them through your existing merchant account, and the card underneath sets your cost. The wallet does not.
That fact answers most merchant questions about cost and fraud. It only holds for one kind of wallet, though, so the first step is telling the two kinds apart.
What Is a Digital Wallet? Two Kinds That Bill You Differently
| Wallet type | Examples | What actually pays you | Who sets your cost |
|---|---|---|---|
| Pass-through wallet | Apple Pay, Google Pay, Samsung Pay | The customer's Visa, Mastercard, Amex or Discover card | Your card processing agreement |
| Staged or stored-value wallet | PayPal, Cash App Pay | The wallet company's balance or funding source | The wallet company's merchant pricing |
A pass-through wallet holds a stand-in for the customer's card. When the customer pays, your processor sees a card transaction and prices it as one. A staged wallet behaves more like its own payment network. The customer pays the wallet company, the wallet company pays you, and you're charged under that company's terms. Our guide to Cash App Pay fees and setup for business explains how that model works.
Mixing the two up leads to bad decisions. A merchant who has heard that wallets are expensive may be thinking of staged-wallet pricing and skip turning on Apple Pay, even though in a typical card processing setup it adds no separate wallet charge. The rest of this piece is about pass-through wallets.
How Apple Pay and Google Pay Process a Payment
The work starts before the customer ever reaches your counter. When someone adds a card to Apple Pay or Google Pay, the card network issues a token: a substitute number tied to that card on that specific device. The real card number never reaches your business.
At checkout, the phone first confirms that the person holding it is the owner, usually with a face scan or fingerprint. It then sends the token along with a one-time code, called a cryptogram, that is valid only for that payment. In a store, the message travels over NFC, the short-range radio behind every contactless tap. Our explainer on NFC payments and tap to pay covers the hardware side. Online, the wallet passes encrypted payment data to your gateway instead.
After that, the payment follows the same path as any card sale. Your processor routes it to the card network. The network swaps the token back for the real account number and asks the cardholder's bank to approve the charge. The money then reaches your account on your normal payment settlement schedule. Our guide to next-day funding explains how faster deposit timing works. Our November 17, 2026 payments news roundup covers what that week's Chase outage meant for merchant deposits.
Because your systems handle a token instead of a card number, a breach exposes less. That does not remove your PCI DSS compliance obligations. You still take cards in other ways, and your systems still touch payment data.
Digital Wallet Fees Follow the Card Underneath
Apple and Google generally don't send merchants a separate bill for accepting their wallets through a standard card processing setup. Whatever you pay comes through your processor, so confirm the specifics with your own provider. The amount depends on the same factors that price any card sale.
The card itself matters most. A rewards credit card loaded into Apple Pay carries the interchange of a rewards credit card. A debit card in Google Pay is still debit, with debit pricing and debit rules. Interchange is the fee paid to the cardholder's bank and the largest part of your cost. Our guide to how interchange fees are set walks through the network tables.
The channel matters next. A phone tapped on your terminal is a card-present sale. Apple Pay used in a browser or app is a card-not-present sale. Visa and Mastercard publish separate interchange categories for the two, and card-not-present categories generally cost more. That is a network rule, and the wallet doesn't change it.
Network assessment fees apply to every transaction, wallet or not. Then comes your processor's own markup and pricing model, which is the one place wallets sometimes look different. On tiered pricing, some processors sort transactions into "qualified" and "non-qualified" buckets using their own logic. That is one processor's pricing choice and not a network rule, so check how wallet sales land on your statement.
Cost programs follow the card too. If you run dual pricing for card and cash customers or a cash discount, a wallet payment counts as a card payment. Surcharging rules attach to the underlying card, so a debit card tapped from a phone is treated as debit. Surcharging rules differ by network and by state. Confirm current requirements with your processor and a qualified advisor before you apply one.
The quickest way to check whether wallets are moving your costs is your effective rate: total fees divided by total card volume. If it shifts after you start taking wallets, look for a change in your card or channel mix, or a processor pricing tier.
Apple Pay for Merchants Online: A Worked Checkout Example
Wallet buttons matter most online. Typing a card number and shipping address on a small screen is where many mobile shoppers give up.
Here is an illustrative example. The figures are assumptions picked to make the math easy to follow, not benchmarks. Picture a store with 2,000 checkout starts a month on phones and an average order of $50. If wallet buttons raise mobile completion by a single percentage point, that means 20 more orders, or about $1,000 in added monthly revenue.
The processing cost on those added orders is your existing card-not-present rate. The wallet adds no separate fee in this setup, so your cost grows with sales instead of adding a fixed monthly charge. Enabling the buttons is mostly one-time setup work, which keeps the break-even bar low.
What decides it for your store is whether mobile shoppers drop off at the card-entry step. Open your platform's checkout funnel and compare mobile completion with desktop. A wide gap points to wallet buttons as an inexpensive fix to test. A narrow gap points to friction elsewhere, such as shipping costs or account creation. Our comparison of Apple Pay vs. Google Pay for business covers how setup differs between the two.
Where Mobile Wallet Payments Cut Fraud, and Where They Don't
Mobile wallet payments shut down the fraud that relies on stolen card data. A token tied to one device is worthless to someone who skims or steals it, because every payment also needs a fresh cryptogram that only the enrolled phone can produce. A thief holding a stolen phone still has to get past the owner's biometrics or passcode. In a store, a wallet tap is processed as a contactless chip-style transaction. That puts you in a much stronger position on counterfeit fraud than a magnetic-stripe swipe. Ask your processor how your setup is treated under current network liability rules.
Wallets do nothing for disputes unrelated to stolen credentials. A chargeback for an item that never arrived or didn't match its description looks the same whether the customer paid with Apple Pay or a keyed card number. Online, whether a wallet payment shifts fraud liability depends on network rules and on how your gateway flags the transaction, so get a direct answer from your processor. For online card payments made outside a wallet, 3-D Secure authentication is the tool built for that job.
Refunds can catch staff off guard. The digits printed on a wallet receipt often belong to the token, not the physical card. A customer comparing receipt and card may then insist you charged the wrong account, when you charged the right one. Many terminals also ask the customer to tap the same phone again to complete an in-store refund. If the mistake is caught the same day, our guide to voids vs. refunds explains why canceling before the batch closes usually costs less.
How to Start Accepting Apple Pay and Google Pay
In a store, you don't need a separate Apple Pay or Google Pay merchant account. You need a terminal that reads contactless payments, with contactless switched on and the contactless symbol where customers can see it. Most current smart terminals and POS hardware support it. How you set it up depends on the kind of business you run.
Retail Counters
At the register, a wallet tap is usually the quickest way to pay, and that adds up during holiday and weekend rushes. Mount the reader where the customer can reach it without handing anything to the cashier. Train staff to explain the token digits on receipts so returns don't turn into arguments.
Restaurant and Bar Tables
Pay-at-the-table handhelds let guests tap a phone without a server carrying a card to the back. Bars should confirm two things before relying on wallets for tabs: whether the POS can open a tab and pre-authorize on a wallet tap, and how it handles a tip adjustment on that authorization. Systems differ on both.
Food Truck Windows
Mobile terminals with cellular data keep lunch lines moving, and a tap is faster than inserting a chip at a service window. Be careful with offline mode. If your terminal holds transactions and sends them once the signal returns, wallet taps carry the same decline risk as any offline card sale. Our guide to store-and-forward explains that risk and how to limit it.
Online Checkouts
Online acceptance runs through your payment gateway or e-commerce platform. Apple Pay on the web typically requires your site to run over HTTPS and to verify your domain, and Google Pay may require a business profile, depending on how your gateway integrates. Your gateway's documentation will list the exact steps. Before you announce anything, test the full checkout on an iPhone in Safari and on an Android phone in Chrome. For in-store details, see our step-by-step guide to setting up Apple Pay and Google Pay at a small business.
Your next move: pull last month's processing statement and find how wallet transactions are labeled and priced. If they land in a costlier tier than the same cards would by chip, or your online checkout has no wallet buttons, request a free quote and a MannyPay specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
