Brick-and-mortar retailers have relied on dedicated POS terminals for decades. But the hardware is expensive, the contracts are rigid, and every additional lane or pop-up location means another terminal to provision, certify, and maintain.
In-store payment links offer a different model. Instead of swiping or tapping a card on a terminal, the customer scans a QR code, taps an NFC tag, or receives an SMS — and completes checkout on a hosted payment page from their own phone. No POS hardware required. No PCI scope on the merchant's network. The payment is processed through the same infrastructure that powers online checkout.
This guide covers how in-store payment links work, where they outperform traditional POS, and why platforms serving physical retailers should pay attention.
What Are In-Store Payment Links?
A payment link is a URL that opens a hosted checkout page. Online merchants already use them in emails, invoices, and chat conversations. In-store payment links bring the same concept into physical retail by presenting that URL to a customer who is standing in front of you.
There are three common delivery methods for in-store payment links:
QR code at the point of sale — A dynamic QR code is generated for the transaction amount. The customer scans it with their phone camera, which opens the hosted checkout page. They pay with Apple Pay, Google Pay, or enter card details directly.
NFC tap — An NFC tag or tap-to-pay prompt on a tablet or phone triggers the payment page on the customer's device. This works well for counter service and kiosk environments.
SMS or WhatsApp at the register — The staff member enters the customer's phone number, and a payment link is sent instantly via text message. The customer pays on their phone without any physical device interaction.
In every case, the payment is processed through a PCI-compliant hosted page. The merchant never touches card data. The transaction settles through their existing payment provider, with the same reporting and reconciliation they use for online orders.
Why Retailers Are Adopting Payment Links In-Store
The shift toward in-store payment links is not about replacing every POS terminal overnight. It is about solving specific pain points that traditional hardware cannot address efficiently.
Queue busting. During peak hours, long checkout queues cost retailers sales. A staff member with a tablet can generate a payment link for customers waiting in line, letting them pay and leave without reaching the register. No additional POS terminal needed — just a device that can display a QR code or send a text.
No POS hardware dependency. POS terminals cost £300–£1,200 per unit, plus monthly fees, PCI certification costs, and maintenance contracts. Payment links require no hardware beyond what merchants already own — a phone, tablet, or laptop. This makes them ideal for pop-up shops, market stalls, seasonal locations, and any environment where provisioning a full POS terminal is impractical.
Line-item flexibility. Payment links can carry metadata — order reference, line items, customer ID, tip amounts. This is harder to achieve with a basic card terminal, which only captures an amount. For merchants who need itemised receipts or want to pass order context back to their platform, payment links offer richer data capture than a tap-and-go terminal.
Unified online and in-store payments. Many retailers already accept payment links for remote orders, phone orders, and invoicing. Using the same payment link infrastructure in-store means one reconciliation flow, one settlement process, and one set of reports — regardless of whether the customer was online or in the shop. Platforms that serve both channels benefit from a single integration that handles every scenario.
How In-Store Payment Links Work
The technical flow is straightforward and mirrors online payment link processing:
The merchant's system (POS software, platform dashboard, or staff app) creates a payment link via API, specifying the amount, currency, and any metadata such as order reference or customer ID.
The link is presented to the customer — as a QR code on screen, an NFC tap prompt, or an SMS/WhatsApp message.
The customer opens the link on their own device. The hosted checkout page loads with the pre-filled amount and any branding configured by the merchant.
The customer pays using Apple Pay, Google Pay, saved card, or manual card entry. 3D Secure authentication runs if required by the card issuer.
The platform receives a webhook confirming payment. The merchant's dashboard updates in real time, and a receipt is sent to the customer.
The entire process takes 15–30 seconds from scan to confirmation. Because the checkout page is hosted by the payment provider, the merchant's in-store network never handles card data — which dramatically simplifies PCI compliance and security.
In-Store Payment Link Use Cases
Payment links are not limited to traditional retail. Any business that collects payments face-to-face can benefit.
Retail and high street. Clothing stores, electronics retailers, and department stores use QR-based payment links for queue busting during peak periods. Staff on the shop floor generate links from a tablet, letting customers pay and collect their items without waiting at the till.
Hospitality. Restaurants, hotels, and bars use payment links for tableside checkout, room charges, and split bills. A server sends a QR code or SMS link to the table — the customer pays and tips on their own phone. No card machine changes hands, and the tip is captured digitally rather than in cash.
Events and festivals. Pop-up vendors at festivals, trade shows, and markets often lack reliable Wi-Fi for POS terminals. Payment links work over the customer's mobile data connection, so the vendor only needs a printed QR code or a phone to send an SMS. No terminal connectivity issues, no declined taps due to offline mode.
Field service. Plumbers, electricians, delivery drivers, and repair technicians collect payments on-site. Instead of carrying a card reader or invoicing later, they send a payment link by SMS before leaving the job. The customer pays immediately, and the platform records the payment against the job automatically.
Healthcare and professional services. Clinics, dental practices, and consultancies use payment links to collect co-pays, deposits, or session fees at reception. The patient scans a QR code while checking out, avoiding the need for a dedicated payment terminal at the front desk.
Phygital Payments: Blending Online and In-Store
The term phygital describes the convergence of physical and digital commerce. Customers browse online and buy in-store. They reserve in-app and pick up at the counter. They return in-store items purchased online. Every one of these journeys involves a payment that crosses the online/offline boundary.
In-store payment links are a core enabler of phygital commerce because they use the same payment infrastructure for both channels. A customer who pays via payment link in-store and later pays via payment link online has a single payment history, a single refund flow, and a single set of stored credentials. For the platform, this means one integration, one ledger, and one compliance surface.
This matters for platforms building multi-channel experiences. Rather than maintaining separate POS integrations (Stripe Terminal, Adyen in-person, Square hardware) alongside their online payment stack, they can route all transactions through payment links — whether the customer is on a website, in a mobile app, on a phone call, or standing at the counter.
Payment Links vs Traditional POS Systems
Payment links do not replace POS systems in every scenario. High-volume supermarkets processing thousands of transactions per hour still need dedicated hardware. But for many merchants, payment links handle 80% of in-store payment needs at a fraction of the cost.
Here is how they compare:
Hardware cost. A standard POS terminal costs £300–£1,200 upfront, plus monthly rental or leasing fees. Payment links require no dedicated hardware — merchants use devices they already own.
Setup time. POS terminal provisioning takes days to weeks, including PCI certification, network configuration, and software installation. A payment link integration can be live in hours through an API, with no on-site hardware configuration.
Scalability. Adding a new checkout lane or location with POS means ordering, shipping, and configuring another terminal. With payment links, scaling means printing another QR code or giving another staff member access to the link generator. There is no per-location hardware constraint.
Transaction speed. Contactless tap on a POS terminal is faster for a single item purchase — under 3 seconds. Payment links take 15–30 seconds including the QR scan and checkout page load. For complex transactions with line items, tips, or split payments, payment links are often faster because they handle all of that in the hosted page rather than requiring manual terminal input.
Maintenance. POS terminals need firmware updates, hardware replacements, and periodic PCI re-certification. Payment links are maintained by the payment provider — the merchant has no terminal to manage.
For platforms that serve merchants across multiple locations — particularly those in hospitality, field service, or pop-up retail — payment links dramatically reduce the operational burden of in-person payments. If you are evaluating in-store payment infrastructure, compare what Stripe Terminal and similar POS solutions require against what a payment link API delivers out of the box.
Cost Comparison: Payment Links vs POS Hardware
The cost advantage of in-store payment links becomes clearest when you look at total cost of ownership across a multi-location deployment.
Consider a platform serving 50 merchant locations, each needing two checkout points:
POS route: 100 terminals at £500 each = £50,000 upfront. Add monthly fees of £20–£40 per terminal (£24,000–£48,000/year), PCI certification costs per location, shipping and provisioning logistics, and hardware replacement for damaged or outdated units.
Payment link route: One API integration. Per-transaction pricing only — no hardware costs, no monthly terminal fees, no on-site provisioning. Merchants use existing phones or tablets. QR code stands cost under £10 each if the merchant wants a physical display.
Transaction fees for payment links are typically in line with standard card-not-present rates (1.5%–2.9% depending on the provider and card type). POS terminals benefit from lower card-present interchange rates (0.2%–0.3% lower in the UK). For merchants processing high volumes of low-value transactions, the interchange saving on POS may offset hardware costs. For merchants with moderate volume, seasonal spikes, or multiple locations, the payment link model is significantly cheaper.
Security and PCI Compliance Benefits
PCI compliance is one of the strongest arguments for in-store payment links. With a traditional POS setup, the merchant's network handles card data — which means PCI DSS requirements apply to the in-store network, the terminal, the connection between them, and any systems that store or transmit cardholder data.
With payment links, card data never touches the merchant's infrastructure. The customer enters payment details on a hosted page served by the payment provider. The merchant's in-store system only receives a payment confirmation webhook — no card numbers, no CVVs, no sensitive data.
This reduces the merchant's PCI scope from SAQ D (the most comprehensive self-assessment) to SAQ A (the simplest). For platforms, this means their merchants face fewer compliance requirements, lower audit costs, and reduced liability for data breaches. Learn more about how payment links simplify PCI compliance and card authorisation.
Additional security benefits include:
3D Secure authentication runs automatically on the hosted checkout page, reducing fraud and chargeback liability.
Payment links can be set to expire after a defined period, preventing stale links from being reused.
Each link is unique to a transaction, so there is no risk of amount tampering or replay attacks.
No card data is stored on the merchant's local network, eliminating the primary vector for in-store data breaches.
How Platforms Can Offer In-Store Payment Links
If you are a platform serving merchants with physical locations, adding in-store payment links to your product is simpler than integrating POS hardware — and it gives your merchants a payment method that works across every channel.
The integration path looks like this:
Generate payment links via API — Your platform creates a payment link for each in-store transaction, passing the amount, currency, merchant ID, and any order metadata.
Present to the customer — Render the link as a QR code on a screen, send it via SMS, or trigger it via NFC. Your merchant-facing app handles the presentation layer.
Handle webhooks — When the customer pays, your platform receives a webhook with the payment status, transaction ID, and metadata. Update the merchant's order system and trigger any downstream workflows.
White-label the checkout — The hosted payment page can carry the merchant's branding, so the customer experience is seamless. No redirect to a third-party site.
Shuttle's embedded payment infrastructure lets platforms generate white-labelled payment links across any channel — online, in-store, over the phone, or via chat. One API integration covers every payment scenario your merchants need. Explore how it works for platforms, or book a discovery call to see it in action.
FAQ: In-Store Payment Links
Can payment links replace POS terminals completely?
For many merchants, yes. Businesses with moderate transaction volumes, pop-up locations, field service operations, or seasonal retail can run entirely on in-store payment links. High-volume environments like supermarkets still benefit from dedicated POS hardware for speed, but even those retailers use payment links for queue busting and supplementary checkout points.
Are in-store payment links PCI compliant?
Yes. Because the customer enters card details on a hosted checkout page operated by the payment provider, the merchant never handles card data. This reduces PCI scope to SAQ A — the simplest compliance level. The merchant's in-store network only receives payment confirmations, not cardholder data.
Do customers need to download an app to pay?
No. Payment links open in the customer's default mobile browser. They scan a QR code or tap an NFC tag, and the checkout page loads in Safari, Chrome, or whatever browser they use. Apple Pay and Google Pay work natively on the page without any additional app.
What happens if the customer's phone has no internet?
The customer needs a mobile data or Wi-Fi connection to load the hosted checkout page. In practice, most customers have mobile data. For venues with poor signal (underground locations, large warehouses), providing guest Wi-Fi solves this. POS terminals face the same connectivity requirement — they need a network connection to authorise payments in real time.
How fast is checkout with an in-store payment link?
From QR scan to payment confirmation, the process typically takes 15–30 seconds. This is slower than a contactless tap on a POS terminal (under 3 seconds) but faster for complex transactions involving line items, tips, or split payments. For queue-busting scenarios where customers pay while walking the shop floor, the total time saved is significant because they skip the checkout queue entirely.