Accept Apple Pay at Your Small Business: Costs and Setup
Merchant Education & Growth

How to Accept Apple Pay at Your Small Business: Costs, Setup, Security

Accept Apple Pay at your small business with no extra Apple fee. See real Visa costs, terminal and gateway setup, and the domain rule that breaks checkout.

Empty modern conference room with a long dark wooden table, gray upholstered chairs, small potted cacti and a glass whiteboard

Photo: Pixabay

On this page 5 sections
  1. What It Costs a Small Business to Accept Apple Pay
  2. In-Store Setup for Apple Pay and Google Pay
  3. Online Setup: Gateway, HTTPS and Domain Verification
  4. What Tokenization Stops, and What It Doesn't
  5. When Wallet Payments Fail

Key takeaways

  • A wallet tap costs the same as a chip insert. The saving is against keyed entry: in our illustrative $60 traditional Visa credit sale, keying costs 23 cents more in interchange.
  • Apple Pay on your website is priced as card-not-present. Regulated debit is the exception, because Visa lists the same rate in store and online.
  • Phone taps and Apple Pay send a device token in place of the card number. Google Pay online can send an encrypted card number instead, so ask your gateway which kind it accepts.
  • Apple Pay refunds go through the Device Account Number, so ask customers to tap the same phone they paid with.

To accept Apple Pay at your small business, you need a card terminal that reads contactless payments for in-store sales and a payment gateway that supports wallet buttons for online sales. Apple doesn't charge you anything extra. Its partner FAQ says Apple does not charge merchants "any incremental fees for accepting Apple Pay" in stores, on the web or in apps. You pay your normal processing rate for whichever card the customer loaded into the wallet. In store, one contactless terminal accepts both Apple Pay and Google Pay. Online, you enable each wallet separately through your gateway or e-commerce platform. Ask your processor to confirm that your agreement doesn't add a fee for either wallet.

Apple Pay and Google Pay are not payment networks. Every wallet payment runs over the network of the card inside it (Visa, Mastercard, American Express or Discover), which is why pricing follows the card. What the wallet actually sends differs. Apple Pay, and any phone tapped at your counter, sends a device-specific stand-in number in place of the real card number. Google Pay on the web is mixed. Google's developer tutorial says the API can return either a card the customer saved to their Google account or a device token from an Android phone. In the first case your gateway receives the actual card number, encrypted, and not a token.

What It Costs a Small Business to Accept Apple Pay

A wallet payment costs what the card inside it costs, and three things set that price.

The card type sets the interchange fee, the per-sale charge the card networks set and pay to the bank that issued the card. A rewards credit card in Apple Pay is priced as that rewards card. Debit cards are priced as debit.

The channel matters next. A phone tapped at your counter is a card-present sale, priced like a chip insert. Apple Pay on your website or inside an app is a card-not-present sale, and the networks price most card-not-present categories higher.

Your pricing model decides whether you see any of this. On flat-rate pricing, a tap and a chip cost the same percentage. On interchange-plus, card type and channel pass straight through to your statement. Our comparison of interchange-plus vs. flat-rate pricing shows which one tends to cost less at your volume.

Worked Example: One $60 Sale, Five Ways

These numbers are illustrative. The example assumes a $60 sale on a Visa consumer card at a retail merchant. It shows interchange only, before Visa's network fees and your processor's markup. Debit rates come from Visa's U.S. Interchange Reimbursement Fees schedule. Credit rates come from Helcim's published summary of Visa's U.S. card-present rates.

Card and entry methodInterchange rateInterchange on $60
Traditional Visa credit, tapped with Apple Pay or inserted1.51% + $0.10$1.01
Same credit card, keyed in by hand1.90% + $0.10$1.24
Visa debit from a smaller (exempt) bank, tapped or inserted0.80% + $0.15$0.63
Same debit card, keyed in1.65% + $0.15$1.14
Visa debit from a large (regulated) bank, tapped in store or paid online0.05% + $0.21$0.24

Visa's table marks the regulated debit rate with an asterisk, and Helcim lists it a penny higher, at 0.05% + $0.22. Check the current schedule before you rely on any row.

A wallet tap costs exactly what a chip insert costs. You pay no wallet premium and get no wallet discount. The money is in avoiding keyed entry. When a chip won't read and a cashier types the number, the same credit sale costs 23 cents more in interchange. A shop that keys 100 of those sales a month pays about $23 more than it would if those customers had tapped (again, illustrative). Customers holding a phone can tap instead.

Debit cards from large banks fall under the Federal Reserve's Regulation II. For those cards, Visa lists the same rate for card-present and card-not-present sales. A regulated debit card in Apple Pay therefore costs the same at your counter as on your website.

Add-On Fees Worth Questioning

Check your quote for gateway charges labeled "digital wallet" enablement. Look too for terminal replacement fees if your device can't read contactless. These fees are one provider's pricing, not network charges, so compare them across quotes.

Cash Discount and Surcharging Programs Treat Wallets as Cards

If you run a cash discount program or dual pricing, an Apple Pay tap is a card payment and gets the card price. Surcharging is stricter. Card network rules limit which card types you can surcharge and by how much, and some states restrict the practice. A wallet payment keeps the identity of the card inside it, so a debit card in Apple Pay must be handled exactly like the plastic one. Before you turn anything on, read how surcharging works where it's permitted. Then confirm current rules with your processor and a qualified professional.

In-Store Setup for Apple Pay and Google Pay

Apple's guidance to payment providers gives merchants three routes to in-person acceptance: turn on contactless on a terminal you already own, buy a new EMV contactless terminal, or take payments on an iPhone with Tap to Pay on iPhone. Tap to Pay only works if your provider supports it, so ask before you plan around it.

Check the hardware. Wallet taps use near-field communication (NFC), the same short-range radio as contactless cards. Look for the contactless symbol, four curved lines, on the screen or the edge of the device. Most current smart terminals for retail and restaurant counters have one. Swipe-only and chip-only devices need replacing. MannyPay sells Clover, Valor, Dejavoo, PAX, First Data and SwipeSimple hardware. Before buying any model, have your provider confirm that it reads contactless and that contactless will be switched on for your account.

Switch it on. A terminal can have an NFC reader and still have contactless turned off, either in its settings or on the merchant account. If chip cards work and phones don't, ask your processor about that setting first. Then run a real tap with a tip prompt to make sure it works.

Train for refunds. Counter confusion usually starts here. Apple Pay records the sale under a Device Account Number, not the number printed on the customer's card. As one credit union's Apple Pay FAQ explains, the cashier uses that number to find the purchase and process the return like any card refund. The customer taps the same phone, picks the original card and approves the refund. If a customer says the digits on the receipt don't match their card, send them to the Wallet app. The card's details there show the last four digits of the Device Account Number.

Restaurants and bars that close checks at the table need handheld terminals for pay-at-the-table service with tip prompts that work on taps. Salons that keep a card on file for no-show fees should ask how a wallet card can be stored for a later charge, because that depends on the gateway.

Online Setup: Gateway, HTTPS and Domain Verification

For websites, Apple tells merchants to ask their e-commerce platform or payment provider which services they offer. Most payment gateways for online checkout support Apple Pay and Google Pay, some by default and some on request. MannyPay works with Authorize.net and NMI and integrates with Shopify, WooCommerce, BigCommerce and Magento. If your store runs on a platform, start in its payment settings. A Shopify payment integration or WooCommerce payment integration can show wallet buttons once the gateway allows them.

Apple then requires proof that you control the site. Its Merchant Integration Guide says you "must register and verify all top-level domains and subdomains" where the button appears. You place a file Apple generates in the .well-known folder on your server, as Apple's developer tech talk on Apple Pay on the Web shows. Payment processor Payrix's setup guide adds that the domain must be public and served over HTTPS with a valid SSL certificate.

The rule owners most often miss is that the subdomain list includes www. Blackbaud's merchant help file says so directly. Say you verify yourstore.com but serve checkout from www.yourstore.com. Depending on your gateway or platform, the Apple Pay button won't appear, or it will appear and then fail when the customer taps it. The same problem can follow a redesign or platform migration that deletes the verification file, or a new checkout subdomain nobody registered.

Google Pay needs its own setup, because turning on Apple Pay does nothing for the Google Pay button. A hosted checkout or platform payment page handles Google Pay for you in most cases. With a custom build, your developer calls the Google Pay API and routes the encrypted payment data to your gateway, using the gateway name and merchant ID the gateway supplies, as Mastercard Gateway's integration guide shows.

Google's tutorial also tells merchants to confirm with their processor whether device tokens are supported before choosing which card types to accept. To go live, you need a Google merchant ID. Google's developer FAQ says you receive one after Google approves your website in the Google Pay & Wallet Console, where you list every domain and subdomain that will call the API.

Before going live with either wallet, test on an iPhone in Safari and an Android phone in Chrome. Confirm that tax and shipping recalculate when the customer changes the address in the wallet screen.

What Tokenization Stops, and What It Doesn't

When a customer adds a card to Apple Pay, the wallet creates a separate, device-specific number linked to that card. Each payment also carries a one-time code, called a cryptogram, and the customer approves it with Face ID, a fingerprint or a passcode on their own phone. Google Pay taps at your terminal also send a device token. In both cases your terminal never receives the real card number, so a breach of your POS would expose tokens rather than card numbers a thief could reuse. That lowers your risk, but your PCI DSS compliance obligations still apply.

Google Pay on your website is the exception. When the API returns a card saved to the customer's Google account, your gateway gets the encrypted card number, not a device token, so the token protection above doesn't fully apply to that payment. Ask your gateway which Google Pay types it accepts and what checks it runs on the card-number type.

Tokens stop stolen and counterfeit card numbers. They don't stop disputes. Customers can still file chargebacks for orders that never arrived, or for purchases they made and later deny. Online wallet payments are card-not-present sales, so keep delivery confirmation and a clear refund policy. Ask too whether 3D Secure authentication for online payments suits your risk profile. Our walkthrough of how chargebacks work from start to finish covers the evidence that wins disputes.

To see whether wallets lift sales, measure your own mobile checkout completion rate before and after you add wallet buttons above the card form. Don't rely on industry averages. If you're weighing wallets beyond these two, read which digital wallets to accept and why.

When Wallet Payments Fail

Most failures come from setup problems, not the customer's phone.

SymptomLikely causeWhat to check
Phone taps, nothing happensContactless turned off, or terminal not ready for a saleDevice settings and software version
Contactless cards work, phones don'tWallet acceptance not set upAsk your processor to check wallet acceptance on the account
Apple Pay button missing or fails when tapped onlineDomain or www subdomain not verified, file deleted in a site update, or page not on HTTPSVerify every domain where the button appears again
Google Pay button missing, Apple Pay worksGoogle Pay not enabled in the gateway or platform, or site not approved in the Google Pay & Wallet ConsoleGateway wallet settings; your Google merchant ID and listed domains
Button shows on some devices onlyUnsupported browser, or no card in the customer's walletTest in Safari on iPhone and Chrome on Android
Payment declinedIssuer decline or suspected fraudLook up the response code in our guide to credit card decline codes
In-store refund won't go throughRefund sent to a different card or deviceHave the customer tap the same phone, or use the Device Account Number

The fastest check costs nothing. Tap your own phone on every terminal you own, then open your checkout on an iPhone and an Android phone. If either fails, or your quote includes wallet enablement fees, request a free processing quote from MannyPay. Have your latest statement and terminal models ready. A MannyPay specialist responds within one business day.

---

I fixed both problems you listed:

  • Google Pay tokens: Only Apple Pay and phone taps in store are now described as sending a stand-in number. The intro and the security section both say that Google Pay on a website can send the encrypted card number for a card saved to a Google account. That claim cites Google's developer tutorial, which is a new entry in SOURCES. One takeaway also changed: the one about the www subdomain now covers this Google Pay difference, since the body already explains the www rule.
  • The www subdomain: The text now says the Apple Pay button may not appear, or may appear and fail when tapped, depending on your gateway or platform. The troubleshooting table row says the same thing.

I also turned the three-item list of Apple's in-store options into a single sentence. That cuts the stacked lists and keeps the bulleted bold paragraphs from opening the same way.

  • Most sources weren't rechecked: I hit the search tool's limit after three searches. I rechecked the Google Pay claim, Apple's "no incremental fees" statement and the Visa rates. The other sources come from the previous version and I couldn't check them again. Those are Apple's integration guide and tech talk, Payrix, Blackbaud, Mastercard Gateway, Google's FAQ and the credit union refund FAQ.
  • No inline citation tags: The body has none, because the required format doesn't allow HTML. Sources are listed only in SOURCES.
  • Questions for the payments team: I added notes asking which Google Pay types MannyPay's gateways accept and whether MannyPay charges any wallet fees. The answers would let us make those parts more specific.

Sources

  1. Apple Pay Partners: Partner with Us for Platforms
  2. Apple Pay Merchant Integration Guide (March 2026)
  3. Apple Developer Tech Talk: Get Started with Apple Pay on the Web
  4. Payrix: Set Up Apple Pay
  5. Blackbaud Merchant Services: Verify a Domain for Apple Pay
  6. Google Pay API: Tutorial (Web)
  7. Google Pay API: Frequently Asked Questions
  8. Mastercard Gateway: Google Pay Integration
  9. Visa USA Interchange Reimbursement Fees
  10. Helcim: Visa Interchange Rates USA
  11. Orange County's Credit Union: Apple Pay FAQ

About the author

Isabella Cruz

Isabella Cruz is Business Growth & Commerce Editor for Beyond the Swipe, writing for small businesses, restaurants, retailers, entertainment venues and e-commerce sellers.

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.

Related reading