Phone Order Fraud: How to Vet Keyed Card Transactions
Phone order fraud lands on the merchant when keyed sales go bad. Use this staff script, red flags and AVS/CVV settings to vet orders before you charge.

Photo: Pixabay
On this page 6 sections
Key takeaways
- An approval code shows the account is open and has funds. It does not show that the caller owns the card, and a keyed phone order gives you little fraud protection.
- A full AVS and CVV match lowers risk but rarely wins a "cardholder didn't authorize this" chargeback. A signed authorization form doesn't either.
- If your cost of goods is more than half the sale price, one fraudulent phone order costs you more than one legitimate order earns.
- Turn on CVV-required, AVS decline rules and staff permissions in your virtual terminal before the next big phone order comes in.
Phone order fraud costs merchants so much because a keyed card sale gives you little protection. Suppose the real cardholder later says they never placed the order. The chargeback usually lands on you, even if the authorization was approved and the address matched. That means you have to stop the fraud before anyone types in the card number. Staff need to recognize the red flags, follow a short verification script, and know they are allowed to refuse a sale.
The steps below are for the people who answer the phone: the counter clerk at a furniture store, the service writer at a repair shop, the sales associate at a jewelry case, the inside sales rep at a wholesale distributor.
Why Phone Order Fraud Lands on the Merchant
When a customer dips a chip card at your terminal, the card itself takes part in the transaction. The chip generates data the issuing bank uses to confirm the card is genuine. On a phone order you have none of that. What you get is a card number, an expiration date and the security code printed on the card. Thieves buy all of that together after a data breach or collect it with a phishing text.
The card networks call these sales card-not-present. Phone and mail orders are often grouped together as MOTO (mail order/telephone order). Many owners get one point wrong here: an approval code only means the account is open and has available funds or credit. It says nothing about whether the person on the phone owns the card.
E-commerce sellers can sometimes shift fraud liability to the card issuer with 3-D Secure. That works only because the cardholder confirms the purchase with their bank in a browser or app. A sale your employee keys into a virtual terminal for phone orders has no such step. So when the real cardholder sees a large charge they don't recognize and files a fraud dispute, the issuer has little reason to side with you.
That is the core of moto fraud risk. Each card network sets its own evidence rules for disputes and revises them from time to time, so ask your processor what, if anything, can win a card-absent fraud dispute in your setup. If a dispute does go against you, see our guide on when to escalate a dispute to pre-arbitration and arbitration.
What One Bad Phone Order Costs
Before you set a threshold for extra checks, price out a single fraud loss with your own numbers. Pull them from your last processing statement and your processor's fee schedule rather than guessing.
| Cost of one fraudulent phone order | Where to find your number |
|---|---|
| Merchandise or parts you shipped or released | Your cost of goods, not the retail price |
| Processing fee on the original sale | Your statement; ask whether your processor returns it when a sale is charged back |
| Chargeback fee | Your processor's fee schedule |
| Shipping, delivery or labor you paid | Carrier invoice, delivery log or technician time |
Add those rows, then compare the total with what the same order would have earned if it were legitimate: the sale price minus the same merchandise cost and processing fee. The comparison rarely favors the merchant. Whenever your cost of goods is more than half the sale price, one fraudulent order costs you more than one good order earns, and that holds before you even add the chargeback fee. A jeweler or furniture store working on a modest markup can give back the profit from several good sales to one bad one. The callback in the script below takes a few minutes.
Red Flags That Should Stop a Phone Order
No single sign proves fraud. When several show up together, hold the order until someone senior reviews it.
- Price indifference. The caller doesn't ask about price, picks the most expensive option, or agrees to rush shipping without asking what it costs.
- Several cards. The first card declines and the caller reads off a second and a third, sometimes in different names.
- Mismatched addresses, especially when the shipping address is a freight forwarder, a reshipping service, a hotel, or a vacant property.
- Third-party pickup. "My driver will come get it," "a courier is on the way," or "my assistant will pick it up."
- Overpayment requests. The caller wants you to charge extra and send the difference to their "shipper" by wire, gift card or app.
- Hesitation on basic details. The caller pauses on their own billing ZIP code, or sounds like they're reading every answer off a screen.
- Urgency and pressure. It has to ship today, it's a gift for an event tonight, or the caller gets irritated when you ask questions.
- No history. A brand-new customer who has never visited your location places a first order much larger than your usual phone sale.
Relay services for callers who are deaf or hard of hearing are legitimate, and many honest customers use them. Fraudsters sometimes misuse them, but how someone calls is not a red flag. Apply the same checks you use on every other phone order, no more and no less.
What Red Flags Look Like in Your Industry
B2B and wholesale. A new "company" orders a full pallet of high-resale items such as electronics, tools or tires. The email domain was registered recently, or the caller uses a free email address and asks for freight to a forwarder. Look up the company's main number yourself and call it to confirm the buyer works there. For larger repeat accounts, steering payment to bank transfer or a corporate card program often makes more sense. Our guide to accepting B2B virtual card payments covers how those work.
Jewelry and diamonds. Watch for a caller who wants "any ring size," buys loose stones or gold chains that resell easily, or asks for overnight shipping to an address in another state. Jewelry and diamond merchants combine high tickets with easy-to-resell goods, which is why fraudsters target them.
Auto repair. The usual risk is a third party paying over the phone for someone else's repair, or a caller ordering parts or tires and asking to pick them up "before close." A parent paying for a kid's brakes is often legitimate. Get the cardholder's name and number and confirm by callback before releasing the car. Auto repair shops that release vehicles after hours should be especially strict, because once the car is gone, so is your chance to collect another way.
Furniture stores. The pattern is a large phone order delivered by your own truck to an address that doesn't match the card. A furniture store can check the delivery address against public listings for vacant or for-sale homes, since fraud rings have used empty houses as drop points. Custom orders taken with a phone deposit carry their own risks, which we cover in taking card deposits on custom orders.
A Verification Script Your Staff Can Use
Post this next to every phone that takes payments. Staff can change the wording, but they shouldn't skip steps.
- Get the order details first and the card last. "Let me write up the order, and then I'll take your payment information." A caller who pushes to skip ahead to payment is telling you something.
- Ask for the cardholder's full name and billing address. "What's the name exactly as it appears on the card, and the billing address the card company has on file?" Write it down before you enter anything.
- Take a callback number and email. "What's the best number to reach you if we have a question about the order?"
- Explain your policy, calmly. "For orders over $[your threshold], we confirm with a quick call back before we process. It protects you as much as us." Legitimate customers rarely object.
- Verify through a number you found yourself. If the buyer is a business, call the main line listed on its website or in a directory. An existing customer gets a call at the number already in your records. With a new consumer, call back the number they gave you and check it against any history you have.
- Run the authorization with AVS and CVV, then read the response codes before you release anything (see the next section).
- Send a written order confirmation to the email on file, listing items, amount, shipping address and your return policy.
Signed card authorization forms are useful for documenting terms on a legitimate order. They won't protect you against a stolen card, because whoever stole the card can also sign the form. Keep using the form, but don't treat it as a fraud check.
One more rule for staff: never write the security code on an order ticket or in a notes field. Card industry security standards generally prohibit keeping the security code after authorization, so confirm the details with your processor's PCI guidance.
Using AVS and CVV on Card-Not-Present Phone Orders
The Address Verification Service (AVS) compares the billing address the customer gives you with the address the issuer has on file. It generally checks the numbers in the street address and the ZIP code. The card verification value (CVV) check confirms the caller has the security code from the card. Your gateway returns a result for each, such as full match, partial match, no match, or unavailable.
Use those results to decide, but know their limits. Thieves who buy a full stolen card record often get the billing address with it, so a perfect match lowers risk without removing it. Mismatches tell you more. When the CVV fails on a phone order, the caller doesn't have the right code, and in most cases you shouldn't ship. Treat a ZIP-only match on a large order going to a different shipping address as a case for manager review. For a decision chart by response type, see AVS and CVV mismatch rules for accepting a transaction.
If a phone order fails AVS or CVV and you decide not to proceed, void the authorization. Don't leave the hold sitting on a card that might belong to an innocent cardholder.
Shipping and Pickup Rules for Risky Orders
Set these rules in advance so staff aren't deciding under pressure.
Ship only to the verified billing address above your threshold, unless the order passes manager review. Require signature confirmation on high-value shipments, and don't reroute a package after it ships just because the caller asks.
When the customer is picking up, charge the card at pickup instead of keying it over the phone. This is the most useful rule here. A chip card dipped on a countertop smart terminal becomes a card-present transaction, with far stronger protection than the same card keyed in from a phone call. If you need to hold the item, take a small deposit by phone and run the balance on the chip at pickup. Check photo ID against the name on the card at the same time.
Refuse third-party pickup on phone-paid orders above your threshold. If the cardholder can't come in, ship to the billing address instead.
When your gateway supports it, consider sending a hosted payment link instead of taking the number over the phone. The customer enters the card themselves, so staff never hear or handle the number. If the page supports 3-D Secure authentication, the sale may also qualify for liability protection that a keyed sale never gets.
Virtual Terminal Settings That Cut Keyed Transaction Fraud
Most of these take minutes to set up in the gateway admin panel. Payment gateways such as Authorize.net and NMI offer configurable filters. Names and options vary by gateway, so review them with your processor.
- Make CVV and the AVS fields mandatory so no one can key a sale without them.
- Set automatic decline or hold rules for CVV no-match, and for AVS no-match above a dollar amount you choose.
- Cap the single-transaction amount for keyed sales, so anything larger needs manager approval.
- Add velocity limits on how many attempts one card, or one session, can make within an hour. These catch card testing, where a fraudster runs several numbers to see which ones work.
- Limit user permissions. Give each employee their own login, restrict who can issue refunds, and disable force or offline sales for anyone who doesn't need them.
- Allow refunds only to the original card. Callers who want a refund sent to a different card are often running the overpayment scheme described above.
Start this week: fill in the cost worksheet, pick your phone order dollar threshold, print the script, and open your virtual terminal settings to check each item on that list. If you'd like a second set of eyes on your gateway setup or terminal mix, request a free quote from MannyPay, and a specialist will respond within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.


