NFC & Contactless

Also called contactless payments, tap to pay, NFC, Apple Pay, Google Pay, near field communication

Tap instead of dip. Same EMV security, faster, and wallet payments layer tokenization on top so the real card number never reaches you.

What it is

NFC — near field communication — is the short-range radio standard that lets a card or phone communicate with a terminal by tapping. Contactless payments run the same EMV cryptographic process as a chip dip; the difference is the interface, not the security. A contactless tap is an EMV transaction and carries the same liability protection. Wallet payments — Apple Pay, Google Pay, Samsung Pay — add a second layer. The wallet stores a device-specific token rather than the actual card number, and each transaction includes a cryptogram. That means the merchant never receives the real card number at all, which reduces both fraud exposure and PCI scope. From the merchant's side, a wallet tap and a contactless card tap look identical and price identically. Contactless is now the default expectation rather than a differentiator. Every current terminal supports it, Tap to Pay on phones is built on it, and transit systems, drive-thrus and quick-service counters have trained consumers to expect it. A business without contactless in 2026 reads as behind.

Why it matters to your business

Speed at the counter is revenue during season. A contactless tap is meaningfully faster than a chip dip, and across a lunch rush or a bar service that compounds into throughput. More importantly, contactless is the same EMV protection as a dip, so encouraging taps costs you nothing in liability and gains you time. If your terminal supports it and your signage doesn't tell customers, you're leaving the speed on the table for no reason.

Where it gets contested

The honest criticism of contactless is minor and mostly historical: early concerns about "skimming" a card from a distance were largely overblown, since NFC range is a few centimeters and the transaction still requires a valid cryptogram. The residual real complaint is accidental double-reads and cards charging when a wallet is placed near a terminal, which is a UX annoyance more than a security issue. The more substantive tension is about wallets specifically. When a customer pays with Apple Pay or Google Pay, the wallet provider sits between you and the card, and the tokenization means you never see the underlying credential. That's good for security and it does complicate card-on-file scenarios, recurring billing setups and some dispute processes. It also means the wallet providers accumulate transaction relationships and data that merchants historically owned. For merchants, though, the practical case is one-sided. Contactless is faster at the counter, produces the same interchange treatment as a chip dip, carries the same liability protection, and reduces terminal wear. There isn't a serious argument for not enabling it.

How to check it yourself

Confirm contactless is enabled on every terminal and handheld you own — including back-of-house and overflow devices, which often get missed. Then check that your terminal displays the contactless prompt clearly; many default to a chip-first screen that trains customers to dip.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

Visa has expanded access to Apple's Tap to Pay technology, built on the same NFC contactless standard
americanbanker.com ↗
Elavon markets EMV, NFC/contactless and mobile processing as standard acceptance capabilities in its agent program
elavon.com ↗
Contactless and wallet acceptance is standard across current smart terminals, which are roughly 36% of the POS terminal market
openpr.com ↗