Tap to Pay UK: How to Take Card Payments on Your Phone
Published - 11 January 2022
Revised - 27 August 2026


Libby James is the founder and Managing Director of Merchant Advice Service. Since 2016, she has worked directly with businesses and payment providers across merchant accounts, card processing, payment gateways and complex provider requirements.
Libby specialises in high-risk, declined and harder-to-place merchants, as well as businesses requiring specialist payment methods, integrations or international support. She writes and reviews Merchant Advice Service content, drawing on practical experience gained from real merchant enquiries and provider relationships.
Businesses can now take contactless card payments directly on a compatible smartphone without using a separate card reader or traditional payment terminal.
This is commonly known as:
A customer can tap a contactless debit or credit card, smartphone, smartwatch or supported digital wallet against the merchant's compatible phone to make an in-person payment.
In the UK, both iPhone and Android-based payment acceptance solutions are available through supported payment providers.
That means a smartphone can increasingly perform a role that previously required separate card-reader hardware.
But that does not mean a phone is automatically the right replacement for every card machine.
Businesses still need to consider:
Tap to Pay removes the separate terminal. It does not remove the payment provider, merchant onboarding or the need to design the payment process properly.
Tap to Pay allows a compatible smartphone or tablet to become a contactless payment-acceptance device.
The merchant typically:
The payment is then processed through the merchant's payment provider.
No separate contactless reader needs to be paired with the phone.
No.
This is an important distinction.
Apple Pay allows a customer to use an Apple device to make a payment.
Tap to Pay on iPhone allows a merchant to use an iPhone to accept a payment.
A customer could therefore use Apple Pay on their iPhone to pay a merchant who is accepting the transaction using Tap to Pay on another iPhone.
Likewise, customers may be able to pay using:
SoftPOS is an industry term for software-based point-of-sale technology that turns a compatible commercial smartphone or tablet into a payment-acceptance device.
Instead of requiring dedicated payment-terminal hardware, the payment application uses capabilities already built into the phone, including its NFC interface.
You may also see terms such as:
COTS means Commercial Off-The-Shelf device — such as a normal smartphone or tablet rather than a purpose-built payment terminal.
SoftPOS is the technology category. Tap to Pay is the customer-friendly way many providers describe the experience.
A simplified payment journey looks like this:
Payment app → smartphone NFC → customer's contactless card/device → payment provider → acquiring and card network → issuer authorisation.
The phone replaces the dedicated physical point-of-sale terminal at the merchant end of that journey.
It does not replace:
Yes.
Apple launched Tap to Pay on iPhone in the UK in July 2023.
Apple currently states that businesses can use a supported payment application to accept in-person contactless payments directly on a compatible iPhone without additional payment-terminal hardware.
Supported payment methods can include:
Apple currently states that iPhone XS or later is required and recommends using the latest version of iOS.
See Apple's current Tap to Pay on iPhone information.
Yes.
The iPhone does not simply become an unrestricted card terminal because it contains NFC hardware.
The merchant needs a payment-enabled application from a provider that supports Tap to Pay on iPhone.
The merchant will also normally need to:
Apple's current UK page lists a range of payment applications supporting the capability.
Yes, where the device and payment provider support it.
Android Tap to Pay and SoftPOS solutions can use the phone's built-in NFC capability to accept contactless payments without a separate card reader.
Requirements vary between providers and phone manufacturers.
They can include:
This means businesses should check their exact device rather than assuming that every Android phone with NFC will automatically work.
| Tap to Pay on iPhone | Android SoftPOS / Tap to Pay |
|---|---|
| Uses compatible iPhone hardware | Uses compatible NFC-enabled Android hardware |
| Requires a supported payment app | Requires a supported payment app |
| No separate reader required | No separate reader required |
| Accepts supported contactless cards and wallets | Accepts supported contactless cards and wallets |
| Device support controlled by Apple and payment provider | Compatibility can vary more widely by manufacturer, Android version and provider |
| Can form part of a wider POS environment | Can form part of a wider POS environment |
The better option will usually follow the devices, software and payment provider already used by the business.
No.
The payment application is on the merchant's device.
The customer simply presents a supported payment method in much the same way as they would at a traditional contactless terminal.
That might be:
No.
Despite the phrase “Tap to Pay”, the customer does not need a smartphone.
A normal contactless debit or credit card can also be presented to the merchant's phone where supported.
Tap to Pay primarily uses the contactless/NFC interface rather than physically inserting a chip card into the merchant's smartphone.
However, modern mobile-payment acceptance solutions can support cardholder verification including secure PIN entry on compatible commercial smartphones.
This is an important area of development.
The PCI Security Standards Council's Mobile Payments on COTS (MPoC) standard specifically supports payment solutions that can accept both:
using commercial off-the-shelf devices.
Actual PIN and high-value transaction functionality still depends on the particular payment provider, application, device and payment method.
Businesses should therefore check provider capabilities rather than assuming every SoftPOS implementation works identically.
Potentially, yes.
The £100 UK contactless threshold should not be interpreted as a universal maximum transaction value for every phone-based payment.
Whether a higher-value transaction can be completed depends on areas including:
For example, some modern provider implementations can support PIN entry directly through the merchant's smartphone for transactions requiring cardholder verification.
Businesses expecting high-value transactions should check this specifically before relying on Tap to Pay as their only card-present payment method.
Phone-based card acceptance should use a payment solution designed and assessed for this specific use case.
The PCI Security Standards Council maintains a dedicated security standard for modern mobile payment acceptance:
PCI Mobile Payments on COTS (MPoC).
MPoC establishes security and testing requirements for payment solutions operating on commercial devices such as smartphones and tablets.
The PCI SSC also maintains listings businesses and acquirers can use when identifying PCI-listed MPoC solutions.
Read the PCI SSC Mobile Payments on COTS information.
This is particularly relevant for businesses researching older SoftPOS guidance.
PCI SSC previously maintained separate standards including:
PCI SSC subsequently introduced the broader MPoC framework, combining and extending capabilities used in these earlier mobile-payment standards.
In 2026, PCI SSC announced the formal sunset period for both CPoC and SPoC from 1 May to 31 October 2026.
MPoC is therefore the more relevant framework when evaluating current-generation mobile payment-acceptance solutions.
“It's secure because it's on an iPhone” or “it's secure because it's on Android” is not enough. The payment solution operating on the device is what needs to be properly designed, supported and assessed.
Not automatically.
Using a properly designed mobile-payment solution can reduce how much payment data the merchant's ordinary systems handle.
However, businesses still need to understand:
A merchant that also accepts payments through:
may still have wider PCI DSS considerations.
See our PCI DSS Compliance Guide.
No.
This distinction is why much older mobile-payment content is now out of date.
Previously, taking card payments through a phone often meant:
phone + provider app + separate card reader.
Readers connected using technologies including:
With true Tap to Pay / SoftPOS:
the compatible smartphone itself becomes the payment-acceptance device.
No separate NFC reader is required.
No.
Dedicated payment hardware still offers advantages in many environments.
A purpose-built terminal may be preferable where the business needs:
Tap to Pay adds another card-present option. It does not make every traditional terminal unnecessary.
It can be particularly useful where payment acceptance needs to be flexible.
Examples include:
This is one of the more interesting uses for established retailers and venues.
Imagine a store has:
six permanent tills
but experiences major queues during:
Instead of installing permanent extra checkout hardware, appropriately equipped staff could potentially accept payments using managed smartphones and a supported payment application.
This can create temporary additional payment points.
Tap to Pay is not only a small-business alternative to buying a £30 card reader. For larger merchants, it can become a flexible additional endpoint within the payment estate.
For larger businesses, the question moves beyond whether one phone can take a payment.
The organisation may need to understand:
Phone-based acceptance can therefore become a device-management and payments-infrastructure decision at scale.
Events are another strong use case because additional payment capacity may only be required temporarily.
Potential advantages include:
But events also expose weaknesses quickly.
Check:
Yes, depending on the provider and restaurant setup.
It may be useful for:
However, a restaurant should compare Tap to Pay against a fully integrated portable card-machine setup if it requires:
Yes.
A retailer could potentially use phone-based payment acceptance for:
The important question is how the transaction integrates with:
For larger estates, see our Merchant Services for Multi-Location Retailers guide.
Potentially, yes.
This can be one of its strongest applications.
If a traditional terminal fails, a supported phone-based payment route may provide an alternative way to continue accepting contactless payments.
But it should be:
Downloading an app for the first time while customers are already queuing is not a resilience strategy.
It needs suitable data connectivity, but that may be provided using:
The exact requirement depends on the provider.
Businesses should check connectivity throughout the locations where staff will actually use the service.
Do not assume payments can continue offline.
Offline payment functionality varies significantly between payment products and can create different risk considerations.
The safer operational assumption is that the business needs a reliable supported data connection unless the provider explicitly confirms another workflow.
Potential alternatives might include:
A business using smartphones as payment endpoints needs device controls.
These can include:
Larger organisations may prefer corporate-managed phones rather than allowing staff to use unmanaged personal devices.
This requires careful consideration.
Technically possible does not necessarily mean operationally desirable.
Issues can include:
For larger organisations, a managed-device policy may provide stronger operational control.
Tap to Pay solutions can often provide digital receipt options through the payment application.
Depending on the provider, this might include:
If printed receipts are operationally important, a dedicated terminal with an integrated printer may still be preferable.
Usually through the payment provider's application or dashboard where supported.
Businesses should establish:
Potentially.
SoftPOS can be implemented as:
This is particularly important for larger merchants.
The most interesting question may not be:
“Can this phone accept a card?”
but:
“Can our existing application turn thousands of managed devices into payment-acceptance points?”
See our Integrated Card Machines & EPOS Compatibility guide.
There is no universal UK Tap to Pay transaction rate.
Costs depend on the provider and commercial arrangement.
Potential costs can include:
The absence of a separate card reader does not mean payment processing is free.
It can reduce hardware costs, but it is not automatically cheaper overall.
Imagine:
Option A has no terminal rental but costs an additional 0.20% in processing.
Option B includes terminal rental but has lower transaction pricing.
For a merchant processing £200,000 per month, the additional:
0.20% = £400 per month
or:
£4,800 per year.
That could easily exceed the cost of dedicated terminal hardware.
This is an illustrative MAS calculation, not a provider-rate comparison.
See our Card Machine Costs UK 2026 guide.
Tap to Pay changes the hardware.
It does not change the fundamental economics of card processing.
Businesses should still analyse:
See our Card Machine Transaction Fees guide.
| Tap to Pay | Portable Card Machine |
|---|---|
| Uses compatible smartphone | Uses dedicated payment hardware |
| No separate terminal required | Separate terminal supplied |
| Can be highly flexible | Purpose-built for payment acceptance |
| Uses phone battery | Dedicated terminal battery |
| Digital receipts often central | Some models include printers |
| Can be strong for backup/temporary use | Can be strong for permanent high-volume use |
| Integration varies by provider/app | Established EPOS integrations widely available |
| Device management may sit with merchant | Terminal management may sit with provider |
The distinction becomes even clearer at a permanent checkout.
A countertop card machine may be better where the business needs:
Tap to Pay may be better where the business values:
Technically possible and operationally sensible are different questions.
Before replacing a terminal estate with phones, consider:
A hybrid estate can sometimes make more sense:
fixed terminals for permanent tills + portable terminals for hospitality + Tap to Pay for mobile staff and overflow.
The future of card-present payments does not have to be “terminal or phone”. For many established merchants, it will be a mixture of payment endpoints selected around the customer journey.
Yes — but often for a different reason from a micro-business.
A high-volume business may use it to:
The strategic value can therefore be operational flexibility rather than simply avoiding the cost of a card reader.
Merchant Advice Service would assess phone-based payment acceptance across six areas.
Why does the business want phones to accept payments — mobility, backup, queue busting, hardware reduction or application integration?
Do the business's iPhone or Android devices meet the provider's requirements?
Does the solution support the cards, digital wallets, transaction values and cardholder-verification methods required?
How will payments connect to EPOS, stock, customer records, reporting and refunds?
How does transaction pricing compare with dedicated-terminal alternatives at the merchant's actual volume?
How will the business manage devices, staff, charging, connectivity, security, support and failures?
Do not ask whether your phone can replace a card machine. Ask whether phone-based payment acceptance improves your payment operation.
Merchant Advice Service helps businesses compare payment-provider options based on the wider payment requirement rather than simply the hardware used to accept the transaction.
When considering Tap to Pay or SoftPOS, we may look at:
Businesses can explore payment providers through The Payments Directory® or read How Merchant Advice Service Works.
Apple confirms that supported UK businesses can accept in-person contactless payments using a compatible iPhone and supported payment application without additional payment-terminal hardware.
Apple launched Tap to Pay on iPhone in the UK in July 2023.
Apple — Tap to Pay on iPhone UK Launch
Apple's current business guidance explains how Tap to Pay on iPhone works with a merchant's payment provider and merchant identifier.
Apple Business — Tap to Pay on iPhone
PCI MPoC provides security and testing requirements for mobile payment-acceptance solutions operating on commercial devices such as smartphones and tablets.
PCI SSC — Mobile Payments on COTS
PCI SSC's current standards information confirms the 2026 sunset period for the earlier CPoC and SPoC standards as the mobile-payment ecosystem moves toward MPoC.
Merchant Advice Service is an independent payments information, comparison and provider-matching service.
MAS may receive commission or a referral fee from some payment providers where a business chooses to proceed following an introduction. This does not determine the factual information or provider-selection principles within this guide.
Tap to Pay, SoftPOS and mobile-payment functionality varies according to payment provider, device, operating system, card scheme, merchant setup and market.
Not every iPhone or Android device supports every mobile payment-acceptance product.
Apple currently specifies iPhone XS or later for Tap to Pay on iPhone and recommends the latest version of iOS. Android compatibility varies between providers and device manufacturers.
Higher-value transaction and PIN functionality varies between payment solutions. Businesses should confirm cardholder-verification capabilities with the relevant provider.
PCI MPoC provides the current PCI SSC framework for modern mobile payment acceptance on commercial devices. Using a mobile payment solution does not automatically remove all PCI DSS responsibilities from a merchant.
Provider pricing, supported hardware, operating-system requirements, card acceptance, security standards and integrations can change.
Merchant Advice Service does not guarantee provider acceptance, pricing, device compatibility or technical functionality.
Mobile payment and security information last checked: 27 August 2026
This guide provides general payments information and should not be treated as technical, legal, regulatory or PCI compliance advice.
Written or reviewed by Libby James, founder of Merchant Advice Service and specialist in merchant payments and complex provider requirements.