Phone and mail order payments: the channel nobody scopes
By Sam Rivera, Founder, SentinelPanda · October 19, 2026 · 3 min read · PCI DSS
Nobody sets out to build a telephone payment channel. It appears the first time a customer says "can I just give you the number".
How the channel appears
Very few businesses decide to accept mail and telephone order payments. It arrives organically: a wholesale customer wants to settle an invoice, a corporate gifting order needs arranging, a client cannot make the online booking work, an elderly customer prefers the phone.
Someone takes the card, types it into whatever is available, and the business now has a second payment channel that nobody has scoped, trained for or documented.
What questionnaire applies
Where staff key cards into a web-based virtual terminal on an isolated computer, and no card data is stored electronically, SAQ C-VT is the form designed for it. It is short, but its eligibility conditions are specific — notably that the terminal is accessed from a single, isolated device and that card data is not stored electronically.
Where those conditions are not met — the terminal is used on a shared office machine alongside everything else, or details are recorded in a CRM — the channel falls into SAQ D instead. That is the common case, and the gap between "we use a virtual terminal" and "we meet the SAQ C-VT conditions" is where most businesses actually sit.
The paper and inbox trail
- A number written on a notepad while the customer reads it out, then thrown in a bin rather than shredded.
- A number typed into a help-desk ticket so a colleague can process it later, where it stays for the life of the ticket.
- A customer emailing their card details because it felt easier, and the email sitting in an inbox, a sent folder and a backup.
- A recorded call retaining the number and the security code, which Requirement 3.3.1 prohibits outright.
The rule that fixes most of it
One instruction does most of the work: nobody at this company writes a card number down, and nobody accepts one by email or message. If a customer sends one, the response is to delete it, tell them it has been deleted, and send a payment link.
It is a policy rather than a product, which makes it cheap and makes it fragile. It holds if the people taking payments know it, and if there is a comfortable alternative to offer the customer — which means having a payment link ready before you ask staff to stop taking numbers.
Getting it into the scope document
Add the channel to your list even if the volume is tiny. Assessors and acquirers are not primarily interested in volume; they are interested in whether your description of how you take cards is complete.
A channel accounting for two per cent of revenue and none of the paperwork is a worse position than the same channel documented honestly, because the first implies the rest of the document may be incomplete too.