Yes. A business can accept a credit card payment over the phone by taking the customer’s card details and entering them into a payment processor’s virtual terminal or another approved phone-payment system. The transaction is usually keyed in rather than read from a physical card, so use a provider that supports phone orders and follow its security rules.
How phone card payments work
A phone payment is generally a card-not-present transaction: the customer and card are not physically present at the point of sale, and the merchant manually enters the card number, expiration date, security code where permitted, billing details, and amount. The payment system sends the transaction through the processor and card network to the card issuer for an authorization response.
An approval means the issuer authorized the transaction at that time; it is not a guarantee that the payment can never be reversed. The merchant may still need to capture or settle the transaction, and later disputes or chargebacks are possible. The exact flow depends on the payment provider and how its system is configured.
Common ways to take a phone payment include:
- Virtual terminal: A secure web page provided by a payment processor. An authorized staff member enters the transaction details in a browser.
- Point-of-sale system with keyed entry: Some systems allow staff to enter card details instead of tapping, inserting, or swiping a card.
- Payment link: Rather than taking card details aloud, the business sends the customer a link to a hosted checkout page. The customer enters the information directly.
Not every provider or account supports every method. Confirm that phone or keyed transactions are enabled and ask what information the system requires before accepting a customer’s details.
Steps to take a payment
- Use the business’s approved payment system and sign in through its official, secure access method.
- Confirm the order, total, currency, and any applicable delivery or billing details with the customer.
- Enter the card information directly into the payment system. Do not write it down or put it in email, text messages, chat, or ordinary notes.
- Submit the transaction and wait for the system’s response. If it is declined, do not describe the reason as certain unless the provider supplies a clear explanation.
- Tell the customer whether the payment was approved and provide a receipt using a secure method that does not expose full card details.
- Follow the provider’s process for settlement, refunds, and recordkeeping. Keep only information needed for legitimate business purposes.
For example, a repair shop taking a deposit can enter the agreed deposit amount in its virtual terminal while the customer reads the card details. The shop should confirm the amount before submitting and send a receipt afterward. It should not keep the card number in a paper file for a future charge.
Security and cardholder data
Card information is sensitive. Limit phone payments to trained staff and systems intended for payment processing. Avoid speakerphone in a shared area, and do not let other callers or nearby people hear the card details. If calls are recorded, check whether the recording process can prevent sensitive card data from being captured, and follow the processor’s and applicable payment-security requirements.
In particular, do not store the card security code (often called CVV, CVC, or CID) after authorization. Do not send card data through ordinary email or text, and do not store full card details in an unprotected spreadsheet, customer-management note, or call log. If a customer volunteers the information through an insecure channel, avoid copying it into another insecure record and contact the payment provider for guidance on handling it.
Use unique staff accounts where available, restrict access to people who need it, and secure devices with updates and strong authentication. If card information is exposed or entered into the wrong place, follow the provider’s incident-reporting instructions promptly. Security obligations can depend on the systems and methods used; ask the processor what standards and procedures apply to the business.
Fees, authorization, and disputes
Phone transactions may be categorized differently from payments where a card is physically presented. The processor’s agreement determines the applicable processing charges and transaction rules, so do not assume a keyed payment costs the same as an in-person one. Ask the provider for its current terms, including fees, refund procedures, settlement timing, and any restrictions on the type of transaction.
Because the card is not physically presented, the merchant may have less evidence that the cardholder authorized the purchase than in a properly authenticated in-person transaction. An authorization response does not eliminate fraud risk or prevent a cardholder from disputing a charge. Keep accurate order records, provide clear descriptions and terms, and retain appropriate evidence of the customer’s consent without retaining prohibited card data.
If a transaction is declined, do not repeatedly submit it without the customer’s permission. Ask the customer to check with their issuer or use a different payment method. Never ask them to disclose their online banking password or one-time authentication code to complete a card payment.
Phone payment or payment link?
A payment link can reduce the amount of sensitive information staff hear and handle because the customer enters the card details on a hosted checkout page. It can also be convenient when the customer is not ready to provide details during a call. A virtual terminal may suit a business that needs to take an order and payment in one conversation, but it requires careful handling and controlled staff access.
Neither method is automatically appropriate for every business. Check that the provider supports the intended use, that the checkout or terminal is genuine, and that the process fits the business’s privacy and security practices. Do not take card data over the phone and then enter it into an unrelated website or consumer payment app.
Common problems to avoid
- Using an unapproved system: A general-purpose form or notes app is not a substitute for a payment processor’s secure terminal.
- Mishearing a digit: Confirm the amount and relevant details carefully, but do not repeat full card data where others can hear it.
- Charging without clear consent: State the total and obtain the customer’s agreement before submitting the charge.
- Keeping data for later: Use a provider’s supported card-on-file or recurring-payment feature only where authorized and permitted; never keep the security code.
- Treating approval as final: Authorization is not a promise that funds are irrevocable or that no dispute can follow.
Frequently Asked Questions
Can I take a credit card payment over the phone without a card reader?
Yes. A virtual terminal or a payment system with keyed entry can process a card-not-present transaction without a physical reader. Your provider must support the feature.
Is it safe to give my credit card number over the phone?
It depends on who is taking the payment and how the details are handled. Confirm you are speaking with the intended business, avoid sharing details where others can hear, and do not provide card information in response to an unexpected or suspicious call.
Can a business record a call that includes card details?
Recording sensitive payment details can create security and compliance risks. Businesses should use a process that prevents card data from being captured in recordings and follow their payment provider’s instructions.
Can a business keep my card number after a phone payment?
It should not retain card details casually or in unprotected records. Any permitted card-on-file arrangement should use the processor’s supported process and appropriate customer authorization; the security code must not be stored after authorization.
Does an approved phone payment mean the charge cannot be disputed?
No. Authorization confirms the issuer approved the transaction at that point, but a customer may later dispute a charge and the payment may be reversed under the applicable process.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this section
- Avalanche Game Schedule: Dates, Times and Where to Check
- Avalanche Hockey Schedule: Games, Dates and TV
- Avalanche Debt Payoff Tracker Calculator
- Avalanche Debt Repayment Calculator and Payoff Plan
- Avalanche Debt Payoff Calculator and Spreadsheet
- Avalanche Debt Payoff Calculator: Free Estimate