Migrating off QuickBooks Desktop POS? See our switching from QuickBooks POS for the complete 2026 transition playbook.

Key Takeaways

• Apple Pay and Google Pay are NFC tap payment methods that use tokenization to eliminate the transmission of actual card numbers during transactions
• Accepting tap payments requires a terminal with NFC capability, which all PaymentCollect PAX terminals support
• Tap payment transactions process faster than chip or swipe, reduce fraud liability for card-present transactions, and do not carry additional processing fees beyond the standard card network rate
• Consumer adoption of tap payments has grown significantly, and businesses that don’t accept them are beginning to see friction at checkout

Last Updated: May 2026

When a customer holds their phone near your payment terminal and the transaction completes in under two seconds, something interesting has happened behind the scenes. No card number was transmitted. The customer’s actual payment credential never left their device. What the terminal received was a one-time-use token, and that token cannot be reused or counterfeited for a future transaction.

This is what makes tap payments like Apple Pay and Google Pay different from every other card payment method, and it is why businesses that accept them are in a measurably stronger security position than those that don’t. According to Apple’s 2023 developer data, Apple Pay is now accepted at more than 90% of U.S. retail locations that accept contactless payments, and consumer adoption continues to accelerate. By 2024, tap-to-pay transactions accounted for more than 25% of in-person card payments in the United States, according to Visa’s published transaction data.

How Apple Pay and Google Pay Actually Work

Both payment methods use Near Field Communication (NFC) technology, which allows short-range wireless communication between the customer’s device and your terminal when they are within a few centimeters of each other.

When a customer adds a card to Apple Pay or Google Pay, the actual card number is replaced with a device-specific account number, a token, that is stored securely in a dedicated chip on the device. When a payment is initiated, the device generates a one-time dynamic code that is valid only for that specific transaction.

What your terminal receives is the token plus the transaction-specific code. The card network uses these to authorize the transaction and then communicates the approval back to the terminal. At no point does your terminal, your POS software, or your transaction records contain the customer’s actual card number.

For merchants, this has two direct practical benefits. First, because no real card data is transmitted, there is no real card data to steal from your system. Second, fraud liability for tap transactions, where a stolen card is used to make a fraudulent purchase, falls on the card issuer rather than the merchant, because the device authentication (Face ID, Touch ID, or a device passcode) makes it significantly harder to use a stolen device for payments.

Do Apple Pay and Google Pay Cost More to Process?

No. Apple Pay and Google Pay transactions route through the same card networks as the underlying card in the customer’s wallet. An Apple Pay transaction funded by a Visa credit card processes at the same interchange rate as a standard Visa chip transaction.

There is no surcharge, no additional gateway fee, and no Apple or Google transaction fee charged to the merchant. Both companies make their revenue from the card issuers, not from merchants.

The only cost difference, in some cases, is that tap transactions using a tokenized device account may qualify for slightly different interchange tiers than a physical chip transaction. For most standard consumer cards, the rates are equivalent. The interchange rate applies to the underlying card type, not the payment method used.

“One of the most persistent misconceptions in retail payments is that contactless and digital wallet payments cost more,” says payments consultant Jason Richelson, founder of Shopkeep POS. “They don’t. And the security benefits they provide, including reduced chargeback exposure, often produce a net cost reduction for merchants willing to look at total processing costs rather than just rate lines.”

What Hardware Do You Need to Accept Tap Payments?

Accepting Apple Pay, Google Pay, and other NFC tap payments requires a terminal with an NFC reader. All PAX terminals supported by PaymentCollect include NFC capability.

The PAX A80 (Ethernet/WiFi, countertop) and PAX A920Pro (4G/WiFi/Ethernet, battery operated) are both NFC-enabled. The PAX A35 and PAX A77 are as well. There is no hardware upgrade required to accept tap payments if you are already using a PaymentCollect-supported terminal. It is a native feature, not an add-on.

The terminal’s NFC antenna is typically on the face of the device or near the card slot, and most modern PAX terminals display a contactless payment symbol to signal to customers that tap is available. A small detail worth verifying: if you have had your terminal for several years and are not sure whether customers are regularly attempting tap and failing, a quick test with your own phone will confirm whether NFC is active and working.

Visit the payment terminals page to see the NFC specifications for each PAX model.

Apple Pay vs. Google Pay: Are They Different for Merchants?

From a merchant processing perspective, Apple Pay and Google Pay are functionally identical. Both use NFC, both tokenize the underlying card credential, and both route through the same card networks as the customer’s associated payment method. The authorization, settlement, and QuickBooks posting process is the same for both.

The differences between the two are entirely on the customer side: Apple Pay works on iPhones and Apple Watches, and Google Pay works on Android devices and some Wear OS watches. Samsung Pay, which uses both NFC and a legacy magnetic secure transmission technology, is largely replaced by Google Pay on current Samsung devices.

For merchants, there is no configuration difference between accepting Apple Pay and Google Pay. If your NFC terminal is active, it accepts both. Your processing statement will not differentiate between Apple Pay and Google Pay transactions by payment method; they simply appear as the underlying card type (Visa, Mastercard, etc.) in the contactless or NFC transaction category.

Customer Experience Benefits That Affect Your Business

Tap payments are faster than chip transactions. A chip transaction requires the card to remain in the terminal for the duration of the authorization, typically four to eight seconds. A tap transaction completes in under two seconds.

That speed difference is barely noticeable for one transaction. For a business with a lunch rush, a peak period at a farmers market, or a Saturday morning at a marina, it compounds. A queue of 15 customers that moves 30% faster generates meaningfully more revenue during a fixed-duration peak period.

Consumer expectations around tap payment acceptance are also shifting. According to a 2023 JD Power survey on retail checkout experience, 42% of consumers under 40 reported that not being able to use their phone or smartwatch to pay created a negative impression of the business. For businesses catering to younger customers or in competitive retail environments, tap acceptance is increasingly a baseline expectation, not a premium feature.

How Tap Payments Reduce Chargeback Exposure

Chargebacks are a real cost for merchants, and tap payments reduce exposure to the most common category: fraudulent use of a stolen card.

A physical credit card that is stolen can be used at any terminal that accepts magnetic stripe or chip transactions. The stolen card number is the only credential needed. But a stolen phone requires the fraudster to also bypass the device’s biometric or PIN authentication before Apple Pay or Google Pay will authorize a transaction. That additional authentication layer dramatically reduces the incidence of fraudulent tap transactions.

For the fraud-based chargebacks that do occur on tap transactions, the liability typically rests with the card issuer rather than the merchant, because the merchant provided a secure, device-authenticated transaction environment. This is the same liability shift logic that applies to EMV chip transactions, extended to tap payments.

The combination of EMV chip acceptance and NFC tap acceptance on PaymentCollect’s terminals creates the most defensible fraud liability position available for card-present transactions. The PCI compliance page covers the broader security framework that surrounds these technical protections.

Tap Payments and Your QuickBooks Integration

Tap transactions post to QuickBooks through the PaymentCollect QuickBooks Online plugin exactly the same way as any other card transaction. There is no separate reconciliation step, no separate account category, and no additional mapping required.

Your QuickBooks account will show the transaction as the underlying card type (Visa, Mastercard, etc.) at the applicable processing rate. The payment method used at the terminal, whether chip, swipe, or tap, does not create a separate line item in QuickBooks. The integration handles all of it automatically.

For bookkeepers and accountants, this means the adoption of tap payments by your customers creates no additional work on the accounting side. The same integration that handles chip and swipe transactions handles tap transactions without modification.

What to Tell Your Staff About Tap Payments

For most staff, the instruction is simple: when a customer reaches for their phone instead of their wallet, they can tap the phone near the contactless symbol on the terminal. The transaction completes the same way a chip transaction does, and the terminal will indicate approval with the same confirmation.

A few practical notes for staff training:

1. The customer does not need to open a specific app. Holding the phone near the terminal with the screen on (and authenticated on iPhone) initiates the payment automatically.
2. The transaction amount must be displayed on the terminal before the customer taps; the customer is authorizing a specific amount.
3. If a tap attempt fails, ask the customer to try again. First attempts occasionally fail if the phone is not held close enough to the NFC antenna.
4. Tap does not require a PIN or signature for most transactions under $100 in the U.S. For higher amounts, the terminal may prompt for additional verification depending on the card issuer’s rules.

Summary

Apple Pay and Google Pay are NFC tap payment methods that use one-time token technology to process transactions without transmitting actual card numbers. They process at the same interchange rates as the underlying card, add no merchant fees, complete faster than chip transactions, and reduce fraud liability for card-present purchases. All PaymentCollect PAX terminals support NFC tap payments natively, and tap transactions post to QuickBooks automatically through the same integration as all other payment methods.

Frequently Asked Questions

Does accepting Apple Pay cost more than accepting a regular credit card?

No. Apple Pay transactions route through the same card networks as the underlying card in the customer’s Apple Wallet. The interchange rate is based on the card type, not the payment method used. Apple does not charge a merchant fee.

Do I need any special setup to accept Apple Pay on my terminal?

If your terminal has NFC capability, no additional setup is required. All PaymentCollect PAX terminals include NFC. Confirm that the contactless symbol is visible on your terminal face to signal to customers that tap is available.

What if a customer’s tap payment doesn’t go through?

Ask them to hold the phone or watch closer to the terminal face, near the contactless symbol. Ensure the transaction amount is displayed before they attempt the tap. If the issue persists, the customer can insert their chip card as an alternative. Contact PaymentCollect support if the NFC reader is consistently failing.

Are tap payments more secure than chip card payments?

In some ways, yes. Tap payments using Apple Pay or Google Pay add a device authentication layer (Face ID, Touch ID, or PIN) that physical chip cards do not require. Tokenization also means no actual card number is transmitted during the transaction.

Do contactless payments work for higher-value transactions?

Yes, though issuers may require additional authentication for larger amounts. Most U.S. issuers allow tap payments up to standard transaction limits. For very large transactions, the terminal may prompt for chip insertion or PIN entry as an additional verification step depending on the issuer’s rules.

Can customers use a smartwatch to pay at my terminal?

Yes. Apple Watch with Apple Pay and Wear OS watches with Google Pay both work through the same NFC tap process as a phone. The authentication happens on the watch before the payment is initiated. No additional configuration is required on the terminal side.

How do tap payments appear in QuickBooks?

Through the PaymentCollect integration, tap transactions post as the underlying card type (Visa, Mastercard, etc.). The payment method (tap vs. chip vs. swipe) does not create a separate category in QuickBooks. Your books treat tap transactions the same as any other card payment.

Conclusion

Tap payments are not a future-state technology. They are a current expectation for a growing portion of customers and a security upgrade for merchants who currently rely on chip-only acceptance. PaymentCollect’s PAX terminals support NFC tap natively, which means if you are already using the platform, your customers can already pay with their phones and watches at your register.

If you want to confirm your terminal’s NFC configuration or discuss an upgrade to a terminal with additional mobile capability, contact the PaymentCollect support team or talk to sales about the current terminal options.