To accept a credit card payment over the phone, type the customer's card details and billing ZIP code into a virtual terminal while they are on the line, submit the charge and send a receipt. Don't write the details down, and never keep the card's security code once the payment is authorized. Safer still, text the customer a payment link during the call so they enter their own details.
MOTO payments (mail order/telephone order) are card transactions in which the cardholder gives their card details to the merchant by post or over the phone, and the merchant enters them for processing. They are card-not-present transactions, so the card's chip is never read and the merchant relies on other checks to confirm the buyer is genuine.
Before you take your first phone payment
Check two things with your processor. First, that your merchant account is set up for card-not-present payments, since an account approved only for in-person sales may not be. Second, that you have a virtual terminal, which is the screen staff use to key the payment. If you are new to that tool, our guide to what a virtual terminal is explains how it works and what keyed payments cost.
Then decide who in the business takes over the phone payments, and from where. A card number read aloud in an open office can be overheard by anyone nearby, so a desk away from the front counter is worth arranging.
What to collect on the call
| Detail | Why you need it | Keep it after the call? |
|---|---|---|
| Cardholder's name as it appears on the card | Identifies the payer and goes on the receipt | Yes, in the customer record |
| Card number | Required to process the charge | No, unless your provider stores it securely with the customer's consent for future charges |
| Expiration date | Required by the card issuer | No, other than as part of a securely stored card |
| Security code (the three or four digits on the card) | Lets the issuer check the caller has the card | Never, once the payment is authorized |
| Billing ZIP code or street address | Used for the address verification check | Not needed after the payment |
| Email address or mobile number | To send the receipt | Yes, in the customer record |
| Invoice or job number and amount | So the payment is recorded against the right balance | Yes |
The security code rule is the one that catches businesses out. The PCI Security Standards Council, which maintains the card industry's data security standard (PCI DSS), says storing card verification codes for card-on-file or recurring transactions is prohibited. It adds that the customer agreeing to it doesn't change that, and neither does encrypting the codes. If you plan to charge the customer again, the card has to be stored the proper way, which our guide to card on file explains.
Step by step: taking an over-the-phone payment
- Open the virtual terminal before you ask for anything, so you type the details straight into it rather than onto paper.
- Confirm the amount and what it covers with the customer.
- Ask for the details one at a time, and read back only the last four digits of the card number to confirm.
- Submit the payment while the customer is still on the line. If it is declined, tell them straight away and ask whether they would like to try another card.
- Check the address and security-code results. If either fails on a large payment from someone you don't know, pause before shipping goods or booking work.
- Send the receipt to the email address or mobile number they gave you, and tell them it is on its way.
A short script keeps staff consistent:
"I can take that payment now. The balance on invoice 1187 is $640. I'll enter your card straight into our secure payment system, and I won't write anything down. Could I have the name on the card, please? … Thank you, that's gone through. Your receipt is on its way to the email address we have on file."
What not to do
- Write card numbers on paper, even to type them in a minute later. Notes get left on desks and in bins.
- Take card details by email or from a voicemail. Both leave the full number sitting in a system you don't control. Call the customer back, or send them a link.
- Record calls without checking what the recording captures. In its guidance on telephone payments, the PCI Security Standards Council says digital audio recordings may not be used to store security codes after authorization if the recordings can be searched, and it advises using technology that stops those codes being recorded where it exists. If your phone system records calls, ask your provider how payment details are kept out of the recordings.
- Keep the card "for next time" in a spreadsheet or customer notes. Use your payment provider's secure storage, with the customer's consent.
The safer alternative: text a link while they're on the line
A payment link sent during the call does the same job without the card number passing through your staff. You say, "I'm texting you a secure link now," the customer opens it, types their own details on the payment page, and you see the payment arrive before you hang up.
| Card read out and keyed | Link texted during the call | |
|---|---|---|
| Who types the card number | Your staff member | The customer |
| Card data heard or seen by staff | Yes | No |
| Digital wallets | No | Yes, if the payment page offers them |
| Extra checks such as 3D Secure | No | Possible, depending on the payment page |
| Works for customers without a smartphone | Yes | No; keep the keyed option for them |
For more on sending payment requests by SMS, including consent and message wording, see our guide to text-to-pay.
What a disputed phone payment costs
The case for the link becomes clearer when a phone payment goes wrong. Say a garden supply yard takes a $1,200 phone order for pavers from a first-time caller and keys the card. A month later the real cardholder reports the charge as unauthorized, the issuer reverses it, and the pavers are gone. At a hypothetical 20% gross margin, the pavers cost the yard $960 ($1,200 × 80%), and that is gone along with the sale, plus whatever dispute fee its processing agreement sets. Earning back $960 at the same margin takes $4,800 of new sales ($960 ÷ 20%). Our guide to chargebacks covers the dispute process and what evidence helps.
No method makes fraud impossible: someone holding a stolen card number can type it into a payment page as easily as read it out. What the link changes is that your staff never handle the number, and the page can apply checks such as 3D Secure that a keyed payment can't.
Making phone payments part of the job flow
For field-service businesses, phone payments usually happen in the office while the work happens elsewhere: a customer calls to pay a balance, or a dispatcher takes a deposit while booking a visit. The less re-keying between the job and the payment, the fewer errors. We can set the office up with a virtual terminal that turns any computer or mobile device into a payment terminal for phone payments, with no extra hardware.
Frequently asked questions
Do I need my processor's approval to take payments over the phone?
Usually you need an account that is set up for card-not-present transactions, and some processors price or underwrite those differently from in-person sales. If your business has only taken cards at a counter so far, ask your processor whether your account covers phone payments before you start, rather than finding out from a held deposit.
Can I charge the same card again next month?
Only if the customer has agreed to it and the card is stored properly by your payment provider, not written down or saved in your own files. The card networks expect a clear agreement covering how and when the card will be charged. Our card on file guide sets out what that agreement should include.
What if the customer doesn't want to give card details by phone?
Offer a link. Many people are, sensibly, wary of reading card numbers to someone who called them. Sending a payment link by text or email lets them pay on a page that shows your business name and the amount, in their own time, and you can stay on the line until it goes through if they prefer.