To accept Apple Pay and Google Pay, you turn them on through your payment provider rather than signing up with Apple or Google as a processor. On a provider's hosted checkout or invoices, that is usually a setting. On your own website it takes extra setup, including registering your domain with Apple. Either way, the payment still runs as a card transaction at your normal card rates.
A digital wallet payment is a card payment made through an app such as Apple Pay or Google Pay, which stores the customer's cards on their phone or account and sends a token to the merchant in place of the card number. The customer approves the payment on their device, and the merchant's processor handles it like any other card transaction.
How a wallet payment works
The customer taps the Apple Pay or Google Pay button, or holds the phone to a contactless terminal, and approves the payment with a card already saved in the wallet. Apple says every Apple Pay transaction on an iPhone or iPad requires Face ID, Touch ID or a passcode. The wallet then passes your provider an encrypted payment token instead of the raw card details. From there, the transaction is ordinary card processing.
That token is the main security benefit for the merchant. Apple's developer overview says merchants don't receive the customer's actual card numbers when customers pay with Apple Pay. Google's API returns a payment token too, though its FAQ draws a distinction: device-specific tokens with cryptograms are only available on Android devices, and on desktop browsers and iOS devices Google Pay returns the card from the customer's Google account instead. Your provider deals with the difference, but it explains why Google Pay on a laptop behaves more like a saved card than a phone tap.
Where you can accept wallet payments
In person
Any contactless-capable terminal or card reader can usually take Apple Pay and Google Pay, because a phone tap works like a contactless card. If your hardware takes tap-to-pay cards, check with your provider that wallet acceptance is switched on.
On payment links and invoices
This is the easiest route for most service and B2B businesses. When a customer opens a payment link or a payable invoice, the provider's page can show the wallet buttons next to the card form. Because the provider owns that page and its domain, the Apple registration work described below is usually the provider's job, but ask to be sure. Your part is confirming the wallets are enabled on your account and testing a payment from an iPhone and an Android phone.
On your own website
If the button sits on a checkout page on your own domain, you (or your developer) take on more of the setup. The steps for each wallet follow.
Setting up Apple Pay on your own website
Apple's documentation for Apple Pay on the web lists these setup tasks, completed in an Apple Developer account:
- Register a merchant ID. This identifies your business to Apple as a merchant able to accept payments. It never expires and can be used across several websites and apps.
- Create a payment processing certificate. Apple uses it to encrypt payment data, and you or your payment service provider use the private key to decrypt it for processing.
- Create a merchant identity certificate. This authenticates your website's sessions with Apple Pay's servers and is needed only for the web, not for apps.
- Register and verify every domain and subdomain where the Apple Pay button will appear. Apple says these domains cannot sit behind a proxy or redirect.
- Track the renewals. The merchant ID lasts indefinitely, but Apple notes that both certificates and the domain verification expire.
Many payment providers do some of this for you, for instance by holding the processing certificate or registering your domain through their own Apple account. Ask yours which steps it covers before your developer starts. Apple also requires sites using Apple Pay to follow its Apple Pay Acceptable Use Guidelines.
Setting up Google Pay on your own website
Google Pay on the web works through the Google Pay API. Google's overview says you should first check that your processor or gateway is on Google's list of supported processors and follow that provider's instructions, and that every merchant must follow Google Pay's brand guidelines. A direct integration, where you handle the payment data yourself, is limited by Google to merchants that are compliant with the PCI Data Security Standard, which is rarely worth it for a small business when a supported gateway is available.
Apple Pay and Google Pay for business, side by side
| Apple Pay | Google Pay | |
|---|---|---|
| Where customers pay online | Websites in Safari and apps, per Apple's developer overview | Websites and Android apps through the Google Pay API |
| How the customer approves | Face ID, Touch ID or passcode on the device | Through the customer's Google account or Android device |
| What the merchant receives | An encrypted token, not the card number | A payment token; device tokens on Android, the account's saved card elsewhere |
| Own-website setup | Merchant ID, two certificates, verified domains | Supported processor's integration, brand guidelines |
| Extra wallet fee | Not listed on Apple's developer overview; confirm with your provider | Google's FAQ says it charges no additional fees |
What wallet payments cost
A wallet payment costs what the card inside it costs. Google's FAQ states that Google Pay doesn't charge merchants additional fees and that merchants continue to pay their processor's fees. So a wallet payment carrying a premium rewards credit card is priced as that card, and one carrying a debit card is priced as debit.
The same logic applies to surcharging, which card networks allow on credit cards only. Say you run a surcharge program at a hypothetical 3% and a customer pays a $385 invoice through Apple Pay:
- If the card in the wallet is a credit card, the surcharge is $385 × 3% = $11.55, for a total of $396.55.
- If it is a debit card, there is no surcharge, and the customer pays $385.
Your payment software has to identify the card behind the wallet token and apply the fee only where it is allowed, which is a good reason to run surcharging as a built-in program rather than adding a fee by hand. Our guide to debit card surcharges explains why debit is excluded, and state rules on surcharging vary, so confirm yours with your processor.
Why wallets matter on invoices
Most invoices sent by text are opened on a phone. Without a wallet, paying a $1,200 invoice on a phone means finding the card and typing a 16-digit number on a small keyboard, then the security code and often a billing ZIP code. With a wallet the customer taps the button and looks at the screen. Every step you remove is a step at which a customer can no longer decide to "do it later" and forget.
That is why wallets belong on the payment page of every invoice and text-to-pay request, as well as on an online store. When you compare providers, ask which of their pages show the wallet buttons: the hosted payment page, payment links, invoices, or only an API checkout. The REST API that PayLink configures for clients accepts Apple Pay and Google Pay alongside cards and ACH.
Frequently asked questions
Do my customers need an iPhone to pay with Apple Pay?
They need an Apple device with Apple Pay set up, such as an iPhone or iPad. Apple's developer overview describes Apple Pay on the web as working in Safari; ask your provider whether its checkout shows the button in other browsers. Customers without an Apple device would use Google Pay or enter a card instead, which is why most payment pages show both wallet buttons above an ordinary card form.
Can a customer dispute an Apple Pay or Google Pay payment?
Yes. A wallet payment is a card transaction, so the cardholder can dispute it with their card issuer under the card network's rules, just as with a card typed into a form. Device authentication makes some kinds of fraud harder, but disputes over the work or the amount work exactly as they would otherwise. Our guide to chargebacks covers the process.
Can I accept wallet payments for recurring billing?
That depends on your provider. Some let a customer set up a subscription or saved payment method with a wallet at checkout, which the provider then stores as a token for later charges. Ask your provider whether its recurring billing and stored-card features accept wallet-originated cards, and test a renewal before relying on it.
Sources
- Apple Developer: Apple Pay overview, accessed 15 November 2026
- Apple Developer Documentation: Apple Pay on the Web, Configuring Your Environment, accessed 15 November 2026
- Google for Developers: Google Pay API for Web overview, accessed 15 November 2026
- Google for Developers: Google Pay API FAQ, accessed 15 November 2026