How to Accept Credit Card Payments Over the Phone

On this page 10 sections

1. Card-Not-Present Payments: What Changes on the Phone
2. Your Options for Taking Phone Payments
3. How to Accept Credit Card Payments Over the Phone, Step by Step
4. What Information to Collect From the Caller
5. Using AVS and CVV to Reduce Fraud
6. Why Keyed Transactions Cost More
7. Receipts, Records, and PCI-Safe Handling
8. Scripts and Policies for Your Staff
9. Phone Payment Notes for Practices, Firms, Wholesalers, and Care Agencies
10. Next Steps

Key takeaways

• A virtual terminal is usually the simplest, most secure way to take phone payments because staff type card data straight into the gateway.
• Collect the billing ZIP code, street address, and security code on every call so AVS and CVV checks can flag fraud and help avoid costlier interchange categories.
• Never write card numbers down, store security codes, or let call recordings capture card data. Enter it once, then let the system handle it.
• A short staff script, clear refund rules, and good records give you the evidence to fight card-not-present chargebacks.

If you need to accept credit card payments over the phone, the process looks simple. A customer reads a card number, and you type it in. Doing it well takes more than that. This guide covers which tools to use, what details to collect from the caller, how AVS and CVV checks reduce fraud, why keyed transactions cost more, how to keep card data PCI-safe, and what your staff should say on every call.

Phone payments are common in businesses where the customer isn't standing at a counter. A dental office collects a balance after insurance pays. A CPA firm takes a retainer. A wholesaler's buyer calls in a reorder. A family pays a home care invoice. The steps below work for all of them, with industry notes near the end.

Card-Not-Present Payments: What Changes on the Phone

When a card is read over the phone, there is no chip, no tap, and no physical card in front of you. Processors and card networks treat these as card-not-present payments, and they are often classified as mail order/telephone order (MOTO) transactions.

That classification affects three things:

• Risk. You can't inspect the card or the cardholder, so fraud is easier for criminals.
• Liability. On card-not-present fraud, the merchant generally absorbs the loss when a chargeback is filed. The EMV liability protections that apply to chip transactions don't apply here.
• Cost. Card-not-present transactions usually fall into higher interchange categories than chip or tap payments.

If you're new to the distinction, our guide to card-present vs. card-not-present fees, fraud, and rules explains it in more depth.

Tell your processor. If your merchant account was set up mainly for in-person sales and you start taking a meaningful share of payments by phone, let your provider know. Your account should accurately reflect how you take payments. Here's more on when to tell your payment processor about business changes.

Your Options for Taking Phone Payments

You have several ways to process a card read over the phone. The right one depends on call volume, whether you also sell in person, and whether you bill customers repeatedly.

For most phone-heavy businesses, virtual terminals are the cleanest choice. Card data goes straight into the gateway instead of onto paper or into a spreadsheet, and many gateways let you require AVS and CVV fields before a sale can be submitted. If you want a fuller walkthrough, read what a virtual terminal is and how to take card payments without hardware.

If you already have in-person hardware, manual entry on smart terminals can work for occasional phone orders. Be sure the device prompts for ZIP code and security code on keyed sales.

How to Accept Credit Card Payments Over the Phone, Step by Step

Here is a repeatable process staff can follow on every call:

1. Confirm the order or invoice first. Agree on the amount, what it covers, and any delivery or service dates before asking for the card.
2. Disclose any fees or pricing terms. If you run a surcharge or another cost program, tell the caller before you charge. Rules vary by state and card brand.
3. Collect card and billing details. Use the checklist in the next section.
4. Key the transaction directly into your terminal or gateway. Don't write it down first.
5. Review the AVS and CVV results. Decide whether to proceed, verify further, or decline.
6. Read back the amount and confirm approval. Give the caller the last four digits of the card and the authorization outcome.
7. Send a receipt by email or text. A receipt the customer actually receives can help reduce "I don't recognize this charge" disputes.
8. Record the call details in your order, patient, or client record, without the full card number.

What Information to Collect From the Caller

For every phone payment, gather:

• Cardholder name exactly as it appears on the card
• Card number and expiration date
• Security code (CVV2, CVC2, or CID, the three or four digits on the card)
• Billing street address and ZIP code for address verification
• Phone number and email for the receipt and any follow-up
• Shipping or service address, if different from billing
• What the payment is for, such as an invoice number, patient account, or matter number

Ask whether the caller is the cardholder. If someone is paying on another person's card, such as an adult child paying a parent's care invoice, note it. For ongoing arrangements, get written permission from the cardholder.

Using AVS and CVV to Reduce Fraud

AVS (Address Verification Service) compares the billing address and ZIP code the caller gives you with what the card issuer has on file. The CVV check confirms the security code. Neither proves identity. Both, however, make it harder for someone with a stolen card number alone to succeed.

Note that an AVS mismatch often doesn't decline the transaction on its own. The issuer may still approve it, so your staff need clear rules on what to do with the result. Many gateways let you set filters to automatically reject certain mismatch combinations.

Phone-Order Red Flags

Train staff to slow down when they notice:

• Rush shipping requests to an address that doesn't match billing
• Several cards tried in a row after declines
• Callers who seem to read card numbers from a list or hesitate on their own billing address
• Unusually large first orders from new customers
• Requests to refund an "overpayment" to a different card or by wire

When something feels wrong, a callback to a number you find independently, such as an existing customer record, is one of the simplest checks you can run.

Why Keyed Transactions Cost More

Keyed transactions usually cost more than chip or tap sales for two reasons.

First, card networks set interchange (the largest part of your processing cost) partly by risk. Card-not-present transactions carry more fraud risk, so their interchange categories are typically higher. If you're comparing card costs with bank payments, see whether your business should accept Same Day ACH.

Second, keyed sales that are missing data can downgrade into even more expensive categories. Leaving out the ZIP code or address verification, settling a batch late, or omitting invoice data on business cards can all push a transaction into a costlier tier. Our article on interchange downgrades and how to fix them walks through the common causes.

Ways to manage the cost:

• Always capture AVS data on keyed sales.
• Settle batches daily.
• For B2B cards, check whether your gateway can pass invoice and tax details.
• Review pricing models. Some merchants use credit card surcharging where permitted or other compliant cost programs. Surcharging rules differ by state and card brand, and some professions have their own considerations. Medical practices, for example, should read whether doctors and dentists can charge credit card fees. Confirm current rules with your processor and a qualified advisor.

Receipts, Records, and PCI-Safe Handling

Taking card data by phone puts your office inside the scope of PCI DSS, the card industry's data security standard. The goal is to touch card data as little as possible and never store it where it doesn't belong.

Handling Rules That Keep Card Data Safe

• Never write card numbers on paper, sticky notes, or order pads. Key them directly into the system.
• Never store the security code after the transaction. PCI DSS treats it as sensitive authentication data that must not be retained after authorization.
• Don't accept card numbers by email, text, or chat. Direct those customers to a secure payment request instead.
• Pause or mask call recordings while card details are spoken, or confirm that your phone system does this.
• Tell callers not to leave card numbers in voicemail.
• Limit access to the virtual terminal by user, and give each staff member their own login.
• Use tokenization for card on file instead of saving numbers in your practice management, CRM, or accounting software.

PCI requirements are detailed and get updated over time. Confirm your obligations with your processor and, where needed, a qualified security assessor.

What to Keep for Chargeback Defense

When a phone payment is disputed, you'll want:

• Date, time, and amount of the call and transaction
• AVS and CVV results
• The receipt you sent, and where you sent it
• Signed authorization forms for card-on-file or recurring charges
• Proof of delivery, completed services, or time records
• Notes on any fee disclosures you made

For contested cases, our chargeback rebuttal letter template and evidence guide shows how to organize this into a response.

Scripts and Policies for Your Staff

A short, consistent script keeps calls quick and makes sure nothing gets skipped. Adapt this illustrative example:

"I can take that payment now. The total for invoice 1042 is [amount]. (Disclose any applicable fee here.) May I have the name exactly as it appears on the card? … The card number? … Expiration date? … And the three- or four-digit security code? … What's the billing ZIP code and street address for the card? … Thank you. That's approved on the card ending in [last four]. I'll email your receipt to [email] now. Is there anything else I can help with?"

Policies Worth Writing Down

• Who can take payments. Only trained staff with their own logins.
• Approval thresholds. Orders above a set amount need a manager's review or a callback.
• Refunds go back to the original card only. Never refund to a different card, cash, or wire.
• Card on file requires written authorization. Use a signed form that spells out amounts and timing. Wholesalers can start with our guide to B2B credit card authorization forms.
• Declines. Staff ask for another payment method. They don't retry the same card repeatedly.

Phone Payment Notes for Practices, Firms, Wholesalers, and Care Agencies

• Medical and dental offices. Phone payments often settle a balance after insurance adjudicates. Keep the call focused on the account and amount, and avoid discussing clinical details with anyone not authorized on the account. If patients agree to have balances charged automatically, see card on file for patient balances after insurance pays. MannyPay also works with medical practices.
• Law, accounting, and consulting firms. Retainers and flat fees may need to land in a specific account depending on professional rules. Confirm with your bar or licensing guidance before setting up phone payments for professional services.
• B2B and wholesale. Buyers often call with purchasing or corporate cards on larger tickets. Capture invoice and PO numbers so records match, and ask about passing that data through your gateway.
• Home care and staffing agencies. Payers are frequently family members rather than the client. Get written authorization from the cardholder, and keep visit or hour records ready, since disputes often center on hours billed. See how MannyPay supports home healthcare and medical staffing businesses.

Next Steps

To take phone payments safely, you need the right tool, a consistent process, and good records. Start with a virtual terminal or keyed entry that requires AVS and CVV. Train staff on a simple script, keep card data off paper, and save the evidence you'd need in a dispute.

If you'd like help choosing a setup for phone orders, request a free quote from MannyPay. A MannyPay specialist will respond within one business day to review your payment flow, hardware or gateway needs, and pricing options.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

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.