Pereiti prie pagrindinio turinio
Visi straipsniai
POSJul 30, 2026

Tap to Pay on iPhone for restaurants and bars: how it works and what you need

Tap to Pay on iPhone lets staff take contactless payments on an iPhone, with no separate card reader. The guest taps a contactless card, or a digital wallet on their phone or watch, against the iPhone, and the payment app sends the payment to its provider for authorisation. To use it in the UK you need an iPhone XS or later on an up-to-date version of iOS, a payment app that supports Tap to Pay, and an account with a payment provider that offers it in the UK.

Apple introduced Tap to Pay on iPhone in the UK on 13 July 2023, and Stripe lists the United Kingdom among the countries where it supports it. In a restaurant or bar it is most useful wherever staff move around: at the table, on a terrace or at the door of an event.

How does Tap to Pay on iPhone work?

The iPhone's built-in NFC reads the card or wallet. Apple's 2023 UK announcement says every Tap to Pay transaction is encrypted and processed using the iPhone's Secure Element, and that Apple does not know what is being purchased or who is buying it. Apple's UK business page adds that Apple does not store card numbers or PINs on its servers, and that encrypted card numbers are stored temporarily on the iPhone only for transactions made in Store and Forward mode, the offline mode some payment apps can offer.

It accepts contactless debit and credit cards, Apple Pay and other digital wallets, including Android wallets, although some contactless cards may not be accepted depending on the payment app. Through Stripe, it supports Visa, Mastercard, American Express and Discover contactless cards and NFC wallets, and customers can enter a PIN on the iPhone screen when one is needed.

What do you need for Tap to Pay on iPhone in the UK?

  • An iPhone XS or later on a current version of iOS. Apple's page says it requires the latest version, and Stripe's documentation notes that it does not work on beta releases of iOS.
  • iOS 16.4 or later for PIN entry, which some payments require.
  • A payment app that supports Tap to Pay on iPhone, connected to a payment provider account that offers it in the UK.
  • Another way to take the payments Tap to Pay cannot, such as a card reader or a payment link.

Staff need a few minutes of training. Stripe advises holding the card against the iPhone until it has read the chip, which can take a few seconds after the first vibration. Apple requires payment apps to show merchants a "How to Tap" guide when the feature is turned on, and it is worth walking new starters through it before their first shift.

When does a guest need to enter a PIN or insert their card?

Some contactless payments need extra verification. Stripe says payments above certain amounts can require a PIN, which Tap to Pay on iPhone supports on iOS 16.4 or later. Wallet payments such as Apple Pay and Google Pay usually do not need a PIN.

In the UK, depending on the card issuer, Strong Customer Authentication can require some cards to be inserted into a reader. Tap to Pay cannot accept an inserted card, so those payments are declined before the PIN screen appears and Stripe recommends taking payment another way. Contactless limits can also differ between issuers: FCA rule changes that took effect in March 2026 let banks and payment providers with strong fraud controls set their own limits, although the FCA expects most to keep their existing ones. Keep at least one card reader in the venue for the payments a phone cannot take.

When is Tap to Pay a better fit than a card reader?

Tap to Pay suits serving points that move or only open some of the time: table payment in a restaurant without enough handheld readers, a terrace or garden bar, a pop-up, a ticket desk at the door, or a backup when a reader fails mid-service. Staff can take the order and the payment on the device already in their hand.

A dedicated reader is the better choice at a busy counter that handles most of your volume, for cards that need chip and PIN, and anywhere you want a customer-facing screen.

On Stripe's standard UK pricing in July 2026, Tap to Pay adds 10p per authorisation to the in-person rate. At that price, 2,290 Tap to Pay payments add up to the £229 list price of a Stripe Reader S700, so a phone makes most sense where volumes are modest or the alternative is a reader that would sit idle most of the week.

Plan on Tap to Pay needing a connection. Apple supports offline Store and Forward mode on iOS 18.4 or later where the payment provider offers it, but Stripe's offline mode does not cover Tap to Pay payments in the UK, so a UK venue using Stripe should not plan on taking Tap to Pay payments during an internet outage.

How does Tap to Pay on iPhone work in Tiquo?

Tiquo supports Tap to Pay on iPhone, so staff can take supported contactless payments without a separate card reader. Availability depends on the iPhone model, operating system, country and connected Stripe account, and Tiquo's Staff iOS app needs iOS 26 or later. Tap to Pay is for iPhone only: on iPad, Tiquo takes card payments through a connected card terminal.

The guest taps a contactless card or digital wallet against the iPhone. The payment is processed through Tiquo Payments, stays linked to the order and appears in reporting like any terminal payment, and when a payment needs a PIN the guest enters it on the iPhone screen.

For the payments a phone cannot take, Tiquo's hardware page lists the S700 and S710 card readers at £229 plus VAT each, and the S710 adds built-in 4G/LTE for a terrace or garden with weak wifi. Tiquo's mesh network keeps orders and tabs in sync between supported devices during an internet outage, but offline card payments remain subject to Stripe Terminal, device and risk eligibility, so treat Tap to Pay as a way to take payment while the iPhone is online.

© 2026 Tiquo. "Tiquo" ir Tiquo logotipas yra registruoti Tiquo Ltd prekių ženklai.

GDPR · CCPA · PCI DSS · ICO · Cyber Essentials Certified · EU–US DPF · SOC 2 Type II (in progress) · ISO 27001 (in progress)

Security & Operational

  • 99.99% SLA Uptime
  • AES-256 encryption at rest
  • TLS 1.3 in transit
  • AES-256 / TLS 1.3
  • Perfect Forward Secrecy (PFS)
  • HTTP Strict Transport Security (HSTS)
  • 99.999999999% (11 nines) data durability
  • Automated backups
  • DDoS protection
  • Web Application Firewall (WAF)
  • Zero Trust posture
  • Role-Based Access Control (RBAC)
  • Principle of Least Privilege
  • Secret scanning in CI
  • SBOM generation
  • Dependency supply-chain controls
  • 24/7 infrastructure monitoring
  • GDPR Article 22 safeguards
  • Data Protection Impact Assessments (DPIAs)
  • Records of Processing Activities (ROPA)
  • SAML 2.0 SSO
  • EASIE SSO
  • OAuth 2.0 / OpenID Connect (OIDC)
  • SCIM 2.0 provisioning
  • MFA / 2FA enforcement
  • Responsible disclosure / bug bounty programme

Privacy, Data Protection & Statutory Obligations

  • ICO Registered
  • UK Modern Slavery Act 2015 compliant
  • UK Public Interest Disclosure Act 1998 compliant
  • EU Article 27 Representative appointed (Paris, France)
  • Swiss FADP Article 14 Representative appointed
  • UK GDPR compliant
  • EU GDPR/DSGVO compliant
  • UK Data Protection Act 2018 compliant
  • Swiss revFADP compliant
  • CCPA / CPRA compliant (California)
  • VCDPA compliant (Virginia)
  • CPA compliant (Colorado)
  • CTDPA compliant (Connecticut)
  • TDPSA compliant (Texas)
  • OCPA compliant (Oregon)
  • MCDPA compliant (Montana)
  • FDBR compliant (Florida)
  • ICDPA compliant (Iowa)
  • ICDPA compliant (Indiana)
  • TIPA compliant (Tennessee)
  • DPDPA compliant (Delaware)
  • NJDPA compliant (New Jersey)
  • NHDPA compliant (New Hampshire)
  • NDPA compliant (Nebraska)
  • MCDPA compliant (Minnesota)
  • MODPA compliant (Maryland)
  • KCDPA compliant (Kentucky)
  • RIDTPPA compliant (Rhode Island)
  • Canada PIPEDA compliant
  • Quebec Law 25 compliant
  • Alberta PIPA compliant
  • British Columbia PIPA compliant
  • Singapore PDPA compliant
  • Hong Kong PDPO compliant
  • Brazil LGPD compliant
  • Japan APPI compliant
  • Australia Privacy Act / APPs compliant
  • India DPDPA 2023 compliant
  • Thailand PDPA compliant
  • Malaysia PDPA 2010 (as amended 2024) compliant
  • New Zealand Privacy Act 2020 compliant
  • South Africa POPIA compliant
  • UAE PDPL compliant
  • Mexico LFPDPPP compliant
  • Kenya Data Protection Act 2019 compliant
  • Ghana Data Protection Act 2012 compliant
  • Nigeria NDPA 2023 compliant
  • Indonesia PDP Law 2022 compliant
  • Philippines Data Privacy Act 2012 compliant

Global Fiscal & E-Invoicing

  • EN 16931 - EU e-invoicing core standard
  • UBL 2.1 - Universal Business Language
  • Austria - RKSV
  • Belgium - Peppol BIS 3.0 (B2B)
  • Czechia - fiscalization
  • Croatia - Fiscalization 2.0
  • Denmark - Peppol BIS 3.0 (B2B)
  • France - NF525 / LNE / Infocert, Factur-X / PDP, E-Reporting
  • Germany - KassenSichV / TSE, DSFinV-K, GoBD, E-Rechnung B2B (XRechnung / ZUGFeRD)
  • Hungary - Online Szamla
  • Italy - Scontrino, FatturaPA (via SDI)
  • Lithuania - i.SAF / i.MAS
  • Norway - Peppol BIS 3.0 (B2B), SAF-T
  • Poland - KSeF
  • Portugal - ATCUD/QR, SAF-T PT
  • Slovakia - eKasa
  • Slovenia - fiscalization (davcno potrjevanje)
  • Spain - FacturaE, SII, VeriFactu, TicketBAI
  • Sweden - SKVFS (certified cash registers)
  • Argentina - ARCA (Q4 2026)
  • Australia - Peppol PINT A-NZ (Q4 2026)
  • Brazil - NFe, NFCe, NFSe (Q4 2026)
  • Chile - SII Chile (Q4 2026)
  • Colombia - DIAN (Q4 2026)
  • Finland - Finvoice, TEAPPSXML (Q4 2026)
  • Japan - JP PINT (Peppol) (Q3 2026)
  • Malaysia - Peppol Malaysia (Q4 2026)
  • Mexico - CFDI (Q4 2026)
  • New Zealand - Peppol PINT A-NZ (Q4 2026)
  • Peru - SUNAT (Q4 2026)
  • Romania - Peppol (RO e-invoice) (Q4 2026)
  • Saudi Arabia - ZATCA (Q4 2026)
  • Singapore - Peppol BIS 3.0 (Q4 2026)
  • United Arab Emirates - Peppol (5C) (Q4 2026)

Standards & Frameworks

  • Cyber Essentials Certified
  • SOC 2 Type II - audit in progress
  • ISO/IEC 27001 - audit in progress
  • NIST Cybersecurity Framework - aligned
  • NIST Privacy Framework - aligned
  • NIST SP 800-53 / 800-63 / 800-63B - aligned
  • NIST AI Risk Management Framework - aligned
  • CIS Critical Security Controls / CIS Benchmarks - aligned
  • OWASP ASVS & OWASP Top Ten - aligned
  • ISO 25010 (quality) - aligned
  • ISO 31000 (risk) - aligned
  • ITIL - aligned
  • W3C Web Standards - aligned
  • OpenAPI Standard - aligned
  • DevSecOps practices - aligned
  • ePrivacy Directive - aligned
  • EU Whistleblowing Directive (2019/1937) - aligned

Payments Compliance

  • PCI DSS Level 1
  • PSD2 / Strong Customer Authentication
  • 3D Secure (3DS)
  • EMVCo Level 1 & 2
  • AML / KYC controls
  • Sanctions screening (OFAC, UN, EU, HMT)

International Data Transfer Mechanisms

  • EU-US Data Privacy Framework
  • EU Standard Contractual Clauses (Decision 2021/914) - Modules 2 & 3
  • UK International Data Transfer Agreement (IDTA) + ICO Addendum
  • Swiss FDPIC-recognised transfer mechanisms
  • APEC Cross-Border Privacy Rules (CBPR)

Accessibility Compliance

  • ADA (Americans with Disabilities Act) - aligned
  • European Accessibility Act (EAA) 2025 - aligned
  • WCAG 2.2 - aligned
  • EN 301 549 - aligned
  • WAI-ARIA - aligned

Viena platforma viešbučiams, SPA, užsiėmimams, renginiams ir restoranams.

Tiquo Ltd
Londonas, Jungtinė Karalystė

LinkedInTop Performer Spring

Naudojame slapukus

Pasirinkite, ar leidžiate naudoti analitinius ir reklaminius slapukus. Galite juos priimti arba atmesti. Uždarius šį pranešimą, jie atmetami.

Sužinokite daugiau