Accepting Apple Pay and Google Pay

A customer holds a phone near your terminal and nothing happens. They try again, shrug and pull out a card, or they walk out. As wallet payments become routine, those small failures are lost sales and a small mark against how modern your business seems.

The good news is that accepting Apple Pay and Google Pay rarely requires special programs or separate agreements. It generally rides on the same contactless technology your terminal already uses for tap cards, and online it depends on your gateway. This guide explains what to check, how the security model works and what to tell your staff.

How wallet payments work

When a customer adds a card to a mobile wallet, the card network generates a device-specific token that stands in for the real number. At checkout the phone sends that token, plus a one-time cryptogram, over near-field communication to your terminal. Your terminal passes it to the processor like any other card payment, and the issuer recognizes the token and approves or declines.

Because the real card number is never shared with you, a stolen record from your system is useless to a criminal. The customer also usually authenticates with a fingerprint, face scan or passcode on the device, which adds protection beyond a plain tap card. To you, the sale looks like a card-present contactless transaction.

What your terminal needs

Wallet acceptance depends on the contactless reader, not on a special program. Check the following:

• The terminal has an NFC contactless reader, which most devices sold in recent years include.
• Contactless is enabled in the settings; some terminals ship with it switched off.
• Software and firmware are up to date so the latest wallet and card network requirements are supported.
• If you use a POS integration, the contactless option is passed through to the payment device.
• Signage shows the contactless symbol so customers know they can tap.

No terminal? Use the phone

Modern smartphones can act as the reader. Tap-to-phone software uses the phone's NFC antenna to accept contactless cards and wallets with no extra hardware, which suits mobile businesses and low-volume sellers. Availability depends on the phone model, operating system and provider, so confirm that your device and region are supported.

If you already own an older terminal that cannot do contactless, a small add-on reader or a replacement may be the answer, and some older devices can be reprogrammed. MCCPS checks existing equipment first, so you do not buy something you do not need.

Online and in-app wallet buttons

On a website, wallet payments appear as a button at checkout that lets the customer approve with their device instead of typing card details. This can speed up mobile checkout and reduce typing errors. The button is enabled through your payment gateway and, for Apple Pay on the web, may require domain verification. Your gateway documentation or support team can walk through it.

Wallet transactions online are card-not-present, but because they carry device authentication they are generally harder to defraud than typed numbers. Pricing is still based on the underlying card and your pricing plan.

Cost and common issues

There is generally no separate fee for the wallet itself; the transaction is priced like the card behind it. A tap sale is card-present, so it often costs less than a keyed one. If your statement shows wallet transactions priced oddly, ask for a review.

When a tap fails, the usual culprits are a contactless reader that is switched off, a customer holding the phone too far away, a phone case that interferes, an outdated terminal or a payment device placed behind glass. Move the reader within easy reach and train staff to suggest holding the phone close to the screen until the terminal confirms.

For businesses with several registers or employees, standardize the customer-facing moment. Decide where the reader sits, what the screen says and what staff say when a customer taps, so the experience is the same at every lane. Small touches, such as angling the reader toward the customer and clearing clutter around it, make taps succeed on the first try. Each failed attempt slows the line, so a minute spent on layout pays back all day.

Rollout steps

A short checklist gets you ready.

1. Confirm your terminal has contactless and that it is enabled.
2. Update software and firmware to the latest version.
3. Test with an Apple Pay and a Google Pay transaction on a real device.
4. Enable wallet buttons in your online gateway if you sell online.
5. Post contactless signage and brief staff.
6. Review the next statement to confirm pricing.

Need a hand?

MCCPS supports EMV and contactless acceptance, works with a wide range of terminals and phones, and provides free 24/7 technical support when a tap will not register. A free statement analysis shows how your tap and wallet sales are being priced. Call 844.826.6227 to get started.

This article is general information, not legal, tax or compliance advice. Card-network and state rules change — confirm current requirements before acting. Savings depend on your individual statement analysis.