Key takeaways
- The safest phone payment is one where card numbers never pass through your office: send a payment link or a bank payment request while the customer is on the line.
- If you key cards into a virtual terminal, never write details down, and never keep the security code: it must not be stored after authorisation, even encrypted[1].
- Pause or exclude call recordings during payment, or the recording itself becomes card data you must protect.
- Late payment is a real pressure: 45% of construction SME employers called it a major obstacle in 2025, up from 36%[2]. Taking payment on completion by phone helps.
- Treat requests to change bank details, overpay and refund, or split across several cards as fraud signs until proven otherwise.
Why phone payments matter for trade firms
Plumbing and heating firms take money at awkward moments. The engineer finishes a repair and the customer is at work; a landlord needs to pay a deposit for a cylinder; an elderly customer would rather pay by phone than online. Getting paid at the point the job is done makes a big difference to cash flow. Late payment was a problem for 63% of UK SME employers that gave trade credit in 2025[3], and construction SMEs felt it most: 45% named late payment as a major obstacle, up from 36% a year earlier and the highest of any sector[2].
Source: Department for Business and Trade (GOV.UK), 2025[2]
Show the data
| Item | Value |
|---|---|
| 2024 | 36% |
| 2025 | 45% |
Phone payments solve part of that problem, but they create another. Card numbers read aloud in a busy office, scribbled on a pad or captured in a call recording are exactly what fraudsters look for. The aim is to get paid quickly while keeping card details out of your business as far as possible.
Four ways to take payment remotely
| Method | How it works | Card details pass through you? | Best for |
|---|---|---|---|
| Payment link by text or email | Customer opens a secure page from your payment provider and pays on their own phone | No | Most domestic jobs, deposits and invoices |
| Bank payment request | Customer approves a payment in their banking app, or pays by bank transfer to details on your invoice | No card involved | Larger amounts, landlords, business customers |
| Virtual terminal | Staff key the card number into a provider's web page while the customer reads it out | Yes, briefly | Customers who cannot use a link |
| Card reader on site | Engineer takes payment in person at the end of the job | No (card stays with the customer) | Customers at home when the job finishes |
Make the payment link your default and use the virtual terminal as the fallback. A link sent during the call, with the office staying on the line while the customer pays, is as quick as reading out a card number and keeps the number off your desk entirely.
The rules when you do take card details
Anyone who accepts card payments agrees to follow the Payment Card Industry Data Security Standard (PCI DSS) through their payment provider. The card industry's guidance on telephone payments is blunt about the most important point: sensitive authentication data, which includes the three-digit security code a customer may read out on a call, must not be stored after authorisation, even if it is encrypted[1]. In practice, for a small firm that means:
- Key card details straight into the provider's virtual terminal while the customer speaks. Never write them on paper, a whiteboard or a job sheet first.
- Never email, text or message card numbers, even internally.
- Never save card details in your job-management software, a spreadsheet or the notes field of a booking.
- Take payments only on devices and accounts that are up to date and protected with strong passwords and two-step sign-in.
- Limit who can use the virtual terminal, and give each person their own login.
Your payment provider will usually ask you to complete a short annual self-assessment questionnaire. Using payment links rather than keying cards yourself usually makes it much simpler, because less of your business handles card data.
Call recordings and card numbers
Many trade firms now record calls for training or disputes. A recording that captures a customer reading out their card number and security code turns your phone system into a store of card data. The card industry's guidance says that if sensitive authentication data is received and recorded, it must be rendered unrecoverable once authorisation is complete, and that preventing it from being recorded in the first place is best practice[1]. If any part of your phone set-up is outsourced, you and the provider must be clear in writing about who secures what[1].
The simplest fix is not to take card numbers by voice at all. If you must, use a phone system with a pause-and-resume recording button, or one that masks the keypad tones when the customer types the number in, and check the recording afterwards to make sure the pause worked.
A safe payment call, step by step
Confirm the job and amount
'The invoice for today's repair at 18 Station Road is ready. Would you like to pay it now by card?'
Offer the link first
'I can text you a secure payment link now. Is this the best mobile for it?' Send it while you are still on the call.
Stay on the line
'You should see a text from us with the amount. Let me know when it has gone through.' Check your provider's dashboard as they pay.
Fallback: virtual terminal
If they cannot use the link, pause recording, key the card straight into the terminal as they read it, and never repeat the full number aloud.
Confirm and send a receipt
'That's gone through, thank you. You'll get a receipt by email.' Resume recording if you paused it.
The address in the script is a placeholder. Read back only the amount and the last four digits of the card when confirming, never the full number or the security code.
Fraud signs to watch for
Payment fraud against small firms often starts with a convincing phone call or email. 43% of UK businesses reported a cyber security breach or attack in the 12 months before the 2025 government survey[4], and phishing was by far the most common type, experienced by 85% of those affected[5]. Be cautious when a caller:
- Wants to pay far more than the job and asks you to refund the difference to another account.
- Offers several cards in quick succession after the first is declined.
- Is in an unusual hurry for a large job they have not discussed in detail.
- Asks you to change the bank details you pay a supplier, or claims your own bank details have changed.
- Asks you to read out a one-time passcode sent to your phone.
The rule for all of these is the same: stop, end the call if needed, and verify using a number or channel you already trust.
Deposits and the cancellation period
For larger jobs booked by phone or online, domestic customers usually have a cancellation period that ends 14 days after the contract is made[6]. Taking a deposit by payment link is sensible for parts you must order, but take it in a way that is easy to refund, and explain on the call and in writing what happens if the customer cancels. For urgent work you start straight away, make sure the customer's express request to start within the cancellation period is recorded in your confirmation.
Business customers and late payers
Letting agents, landlords with companies and commercial clients usually pay by bank transfer on invoice. Agree terms before the first job and put them on every invoice. For business-to-business debts, you can charge statutory interest of 8% plus the Bank of England base rate on late payments[7]. Few small firms use that right, but quoting it politely in a reminder letter often moves an invoice up someone's pile.
Refunds and disputed payments
Refunds are where phone payments go wrong most often, because they are rare and nobody remembers the process. Write it down. Refund only to the card or account that made the original payment, through your payment provider's dashboard, never to a different card or bank account the customer gives you on the phone. If a customer disputes a card payment with their bank, the provider will ask you for evidence, so keep the job sheet, the customer's written approval of the price, completion photos and the payment receipt together in the job record. A payment link has an extra advantage here: the provider's record shows that the customer entered their own card details on their own device, which is useful if anyone later claims they never agreed to pay.
Example: moving a firm off card numbers
Example: a fictional three-engineer firm took most payments by having customers read card numbers to the office manager, who wrote them on a pad before keying them in. After reading the card industry's telephone guidance, they switch to payment links sent by text during the call, with the virtual terminal kept for the few customers who cannot use a link. The office manager shreds the old pads, recording is paused during any keyed payment, and the provider's annual questionnaire becomes shorter. Payment on completion becomes routine, so fewer domestic invoices are left outstanding. For larger jobs paid in parts, see stage payments for bigger jobs.
Frequently asked questions
Is it safe to take card payments over the phone?
It can be, if card details go straight into your provider's system and are never written down, stored or recorded. Sending a secure payment link is safer still, because the card number never passes through you.
Can I write down a customer's card number to process later?
No. Key it directly into the virtual terminal while the customer reads it out, and never keep the security code after the payment has been authorised.
What if my phone system records calls?
Pause recording during card payments, use tone masking, or avoid taking card numbers by voice. Check that recordings do not contain card details.
Can I charge interest on late invoices?
For business customers, yes: statutory interest of 8% plus the Bank of England base rate applies to late business-to-business payments.
References
PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑
Department for Business and Trade (GOV.UK) (2025). Longitudinal Small Business Survey 2025: SME employers (businesses with 1 to 249 employees) (opens in a new tab) ↑
Department for Business and Trade (GOV.UK) (2025). Longitudinal Small Business Survey 2025: SME employers (businesses with 1 to 249 employees) (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
Department for Science, Innovation and Technology (GOV.UK) (2025). Cyber security breaches survey 2025 (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2013). The Consumer Contracts (Information, Cancellation and Additional Charges) Regulations 2013, regulation 30 (opens in a new tab) ↑
GOV.UK (2026). Late commercial payments: charging interest (opens in a new tab) ↑