Licensing compliance

Taking card payments by phone: PCI basics

What a plumbing office must never write down, record or text when a customer pays by phone, and safer ways to take the card: links, keypads and readers.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing10 min read

On this page
  1. The card number is the risk, not the payment
  2. What never gets written, recorded or texted
  3. Why recordings are the hard part
  4. Safer ways to take a card by phone
  5. If a card has to be read aloud
  6. Card photos, texts and emails from customers
  7. What stays in the job record
  8. A monthly check for the office
  9. Frequently asked questions
  10. References
Licensing compliance: Taking card payments by phone: PCI basics79%: of US noncash payments were made by card in 2024, up from 71% in 2015LICENSING COMPLIANCETaking card payments byphone: PCI basics79%of US noncash payments were made by card in 2024, up from 71%in 2015Ava for PlumbersInsightsLicensing compliance: Taking card payments by phone: PCI basics79%: of US noncash payments were made by card in 2024, up from 71% in 2015LICENSING COMPLIANCETaking card paymentsby phone: PCI basics79%of US noncash payments were made bycard in 2024, up from 71% in 2015Ava for Plumbers
Figure source: Board of Governors of the Federal Reserve System, 2026[1]

Key takeaways

  • Writing a card number down, or letting a recording or voicemail capture it, counts as storing it under PCI guidance[2].
  • The security code can never be kept after the payment is authorized, even encrypted and even if the customer agrees[2][3].
  • Card details never travel by text or email[2]; a payment link, keypad entry or a card reader keeps them off your desk.
  • When a card must be read aloud, pause the recording, type straight into the processor and note only the approval reference.

The card number is the risk, not the payment

Every plumbing office takes a card over the phone sooner or later. A landlord pays for a tenant's water heater from another state. A snowbird settles an invoice from Florida. A customer wants the deposit done before the install date so the heater can be ordered. None of that is unusual, and none of it is a problem until the card number ends up somewhere it should not be: on a sticky note, in a job note, in a call recording or in a text thread on someone's phone.

Cards are how customers pay. They made up 79% of US noncash payments by number in 2024, up from 71% in 2015[1]. The payment card industry's own guidance explains why phone payments get extra attention: chip cards have cut fraud at the counter, so criminals increasingly go after card-not-present channels such as telephone orders and online checkout, and a phone payment exposes the card details in the clear[2].

Cards' share of US noncash paymentsShare of noncash payments by number of transactions.
Cards' share of US noncash paymentsColumn chart. 2015: 71%; 2021: 77%; 2024: 79%.0%20%40%60%80%2015: 71%71%20152021: 77%77%20212024: 79%79%2024Cards' share of US noncash paymentsColumn chart. 2015: 71%; 2021: 77%; 2024: 79%.0%20%40%60%80%2015: 71%71%20152021: 77%77%20212024: 79%79%2024

Source: Board of Governors of the Federal Reserve System, 2026[1]

Show the data
YearCard share
201571%
202177%
202479%

The PCI Data Security Standard is the rulebook card brands expect every merchant to follow, including a two-truck shop, and your processor holds you to it through your merchant agreement. It has also grown: of the 64 new requirements in version 4, 51 were future-dated and took effect on March 31, 2025[4]. The practical way through is not to learn every requirement. It is to keep card data off your paper, phones and systems, so fewer requirements apply to you.

What never gets written, recorded or texted

Three rules for every phone payment
  • Security code

    Never kept once the payment is authorized: not encrypted, not with the customer's permission

  • Full card number

    Never on paper, in job notes, in texts, in emails or in photos on a phone

  • Recordings

    No card details left in call audio, voicemail or transcripts after the payment

Drawn from PCI Security Standards Council guidance on telephone payments and card security codes[2][3].

The security code is the hard line. PCI guidance treats it as sensitive authentication data that must not be stored after authorization, even if encrypted[2]. A customer's request or approval to keep it has no validity under the standard[3], so “just keep it on file for next time” is never an option, however good the customer relationship.

  • Paper. A phone payment over an ordinary line is generally outside PCI scope, but if the person answering writes the card down, that counts as storage and pulls your office into scope[2]. That covers the carbon book, the back of a work order and the notepad by the phone.
  • Job notes and customer fields. A card number typed into a note in your field service software is stored card data in a system that was never built to protect it.
  • Texts, emails and chat. PCI guidance says never to send card data over unencrypted messaging such as text, email, chat or social media[2]. That applies to your staff texting it to the office and to the office emailing it to the bookkeeper.
  • Answering machines and voicemail. A machine that captures card details is storage in the same way paper is[2], and a customer who reads a card into voicemail has just created it for you.
  • Photos. A picture of a card on a technician's phone is stored card data on a device nobody secured for that purpose.

Why recordings are the hard part

Most plumbing phone systems record calls by default, for coaching and for disputes. The moment a customer reads out a card number and security code, both are in the audio, and if the system transcribes calls they are in searchable text too. PCI guidance notes that turning audio into queryable data is trivial for an attacker[2]. If a security code is received and recorded, the business must render it unrecoverable once the payment is authorized[2].

Pause-and-resume is the usual fix, and it is only as good as the person pressing the button. Guidance on manual pausing names both failure modes: staff forget to pause and capture the card, or forget to resume and lose recordings the business needed. Where it is used, the guidance recommends checking recordings for card data regularly, preferably weekly, and where a system cannot stop the audio being stored, the security code must be deleted from the recording as soon as the transaction is processed[2].

Example: a four-truck shop takes about 30 card payments a month by phone, every one read aloud on a recorded line. That is 360 recordings a year holding a card number and a security code, each one sitting in the phone system's storage, available to anyone with a login. Moving those payments to links takes all 360 out of the recordings without changing how anyone pays.

Answering software follows the same rule as staff. If an SI Employee picks up your overflow or after-hours calls, give it an approved answer for payment questions, for example that the office never takes card details over the phone and will send a secure payment link during business hours. Those calls are recorded and transcribed like any other, so card numbers have no place in them (how calls are handled).

Safer ways to take a card by phone

The best phone payment is one where nobody at your company hears the number. Each option below gets you closer to that. Most shops end up using two: links for invoices and deposits, and a reader in the truck for payment on completion.

Options for a plumbing office, from least to most card data handled by staff. Ask your processor which ones your account supports.
MethodWho sees the card numberWhat ends up in recordingsBest for
Card reader at the jobNobody; the card is tapped or insertedNothingPayment on completion, at the door
Payment link from your processorThe customer and the processorNothing, if staff stay off the detailsInvoices, deposits, after-hours holds
Card stored by the processor (card on file)Nobody after the first paymentNothingProperty managers and service agreements
Keypad entry with masked tonesNobody, when the tones are maskedMasked or suppressed tonesOffices taking many phone payments a day
Staff type into the processor while on the callThe person typingThe spoken number, unless recording is pausedThe occasional caller who cannot use a link

Payment links do the most for the least effort. PCI guidance says sending a customer a link to a secure online payment page may be treated like an online shop redirecting to a third-party payment page, so the card goes from the customer's phone to the processor and never through your systems; the effect on your scope still has to be checked, and the link itself has to be genuine[2]. Generate links only inside your processor's dashboard, never paste a link someone emails you, and tell the customer on the call which number or address the link will come from.

A fee quoted on the phone does not have to be paid on the phone. In the 8-truck company example, the after-hours fee would be read from a written script before anyone is woken; the payment that follows can still happen by link or by card reader at the door. For holds before a night visit, see card authorizations before night dispatch; for deposits on installs, see deposits on plumbing jobs.

If a card has to be read aloud

Some customers will not use a link: an older homeowner without a smartphone, a caller on a landline, someone who simply wants it done now. Keep a voice method for them, and make it a written routine rather than whatever the person answering happens to do.

  1. Take it at a desk

    Use the office line and the processor's own screen. Not a speakerphone in the van, not a personal cell, not a call transferred to a technician's phone.

  2. Pause the recording first

    Pause before the customer starts reading, and say so out loud, so the customer hears it and the pause sits on the file.

  3. Type straight into the processor

    No notepad and no scrap paper, even for a second. If the screen freezes, ask the customer to read the number again rather than writing it down.

  4. Confirm only the last four

    Read back the last four digits, never the full number. Staff screens should show at most the first six and last four[2].

  5. Resume and log the reference

    Switch recording back on, then note the approval reference, amount, date, last four and who took it. Never the full number, never the security code.

Example script: “I can take that now. I'm pausing our call recording before you read the card. ... It's paused, go ahead.” Then, after approval: “That went through, approval code ending 4471, card ending 0193. I've turned the recording back on. Your receipt goes to the email we have on file.”

Check the routine, not just the rule. Once a week, play a handful of recorded calls that included a payment and confirm the pause happened at the right moment, which is the weekly check PCI guidance recommends where staff pause manually[2]. One missed pause is a recording to fix that day. A pattern of misses means the method is wrong for your office, and links or keypad entry should take over.

Card photos, texts and emails from customers

Customers will text you a photo of their card, or type the number into an email reply to an invoice, because it feels quick to them. Do not process it, do not forward it, and do not leave it sitting in the thread. Reply with a payment link instead, then delete the message and the photo, including from deleted-items folders and the phone's recently deleted album.

Example reply: “Thanks, Maria. For your security we can't take card numbers by text, so I've deleted that message. Here is a secure payment link for invoice 2318 from our payment processor. Please delete the photo on your side too.”

The FTC's advice to small businesses is blunt: don't keep customer credit card information unless you have a business need for it, keep anything you do need only as long as necessary, and shred paper rather than binning it[5]. A plumbing company has no business need for a card photo once a link has been paid.

What stays in the job record

A clean payment record answers a chargeback without ever holding the card. Keep the approval reference, amount, date and time, last four digits, payment method, who took it and the invoice it paid. That is enough to prove the charge was authorized, which is most of what a chargeback response needs.

Printed receipts have their own federal rule. A business that accepts cards may not print more than the last five digits of the card number, or the expiration date, on an electronically printed receipt given to the customer[6]. Most portable readers truncate automatically. Check one receipt from each device anyway, especially older printers in the office.

The stakes go beyond the processor's fines. Every state, plus D.C., Guam, Puerto Rico and the Virgin Islands, requires businesses to notify people when their personal information is exposed in a security breach[7], and a stolen notebook full of card numbers is exactly that kind of event. The broader picture of what your shop holds, from addresses to gate codes, is in securing customer data.

A monthly check for the office

  • Walk the office and the trucks: no card numbers on paper, whiteboards, job folders or clipboards.
  • Search job notes and customer fields for 15- and 16-digit numbers, and remove any you find.
  • Search staff texts and the shared inbox for card photos and numbers; delete them and reply with links.
  • Play a sample of recorded payment calls and confirm the pause worked.
  • Check that each person who takes payments has a personal login to the processor, not a shared password.
  • Confirm former employees no longer have processor, phone system or email access.
  • Print or view one receipt from each card device and check the truncation.

Your processor or bank decides how you prove compliance each year, usually a self-assessment questionnaire, and the form depends on how you take cards. Tell them about every method you use, including links and phone payments typed by staff. The fewer ways card data reaches your people, the shorter that form gets. If your state's privacy law applies to you, read state privacy laws for small businesses alongside this.

Frequently asked questions

Is it legal to take a credit card number over the phone?

Yes. Phone payments are normal, and a payment over an ordinary phone line is generally outside PCI scope. What brings your office into scope is storing the details: writing them down or capturing them on a machine or recording[2].

Can we keep the security code if the customer asks us to?

No. Card verification codes must not be stored after authorization, and a customer's request or approval to keep them has no validity under PCI DSS[3].

Our phone system records every call. What should we do about payments?

Move as many payments as possible to links or keypad entry. Where staff take cards by voice, pause the recording before the number is read and check recordings weekly; if card codes still get recorded, they must be deleted once the payment is processed[2].

Can a customer text us a photo of their card?

They can send it, but you should not use or keep it. PCI guidance says card data should never travel over unencrypted channels such as text or email[2]. Send a payment link and delete the message.

What should our receipts show?

On electronically printed receipts, no more than the last five digits of the card number and no expiration date[6]. Most card readers do this automatically; check each device once.

References

  1. Board of Governors of the Federal Reserve System (2026). Federal Reserve Payments Study: National Payment Volumes, Top-Line Data (CY 2015–24) (opens in a new tab) ↑

  2. PCI Security Standards Council (2018). Information Supplement: Protecting Telephone-Based Payment Card Data (v3.0) (opens in a new tab) ↑

  3. PCI Security Standards Council (2017). FAQ: Can card verification codes/values be stored for card-on-file or recurring transactions? (opens in a new tab) ↑

  4. PCI Security Standards Council (2025). Now is the Time for Organizations to Adopt the Future-Dated Requirements of PCI DSS v4.x (opens in a new tab) ↑

  5. Federal Trade Commission (2016). Protecting Personal Information: A Guide for Business (opens in a new tab) ↑

  6. Legal Information Institute, Cornell Law School (U.S. Code) (2026). 15 U.S. Code § 1681c: Requirements relating to information contained in consumer reports (opens in a new tab) ↑

  7. National Conference of State Legislatures (2022). Security Breach Notification Laws (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo