Most digital wallets cost merchants nothing extra. Apple Pay and Google Pay run on the card payments you already accept, so a wallet tap is billed at the same card-processing rate your processor already charges. The fee that matters is the rate in your processing agreement, not a wallet surcharge.
That is good news, but it raises a better question: what does your processor charge per card transaction, and is the pricing model fair? This guide explains how wallet payments are priced, which fees can appear on a statement, and how restaurants, online stores, healthcare practices and other merchants can cut the real cost.
TL;DR
- Apple Pay and Google Pay charge merchants no separate fee. Google states that its standard payment-provider processing fees still apply, with nothing added by Google.
- A wallet payment is a card payment. It is priced at your processor's rate, card-present in store and card-not-present online.
- Gateway, PCI and statement fees are separate lines. They sit on top of the card rate and are worth checking.
- Your pricing model drives the cost. Flat-rate, interchange-plus and Network Offset Pricing produce very different totals on the same wallet volume.
- Get your rates in writing and compare the effective rate (total fees divided by volume), not the headline rate.
Table of Contents
- What digital wallets cost merchants
- Apple Pay and Google Pay fees at a glance
- Google Pay merchant fees: in person and online
- Payment gateway fees and wallet transactions
- Wallets that act as the processor
- Why the same wallet tap costs different merchants different amounts
- Wallet fees for restaurants
- Other fees that show up next to wallet payments
- How to review your statement for wallet and card costs
- Our perspective: judge the pricing model, not the wallet
- Accept every wallet with transparent pricing
- Wallet fees by business type
- FAQ
- Sources
What digital wallets cost merchants
A digital wallet stores a customer's card details in encrypted form on a phone or watch. When the customer pays, the wallet passes a secure token to your terminal or checkout. Your processor then sends the payment through the card network to the customer's issuing bank, exactly as it would a plastic card.
Because of this, Apple Pay and Google Pay use the existing card infrastructure and add no merchant-facing fee. The wallet providers earn their revenue from card-issuing banks, not from you.
Google's own help page describes the same flow for online and in-app payments. Google does not hold or process the funds. The transaction takes place between the merchant and the financial institution that issued the payment method.
Apple takes the same position in its developer terms. Apple is not a party to the payment transactions made with its Apple Pay APIs. Those transactions are between the merchant and its bank, acquirer, card networks or other processing parties.
So what do you pay? Three layers:
- Interchange. The fee set by the card network that goes to the issuing bank. It varies by card type, whether the card is present, and the merchant category.
- Network and assessment fees. Small per-transaction and volume-based charges from the card brands.
- Processor markup and account fees. Whatever your processor adds: a percentage, a per-transaction amount, monthly fees, compliance fees and gateway charges.
A wallet changes none of these layers by itself. What changes your cost is the card behind the wallet (a rewards credit card costs more to accept than a basic debit card) and the pricing model your processor uses.
Apple Pay and Google Pay fees at a glance
| Item | What the merchant pays | Where it comes from |
|---|---|---|
| Wallet fee from Apple or Google | None | No separate merchant charge |
| Card rate on the tap or online payment | Your standard processing rate | Your processor agreement |
| Gateway fee, if you sell online | Set by your gateway provider | Gateway or processor pricing |
| PCI compliance and statement fees | Set by your provider | Provider fee schedule |
| Chargebacks | Standard dispute fee | Provider fee schedule |
We cover the Apple side in more detail in our guide on Apple Pay fees for merchants, including why you should get your rates in writing.
One example from the online world shows how this looks in practice. Ecwid's help center says there are no extra processing fees for Apple Pay or Google Pay. You pay only the flat 2.9% + $0.30 charge. The wallet adds no cost. The flat rate is what you pay either way.
Google Pay merchant fees: in person and online
The question "what does Google Pay cost a merchant" has one answer with two settings.
In person
When a customer taps an Android phone, the terminal reads a tokenized card and the payment is processed as a card-present transaction. In-person Google Pay payments are processed at normal card-present rates. Card-present transactions generally carry lower interchange than card-not-present ones, because the card is physically at the point of sale.
Your terminal must support contactless payments. A modern countertop or mobile terminal handles Apple Pay, Google Pay and Samsung Pay with the same NFC reader. If you want to see how tap-to-pay works on the hardware side, read about contactless payment processing.
Online and in app
Online wallet payments are card-not-present. They usually cost more per transaction than card-present payments, but they often convert better and carry less fraud exposure, because the customer skips typing card numbers. Google confirms that it adds no fees for accepting Google Pay. The merchant's standard payment-provider processing fees still apply.
If you take wallet payments through a website, you will also have a gateway. That brings us to the next fee.
Payment gateway fees and wallet transactions
A payment gateway is the secure connection between your checkout and your processor. It encrypts card data and passes the authorization request along. Online wallet payments run through it, so gateway charges apply to them the same way they apply to a typed card number.
Gateway pricing varies by provider. Common line items include:
- A monthly gateway fee
- A per-transaction gateway fee, usually a few cents
- A setup fee
- A batch or settlement fee
- Add-ons such as fraud tools or tokenization
In store, a terminal normally does this work, so a separate gateway fee is less common. Online, ask for the gateway fees as a written line item. Then you can compare them against the card rate. An all-in package with a transparent gateway is easier to budget than a stack of small add-ons.
PaySec's eCommerce Gateway and merchant services are built for this: one account that covers in-store processing, online checkout, mobile payments, ACH and recurring billing, with fraud prevention included in the platform.
Wallets that act as the processor
Apple Pay and Google Pay are pass-through wallets. Some other wallets work differently. They act as the payment processor themselves, so the merchant pays the wallet company's own rate instead of a rate from a bank or acquirer. Their fee schedules are published by the wallet company and can include a percentage plus a fixed amount, along with fees for withdrawals or currency conversion.
Before you add any wallet button to a checkout, ask one question: does this wallet send the payment through my processor, or does it process the payment itself? If it runs through your processor, your existing rate applies. If it processes the payment itself, read its fee page and add that rate to your cost model.
Businesses that sell across borders face another layer. Rules on paying and being paid also vary by country. Australia, for example, has introduced small business payment laws in Australia that affect how businesses there handle payment timing. For US merchants, the practical focus stays on the card agreement and the processor's fee schedule.
Why the same wallet tap costs different merchants different amounts
Two merchants can each accept the same Apple Pay tap and pay different amounts. The wallet is identical. The pricing model is not.
The three common pricing models
- Flat rate. One percentage plus a fixed fee for every transaction, such as 2.9% + $0.30. It is simple to read, but it blends cheap debit cards and expensive rewards cards into one price.
- Interchange-plus. The processor passes through interchange and network costs, then adds a stated markup. It shows the real cost of each card type.
- Network Offset Pricing. True wholesale interchange passes through, and the network costs are offset so the merchant keeps more of every sale. See how Network Offset Pricing works.
For a side-by-side look at all three, read our comparison of flat-rate, interchange-plus and Network Offset pricing.
A worked example on small tickets
The fixed part of a fee hurts most on small sales. Take a coffee counter that processes 40 wallet taps of $25 each in a day, which is $1,000 in volume. At a flat 2.9% + $0.30:
- Percentage: 2.9% of $1,000 = $29.00
- Fixed fees: 40 × $0.30 = $12.00
- Total: $41.00, an effective rate of 4.1%
The headline rate said 2.9%. The effective rate was 4.1%. The wallet did not cause the gap. The fixed fee did. This illustration uses the flat-rate figures from the Ecwid example above, and it is arithmetic, not a quote. Our guide to the small-ticket problem goes deeper on why low-value transactions cost so much to process under blended pricing.
Card mix matters
Wallets draw on every kind of card: debit, basic credit, rewards credit and commercial cards. Interchange differs for each. Visa, for instance, lowered key in-store and online consumer credit interchange rates by 10% in April 2022 for businesses with $250,000 in Visa consumer credit volume, generally those with $2 million to $2.5 million in revenue. The point for you is that interchange is a moving, tiered schedule. A pricing model that passes it through lets you see those changes. A blended flat rate hides them.
For a complete breakdown of every line you may see, use our complete guide to credit card processing fees.
Wallet fees for restaurants
Restaurants are a natural fit for wallets. Guests tap at the counter, at the table with a handheld, or at a pickup window. Tips, split checks and quick turns all work well with contactless payments.
The fee side matters because card costs weigh heavily on thin margins. The National Restaurant Association says that processing credit card transactions is one of a restaurant's largest operating expenses. It also reports that two companies control over 80% of the US credit card processing market.
What should a restaurant operator compare when reviewing processors? Use this list:
- Pricing model. Flat rate, interchange-plus or Network Offset.
- Effective rate. Total monthly fees divided by total monthly card volume.
- Average ticket. Counter-service tickets are small, so per-transaction fees weigh more.
- Hardware cost. Terminals, handhelds and kitchen or table-side devices.
- Contract terms. Length, minimums and early termination.
- Reporting. Whether you can see cost by card type, location and day.
- Multi-location support. One view across all your locations.
We built our restaurant content around exactly these questions. Start with the restaurant credit card processing fees guide, then read how 2.5-3% fees can eat 30-50% of your profit. For the full list of cost lines, see the complete 2026 restaurant payment processing fees guide.
Operators who want to move straight to a quote can use our restaurant payment processing page.
Other fees that show up next to wallet payments
Wallet volume sits on the same statement as everything else. These are the lines to check:
- PCI compliance fees. Merchants must comply with the Payment Card Industry Data Security Standard (PCI DSS) to protect customer data. According to Visa's small business paper, many providers charge additional monthly fees for compliance and security management. Ask whether that cost is built in. PaySec supports PCI DSS Level 1 and SOC 2 compliance.
- Statement or monthly fees. A fixed monthly charge for account maintenance. PaySec has no monthly minimums.
- Terminal fees. Rental or lease charges for hardware. PaySec's Free Placement program places terminals at $0 per month.
- Chargeback fees. A charge per dispute, separate from the lost sale.
- Early termination fees. Penalties for leaving a long-term contract. PaySec has no long-term contracts.
- Non-qualified or downgrade surcharges. Extra charges when a transaction falls outside a bundled tier.
- Data fees on B2B cards. Commercial cards can qualify for lower rates when the right transaction data is passed. PaySec's Enhanced Data Optimization handles this for B2B sellers.
Visa also notes that digital payment acceptance can level the playing field for small businesses, provided merchants evaluate providers on security features, integration and fee structure. That is a useful test for any provider you consider.
How to review your statement for wallet and card costs
A statement review takes about an hour and shows you the true cost of every wallet tap.
- Pull the last three months of statements. Three months smooths out seasonal swings.
- Find total fees and total volume. Divide fees by volume. That is your effective rate.
- Separate the layers. Find interchange, network fees and processor markup. If the statement bundles them, ask for the breakdown in writing.
- List every non-transaction fee. Gateway, PCI, statement, terminal, batch and compliance lines.
- Split card-present from card-not-present. Wallet taps in store should land in the card-present group.
- Check your average ticket. If it is under $15, fixed per-transaction fees may be your biggest lever.
- Compare pricing models. Ask for a quote under Network Offset or interchange-plus, using your own statement data.
- Get rates in writing. Any rate quoted by phone should appear in the agreement.
Our payment processing guide for small business walks through account setup and what to ask for at each step. If you want context on where the industry is heading, read payment processing trends for small business.
Our perspective: judge the pricing model, not the wallet
We talk to merchants every week who ask whether they should accept Apple Pay and Google Pay. The answer is yes. Customers want to tap, and wallets add no merchant-facing fee. The better question is what sits behind the tap.
A wallet payment is a card payment. If your pricing blends interchange and markup into a single flat rate, a rewards card tapped on a phone costs you the same as a basic debit card, and every small ticket carries the fixed fee. That is a pricing problem, and the wallet cannot solve it.
This is why we built Network Offset Pricing. It passes through true wholesale interchange, offsets the network costs, and removes hidden fees and flat-rate markups. Merchants across 18+ industries use it, and typical savings run 30-60% compared to major processors. One client reduced processing costs by 42%.
What we recommend:
- Accept every major wallet. It costs nothing extra and guests expect it.
- Look at your effective rate, not your quoted rate.
- Ask for detailed transaction reporting, so you can see costs by card type.
- Choose a provider with no contracts and no minimums, so your pricing stays earned, not locked in.
- Match the provider to your vertical. Restaurants, healthcare practices, eCommerce stores, SaaS platforms and CBD retailers each have different ticket sizes, card mixes and compliance needs.
— PaySec Marketing Team
Accept every wallet with transparent pricing
PaySec processes in-store, online and mobile payments on one platform, including Apple Pay, Google Pay and contactless tap. You choose from Network Offset, Flat Rate or Custom Enterprise pricing, with no monthly minimums and no long-term contracts. Approvals are fast, including for high-risk verticals, and you get detailed reporting on every transaction.
See the options on our pricing page, explore merchant services, or start at paysec.ai to get a rate review built from your own statement.
Wallet fees by business type
The wallet is the same everywhere. What differs is the average ticket, the share of online sales and the compliance needs. Here is where to focus by sector.
- Restaurants. High card volume and small tickets. Focus on the effective rate and per-transaction fees. Wallets speed up counter and table service.
- eCommerce. Wallet buttons shorten checkout. Focus on gateway fees and card-not-present rates. See our eCommerce payment processing and payment gateway pages.
- Healthcare practices. Patients pay copays and balances by tap or online. Focus on secure, compliant processing and clear reporting.
- SaaS and marketplaces. Recurring billing and larger tickets. Focus on recurring billing tools, ACH options and enhanced data for B2B cards.
- CBD and high-risk retail. Wallet acceptance often depends on the merchant account you hold. Focus on a processor that approves your vertical and keeps pricing fair.
- Mobile and field services. Tap on phone and tablet. See our mobile payment processing page and our page for home services.
FAQ
Does Apple Pay charge merchants a fee?
No. Apple does not charge merchants a separate fee for accepting Apple Pay in the United States. You pay your normal card-processing rate to your processor. Apple earns its revenue from card-issuing banks.
How much are Google Pay merchant fees?
Google adds none. Google's API page says the merchant's standard payment-provider processing fees still apply. In store the payment is processed as card-present, and online it is card-not-present, each at the rates in your processor agreement.
What is a payment gateway fee?
A gateway fee is what a gateway provider charges to securely transmit and authenticate card data between your checkout and your processor. It often combines a monthly fee with a small per-transaction amount, and it is separate from the card-processing rate. Ask for it as its own line in your quote.
Can I accept digital wallets online?
Yes. Wallet buttons can be added to an online checkout through a gateway that supports them. Apple lists the US eCommerce platforms and payment service providers that support Apple Pay. Online wallet payments are card-not-present and bring your gateway fees with them.
How can a restaurant lower wallet and card costs?
Start with the effective rate on your last three statements. Then compare pricing models and ask for transaction-level reporting by card type. Restaurants with small average tickets often gain the most from moving away from blended flat-rate pricing.
Sources
- Google Pay API | Google for Developers
- Pay on an app or website - Google Pay Help
- Digital wallet: Definition and How It Works
- IAP or Apple Pay? | Apple Developer Forums
- Payment Platforms - Apple Pay - Apple Developer
- Apple Pay and Google Pay – Ecwid Help Center
- Visa extends additional support to small businesses
- Credit Card Competition Act: Just the Facts, National Restaurant Association
- National Restaurant Association press release on credit card processing
- Digital transformation of SMBs: The Future of Commerce, Visa
- New Australian Small Business Payment Laws: A Guide