Taking card payments over the phone, safely

A regular calls from home and wants to pay for a catering tray before they pick it up tomorrow. Taking phone payments as a small business is common and useful, but it's a card-not-present sale, which means higher cost and more fraud risk than a chip or tap at the counter. The safe version uses a few extra checks, keeps card numbers off paper, and confirms the customer at pickup.

Phone payments are likely to keep growing as customers get used to ordering ahead. A clear routine now saves problems later.

When does a phone payment make sense?

Phone payments fit a few situations well.

Pre-orders for pickup, like catering trays, cakes, or bulk orders.

Deposits on special orders, where the customer can't come in right away.

Delivery orders for regular customers nearby.

Paying off a balance, like the rest of a layaway or a special order.

They fit less well for first-time customers placing large orders they want someone else to pick up. That pattern shows up often in fraud. It doesn't mean every such order is fraud, but it deserves extra care.

Here's a practical rule. If you know the customer, phone payment is a convenience. If you don't, ask them to pay in person at pickup when you can.

What checks should you run on every phone payment?

A phone payment is a card-not-present transaction. You can't see the card or the person. So you rely on information checks.

1. Ask for the card number, expiration date, and security code.
2. Ask for the billing ZIP code, and the street address if your system checks it.
3. Confirm the name on the card and a callback phone number.
4. Look at the verification results your terminal shows before completing the sale.
5. Note what was ordered, the amount, and the pickup or delivery details.

The card security code check confirms the caller knows the code printed on the card. The address check compares billing details with the bank's records. Neither proves the caller is the cardholder, but together they filter out a lot of fraud.

For large first-time orders, call the customer back at a listed number before you confirm the order.

How do you protect the card number?

This is where many stores slip.

Never write the card number on paper, even for a minute. Type it straight into the terminal or payment system.

Never save card numbers in a notebook, spreadsheet, text message, or email.

Don't read the number back out loud if other customers are nearby.

Take phone payments in a quiet spot, not at a busy register where someone might overhear.

Card industry rules forbid storing the security code after authorization. If you want to charge a regular customer again later, ask your provider about secure card-on-file options instead of keeping numbers yourself.

Phone payments can be taken different ways depending on your setup, such as keying into a terminal or using a virtual terminal. Ask the NRS Pay team what your setup supports before you start taking them.

What should happen at pickup?

Pickup is your last chance to catch a problem.

Ask for the name on the order and check an ID if the order is large.

If someone other than the cardholder is picking up, confirm that with the customer ahead of time and note it on the order.

Give the customer a receipt showing the order, amount, and date of payment.

Keep the order slip or record with your other sale records. If a chargeback comes later, you'll want it.

Here's a hypothetical. A caller orders $300 in party supplies and wants a friend to pick them up in an hour. The card passes the security code check but the ZIP doesn't match. That combination is a reason to pause. You might ask the caller to pay in person, or call back at a listed number before releasing the goods.

For readers and terminals that work with the NRS POS, see NRS Pay equipment.