# Phone as POS: What You Can (and Can't) Do > Published: 2026-07-29 > Updated: 2026-07-29 > Author: Mathias Nielsen > Category: Hardware > Canonical: https://finalpos.com/blog/phone-as-pos-what-you-can-and-cant-do A phone can run your entire register and, with Tap to Pay, read contactless cards by itself. Here is the honest split: what a phone handles on its own, and the four hard limits no app can fix. A phone can be a complete point of sale, and the "can't" list is shorter than the hardware catalogs suggest. A phone as POS means the register half (catalog, cart, checkout screen) runs as software, and on a supported iPhone or NFC-equipped Android the phone is also the card reader, with nothing plugged into it. What remains off-limits comes down to a few hard rules from the card industry, plus some ergonomics worth weighing before a busy Saturday. Device support and payment certifications shift often, so treat the specifics below as a snapshot, accurate as of publication in July 2026. ## What can a phone do as a POS? Everything the register does. A point of sale splits into two halves: the register, which is pure software, and payment acceptance, which is regulated. The register half is products, prices, taxes, discounts, customers, email and text receipts, and end-of-day reports, and a phone runs all of it as well as any purpose-built till. The same logic that puts [an old tablet back to work as a register](/blog/old-tablet-new-register-reusing-hardware) applies to the phone already in your pocket. The register is also where a phone beats the counter, because it moves. It walks a queue at rush hour, takes orders tableside, and rings up sales at a market stall or a pop-up. Sales sync to the same back office as every other till, so a phone till is a full till, not a satellite. ![Staff member ringing up orders on a phone POS while walking a cafe queue](https://hy9joxwes0n0bta4.public.blob.vercel-storage.com/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/07176e73222bddb7-phone-pos-line-busting.png) ## Can a phone accept card payments by itself? Yes, contactless ones. Tap to Pay turns the phone into the card reader: the customer taps a contactless card, a phone wallet, or a watch, and the sale completes with no extra hardware. What makes this possible is not the app but the certification stack behind it: a contactless entitlement (a per-app permission) from [Apple on iPhone](https://developer.apple.com/tap-to-pay/), and [PCI MPoC](https://www.pcisecuritystandards.org/standards/mobile-payments-on-cots-mpoc/), the card industry's security standard for accepting payments on ordinary phones, on Android. If you want the plain-language version of the feature first, start with [what Tap to Pay is and how to accept it](/blog/what-is-tap-to-pay-and-how-to-accept-it-with-final). One distinction saves a lot of confusion: customers tapping their phones to pay and merchants accepting payments on a phone are [two different features](/blog/mobile-tap-payments-vs-tap-to-pay-on-mobile). This article is about the second. ## What can't a phone do? Four hard limits, none of them fixable with a better app. - **It cannot read inserted or swiped cards.** A phone reads contactless only. When a card has to go in the slot (a chip-and-PIN fallback, a magstripe-only card, or an amount your customer's bank will not approve as a tap), you need a certified card reader (payment hardware tested and approved to handle card data). That is a card-industry rule, not an upsell. - **Tap to Pay is one device, start to finish.** The sale must be rung up and paid on the same phone. You cannot ring up an order on a browser till and take the tap on a separate phone. - **No taps in a web browser.** A browser can run your entire register, but phone-as-reader only works inside a native app that carries the certification. - **No unattended use.** Certification programs for phone acceptance are written for attended checkouts, meaning a staffed till. A phone strapped to a stand as a self-serve kiosk is not a certified setup. ## When is a phone the wrong tool? When throughput matters more than mobility. A dedicated certified terminal earns its place at a high-volume counter: bigger battery, a customer-facing screen, faster taps in sequence, and no chance the till doubles as someone's personal phone. Receipt printers and cash drawers can pair with a phone-based till, but juggling a phone over a cash drawer at rush hour is nobody's best workflow. If you are pricing that counter out, [the minimal hardware kit for a first-time merchant](/blog/minimal-hardware-kit-first-time-merchant) covers what to buy on day one. The useful part: this is an "and" decision, not "or". The same checkout can drive a phone on the floor and a terminal at the counter, and the sales land in one set of reports. ![Busy retail counter with a dedicated unbranded payment terminal, with a phone POS nearby](https://hy9joxwes0n0bta4.public.blob.vercel-storage.com/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/ac055f9c57f8eb98-busy-counter-terminal-vs-phone.png) ## How do you set a phone up as a POS? On Final, in a few minutes. Install the Final POS app and the phone registers as a [Native Station](https://finalpos.com/help/set-up-a-native-station), which supports Tap to Pay, [keeps selling offline](/blog/offline-sales-sync-final-pos), and pairs with printers, drawers, and card readers. Or open a [Virtual Station](https://finalpos.com/help/set-up-a-virtual-station) in the browser for the no-install version, register only. Tap to Pay connects automatically on supported devices once Final Pay is on, and there is no monthly software subscription either way. If your checkout was built by AI, nothing changes: [the flow carries the payment button](/blog/connecting-tap-to-pay-to-an-ai-pos-flow), and whichever reader the till uses picks it up. ## So, what can (and can't) a phone do as a POS? It can run your entire register and accept every contactless payment on its own, which for many businesses is most payments. It cannot read inserted or swiped cards, split a tap across two devices, take taps in a browser, or run unattended. If your sales are mostly taps and your counter moves, a phone is a real POS, not a starter kit. Rule of thumb: **a phone can be your whole POS until a card needs to go in a slot; that is the day you buy a certified reader.** When that day comes, [the Tap to Pay guide in the help center](https://finalpos.com/help/take-a-tap-to-pay-payment) shows how the phone and the reader run side by side. ## FAQ **Q: Can I use my phone as a POS with no extra hardware at all?** A: Yes, if your sales are contactless. The phone runs the register, and Tap to Pay on a supported iPhone or NFC-equipped Android reads contactless cards and wallets directly. The moment a card must be inserted or swiped, you need a certified card reader. **Q: Can a phone read chip or swiped cards?** A: No. A phone reads contactless payments only. Inserted chip cards and magstripe swipes require a certified card reader, which is a card-industry security rule rather than a vendor decision. **Q: Can the customer tap their phone on my phone?** A: Yes. Tap to Pay accepts contactless cards and phone or watch wallets such as Apple Pay and Google Pay. Two phones touching back to back is a normal, certified transaction. **Q: Can I ring up a sale on one device and take the tap on another?** A: No. Tap to Pay runs on one device start to finish: the sale must be rung up and paid on the same phone. It is also not available in a web browser. **Q: Does a phone POS work offline?** A: The register can. On Final, a Native Station keeps ringing up sales offline and syncs when the connection returns. Card payments generally need a live connection to authorize.