How to Set Up Contactless Payments at Your Store (NFC, QR, and Wallet Methods)

Setting up contactless payments at a retail store in 2026 is a weekend project, not a quarter-long IT initiative. You need a processor account, an NFC-enabled card reader, a couple of signs at the register, and twenty minutes of staff training. That is the whole thing. The hardest decision is usually which processor to pick, and even that comes down to four reasonable options that all work.

The reason to bother: somewhere between half and three-fifths of U.S. in-store card payments now happen as a tap, not a swipe or an insert. That number was closer to 10% before 2020. Customers expect to tap. When they cannot, the register starts to feel dated, and the line moves slower. A tap takes about 6 seconds. A chip insert takes closer to 18. Multiply that across a busy lunch rush and the throughput difference is something a manager actually notices.

This post walks through the three flavors of contactless (NFC, QR, wallet), what hardware costs, what the fees actually are, the PCI compliance scope you stay in, and the order to do things if you are setting up a register from scratch or upgrading an old terminal. We will also cover the QR-only path for service businesses where there is no register at all.

There are three things people lump together under the word "contactless," and they work differently enough that it is worth naming them.

Near-field communication. The customer holds a phone, watch, or contactless card within an inch or two of the reader, and the terminal pulls a one-time token from the device that authorizes the charge. This is Apple Pay, Google Pay, Samsung Wallet, and the little wifi-looking symbol on the front of most credit and debit cards issued in the last five years.

Under the hood, NFC tap is EMV — the same secure-chip standard as inserting a chip card. It is not a magstripe replay. That matters for PCI scope (covered below) and for fraud rates, which are meaningfully lower for tap than for swipe.

The terminal (or a printed sign, or an invoice on a screen) displays a QR code. The customer scans it with their phone camera, which opens a hosted checkout page in the browser, and they pay there. This is how Stripe Payment Links, Square Online checkout, and most invoice payment links work in 2026.

The useful property of QR is that you do not need any hardware at all. A printed code taped to the counter works. An invoice emailed with an embedded QR works. For a service business with no register — a mobile dog groomer, a home repair contractor, a pop-up event vendor — QR is often the entire payment infrastructure.

Less common at small retail. Bluetooth Low Energy and proprietary mobile apps power things like Starbucks Mobile Order, where you pay in a brand-specific app before you arrive and then either show a code at pickup or have the app talk to the store on your approach. Unless you are building your own consumer app, you can ignore this category. It is mentioned for completeness because customers sometimes ask if a Deelo store can do "app payments" — they usually mean wallet (Apple Pay / Google Pay), not a custom retailer app.

There are three hardware paths for a physical register. Pick one based on volume, how much counter space you have, and whether you want a separate device or want your phone to be the terminal.

All three accept tap, chip, and swipe. All three handle Apple Pay, Google Pay, and Samsung Wallet because those just present an NFC token — the terminal does not know or care whether the tap came from a phone or a plastic card. There is no separate "Apple Pay setup." If your terminal accepts contactless, it accepts wallets.

A quick note on Tap to Pay on iPhone. As of 2026 it is supported in over 20 countries, requires iPhone XS or later running a recent iOS, and works with most major processors. It is the cheapest way to add contactless to a business that already has staff phones. The trade-off is that the phone is now a register, which means it cannot be the phone you also take calls on.

Two cost categories: hardware (one-time) and processing fees (per transaction). The big thing to know is that there is no contactless surcharge. A tap costs you the same as a chip insert. The fee structure is determined by card type (debit vs. credit, rewards vs. plain, in-person vs. online), not by how the card was presented.

The good news is that contactless payments do not push you into a more demanding PCI bucket. The card data never lives on your terminal in cleartext — it is tokenized at the chip or in the wallet, transmitted to the processor encrypted, and you never store a PAN (primary account number) anywhere your team can see it.

Most small retail businesses fit into one of two simplified PCI-DSS self-assessment categories:

What you do not need: a full Report on Compliance, a QSA audit, network segmentation, or any of the heavy enterprise PCI infrastructure. A small retail business accepting tap with a vendor-supplied terminal can usually complete the appropriate SAQ in under an hour per year. The processor will often prompt you to do it inside their dashboard.

The one thing worth double-checking: if your POS software runs on a general-purpose tablet or PC, make sure the card reader is connected directly to that device and the processor (not via some custom integration that touches card data). The moment your own code touches cleartext card data, your scope expands considerably.

If you are starting from zero and want to be taking taps by the end of the weekend, this is the order that works. Each step is half a day or less.

Square, Stripe, Clover, and Sumup are the four most common starting points for small retail. They all do contactless, they all handle wallets, and the fee structures are close enough that the choice usually comes down to ecosystem fit — what other tools you already use, what your accountant likes, whether you also sell online.

Account opening is usually 10-30 minutes online and takes 1-2 business days for the underwriter to approve. You will need business name and EIN (or SSN if sole prop), bank account for deposits, and basic identity verification. Underwriting can take longer for higher-risk categories (firearms, CBD, adult, certain travel), so factor that in.

If you bought a dedicated reader, plug it in and pair it. Most modern readers pair over Bluetooth in under five minutes — open the processor's POS app on your phone or tablet, follow the pairing wizard, the reader's light goes green. Countertop terminals usually ship pre-provisioned and just need wifi or ethernet setup.

If you are doing smartphone Tap to Pay, install the processor's app, sign in, accept the Tap to Pay terms, and you are done. iOS will prompt you to enable the contactless reader entitlement the first time you start a payment.

Most processors include a basic POS app. The default behavior is "charge a custom amount" — the staff types in $24.99 and hits charge. Fine for a coffee cart, not enough for a real store. Spend a couple of hours loading your top SKUs, setting up tax rates by location, and configuring tipping (if applicable) so checkout becomes a tap on the product, not data entry.

This is also where you connect to whatever you use for accounting, invoicing, and customer records. If you run Deelo, the POS app feeds the customer record back to CRM, the invoice into Invoicing, and inventory back into Inventory automatically — no Zaps to wire up. If you run a best-of-breed stack, this is where the integration tax shows up; budget a half day to get the connectors built.

Two cheap pieces of signage make the conversion rate visible. The first is a small "we accept Apple Pay / Google Pay / contactless" sticker on the counter or near the terminal. The second is on the customer-facing display: when the staff hits charge, the screen should explicitly say "Tap, insert, or swipe" — not just "Insert card." Customers default to whatever the screen tells them to do.

Most processor terminals have a screen-message setting buried in admin. Worth ten minutes to change.

The 5% case is where the staff actually need training. Most taps work first try. When they do not, the script should be:

A 20-minute training and a one-page laminated cheat sheet at the register cover this entirely. Re-run the training when you hire someone new, not as a one-time event.

For a service business that does not have a register — a home cleaner, a tutor, a contractor, a small caterer — there is a path that skips hardware entirely. The customer pays from their phone, on their own device, after the work is done.

The flow:

Cost: nothing for hardware. Fees are slightly higher than in-person tap (card-not-present rates apply — typically 2.9% plus $0.30 at flat-rate processors), but you avoid the $200-400 terminal entirely and you can take payment anywhere there is a phone signal.

Deelo Invoicing generates the QR code automatically on every invoice and the hosted checkout page is on Deelo's domain, so the customer never sees a Stripe checkout URL even though Stripe is the processor under the hood. For a service business, this is often the entire payments setup — no terminal, no register, no monthly hardware fees. If you also do some in-person work and want to add tap later, Deelo POS pairs with the same reader hardware listed above and the customer record stays unified across both surfaces.

If you are doing more than $500K/year in card volume, the math on processors starts to matter more. Three things to know.

If you are building a new register from scratch, Deelo POS is what we run. It accepts NFC tap, chip, and swipe through any of the supported readers (Stripe Terminal, Square hardware via the Square plugin, or smartphone Tap to Pay on iPhone). It generates QR codes for any sale that needs hosted checkout. And every transaction flows directly into the same customer record that your CRM, Invoicing, and Customer Portal apps read from — no Zaps, no nightly syncs, no "why is this charge showing up in Stripe but not in the CRM" reconciliation.

For a service business that wants the QR path only, Deelo Invoicing handles it without a register at all. Send an invoice, the QR is on it, the customer pays, and the payment lands in your books and your customer record at the same time. The Customer Portal app gives them a place to see their own payment history and pay outstanding invoices without you sending a follow-up email.

Deelo starts at $19 per seat per month for the entire platform. The processing fees are pass-through — what Stripe or Square would charge you anyway. The difference is that you are not paying for a separate POS subscription, a separate CRM subscription, a separate invoicing subscription, and a separate customer portal subscription on top.

Contactless is not a future-state technology anymore. It is the default. Customers under 35 reach for their phone or watch before their wallet, and the share of taps in U.S. in-store card volume has roughly quintupled since 2020. If your register cannot take a tap in 2026, the line is moving slower than the store across the street, and customers notice. The setup is genuinely a weekend project. The fees do not go up. The PCI scope does not get harder. The customer experience gets meaningfully faster. There is no good reason to still be inserting chip cards as the primary payment path.