Apple Pay vs Google Pay: Security, Devices and Refunds

Apple Pay and Google Pay protect your existing eligible card’s number during in-store contactless payments. Card tokenization gives merchants a substitute number, a payment token, instead of your physical card number. Both Apple and Google explain this protection.

Everyday users need to check phone and card compatibility, merchant acceptance, and mobile wallet refunds. Small businesses must also distinguish contactless terminals from online checkout integrations.

How Apple Pay works in 3 steps

First, add an eligible card to Apple Wallet. Your issuer or its authorized provider creates a device-specific Device Account Number, stored in your device’s Secure Element, a protected chip.

Second, authorize typical iPhone in-store payments with Face ID, Touch ID, or your passcode. Some Express Mode payments skip this step.

Third, hold it near the reader. The contactless NFC connection sends the device token and a transaction-specific security code. The token isn’t single-use; the code changes per transaction. See Apple’s security explanation.

Google Wallet similarly creates a virtual card for eligible in-store cards. Tokenized purchases aren’t anonymous or fraud-proof: banks and merchants retain transaction records.

Apple Pay vs Google Pay: devices and contactless payments

For contactless card payments, Apple Pay uses compatible iPhones and Apple Watches, without native Android support. As of October 2026, Google Wallet’s phone-based card tap-to-pay requires a supported Android device, not an iPhone.

Feature	Apple Pay	Google Pay
Card storage app	Apple Wallet	Google Wallet in many markets
In-store number	Device Account Number	Virtual card number
Phone authentication	Face ID, Touch ID, or passcode, with exceptions	Android screen-lock verification
Acceptance	Eligible card, country, and merchant required	Eligible card, country, and merchant required

On Android, enable NFC, make Google Wallet the default NFC app, and meet its screen-lock and security requirements. Unlock the phone and hold it near the reader; follow any verification prompt. Google’s setup guide explains the checks.

Apple now permits authorized third-party contactless apps in supported markets, requiring eligible hardware, software, agreements, and entitlements. This doesn’t establish Google Wallet card tap-to-pay support on iPhone.

Online checkout and UPI are separate

Both offer web and app checkout where supported. Google Pay’s web checkout can work on participating websites, including through supported iPhone browsers.

Depending on the Google Pay integration, payment data can contain encrypted card numbers or network tokens. Online checkouts don’t always substitute device tokens; Google’s technical FAQ distinguishes these cases. Chrome autofill virtual cards are separate, with distinct eligibility requirements.

Windows shoppers may select Apple Pay in supported browsers, then scan the displayed code with a compatible iPhone or iPad to pay. Merchant, market, browser, and software restrictions apply. Apple’s payment instructions explain how.

Google Pay in India supports iOS UPI payments; UPI is separate from NFC card tap-to-pay.

Small shops selling online should test checkout separately from counter terminals, including a refund through the payment provider. Confirm successful payments match orders before changing staff payment procedures.

Check support and prepare for refunds

Apple Pay receipts may show the token’s last four digits instead of the plastic card’s. For returns, merchants may request your receipt and those digits. On iPhone, open Wallet > card > More > Card Number.

Refunds return to the original card; you may need the same device at the reader. Apple’s refund guide explains how.

Google Wallet returns may require your phone and virtual card’s last four digits. Google’s return instructions cover this.

Check merchant acceptance and wallet support for your phone, exact bank, card, and country first. Keep your receipt and locate the token’s last four digits.