QR Code Payments for Small Businesses: A Practical UK Guide

A payment QR code is a picture of a web address. When a customer scans it, their phone opens a checkout page. The code itself does not move any money; it is simply a fast way to get the customer to the right payment page without typing a link.

That point is important for merchants. Scanning a code does not confirm payment. The payment only exists once the customer has completed checkout and your provider has confirmed it.

The customer opens their camera or QR scanner and points it at the code. Their phone shows the web address, and they tap to open it. The checkout page loads with the amount and any description, so they can check they are paying the right business the right amount.

They then choose an available payment method and confirm. Depending on the provider, that may be a mobile wallet, a card form or a bank payment. Once the provider confirms the payment, the merchant sees the status update and the customer usually sees a confirmation or receipt page.

QR payments for shops and service businesses work best where customers have their phones to hand and a short delay is acceptable.

A static QR code always opens the same page. It may be printed and left on a counter, and depending on the provider it might let the customer enter their own amount or always ask for the same fixed price. Static codes are convenient, but because they do not change, customers can make mistakes with amounts and it can be harder to match each payment to a specific sale.

A transaction-specific QR code is created for one payment request with a set amount. It is shown for that sale, so the customer does not type anything and the payment is linked to the request you created. This takes a moment longer, but reduces errors and makes your records clearer.

Many businesses use a mix: a fixed-price code for a standard item, and per-sale codes for anything priced individually.

Printed codes can be tampered with. A fraudster can stick a different code over yours that leads to a fake payment page. Check printed codes regularly, place them where you can see them, and consider showing codes on your own screen instead for one-off amounts.

Encourage customers to check that the page shows your business and the amount they expect before paying. Keep your codes up to date: if you change prices or replace a payment request, remove old codes so customers do not pay the wrong amount.

A few practical points make QR payments work smoothly day to day.

Phesky creates transaction-specific QR codes. After connecting your own Stripe account, you open Get Paid, enter the amount (at least £0.50) and optionally add a product name, a photo or a tip prompt. Phesky shows a QR code for that request on your screen, alongside a payment link you can share. Scanning the code and opening the link lead to the same checkout.

Phesky checkout supports Apple Pay and Google Pay only; there is no form for typing in card numbers. A wallet button appears only when the customer's device, browser and wallet set-up support it and Stripe confirms it is eligible. Some in-app browsers, such as those inside messaging and social apps, restrict wallets, so customers may need to open the link in Safari or Chrome.

While the QR code is on screen, Phesky watches for the payment to be confirmed and switches to a paid screen once Stripe reports success. The payment then appears in your dashboard with its confirmed status, and you can issue a refund from the payment details. Payments are direct charges on your connected Stripe account, and Stripe pays out to your bank on your payout schedule.

Phesky's application fee is £0.16 on a successful payment below £30, and 0.60% on a payment of £30 or more. That is only Phesky's share: Stripe's processing fees apply separately under your Stripe terms, so Phesky's fee is not your total cost. The pricing page shows worked examples that add both together for £10, £30 and £100 sales.

Phesky is not a contactless card terminal and does not accept NFC card taps. It is a way to show a code that opens a wallet checkout on the customer's own phone.

Before you accept QR code payments, test the whole journey on more than one phone, ideally an iPhone and an Android device, so you know what customers will see. Check mobile signal or Wi-Fi where you trade. Decide whether you will use per-sale codes, a fixed-price code or both, and how you will tell which payment belongs to which sale.

Keep a second way to pay for customers who cannot scan or do not have a suitable wallet. Put a short sign near your code explaining how to pay and what the checkout page should show. Check printed codes for tampering at the start of each day, and make it a habit to glance at your dashboard for the confirmed status before every hand-over. Write down your refund process so anyone working with you handles refunds the same way.

QR code payments in the UK can be a quick, low-hardware way for small businesses to accept payments, especially when each code matches a specific sale. Display codes safely, keep another way to pay for customers who need it, and always confirm payment in your own dashboard rather than trusting a scan or a screenshot. Explore Phesky's payment links and pricing, then create a free account to try QR payments.