The three ways to take a card payment by phone
You can accept credit card payments over the phone using a card-present terminal (you read the card number aloud while the customer holds it), a payment processor or gateway (you enter the card details into software), or a phone-based payment link (you text or email a secure link the customer clicks to enter their own card). Which one you use depends on what equipment you have, how many payments you take, and whether you want the customer to enter their card themselves or you to handle it.
The most important thing to know upfront: never write down a credit card number or store it yourself. Every method described here keeps the card data out of your hands and off your systems, which protects both you and the customer from fraud and data theft.
Key Takeaways
- Payment links sent by text or email let the customer enter their own card details and are the safest option if you do not have a terminal or software account.
- If you take card payments regularly, a payment processor account (Square, Stripe, PayPal) costs less per transaction than one-off payment links and gives you records and refund tools.
- Never ask the customer to read their card number aloud unless you have a secure terminal that encrypts it immediately — typing it into email or a spreadsheet is illegal and exposes you to fraud liability.
- The customer's card data must be encrypted the moment it enters your system; if you cannot may provide that, use a payment link instead.
- Keep receipts and transaction records for at least one year in case of chargebacks or disputes.
Payment links: the fastest way to start
A payment link is a unique URL you send to the customer by text, email, or messaging app. The customer clicks it, enters their card details on a secure page you do not control, and the payment processes. You get a confirmation email and the money lands in your account within one to three business days.
Payment links work through services like Square Cash, PayPal, Stripe, or Wise. You do not need a business account or terminal — most let you create a link from your phone in seconds. The customer sees your business name and the amount, enters their card, and the transaction is done. You never see the card number.
The trade-off is cost: payment links usually charge 2.9% + $0.30 per transaction (or similar), which adds up if you take many payments. They are best for one-off or occasional payments — an invoice for a freelance job, a deposit for a service, a donation. If you are taking card payments multiple times a week, a processor account will cost less.
Processor accounts: lower cost for regular payments
If you take card payments regularly, open an account with a payment processor like Square, Stripe, PayPal, or Toast. These services give you software or an app where you enter the customer's card details (or they enter it themselves), and the processor handles the encryption and fraud checks. Rates are typically 2.6% to 2.9% + $0.10 to $0.30 per transaction, which is cheaper than payment links if you process many payments.
You have two ways to take the payment: the customer can enter their card themselves (called customer-initiated), or you can enter it for them. If you enter it, the processor's software encrypts the card data before it reaches your computer — you type it in, but you never see the full number stored anywhere. The processor keeps the encrypted data, not you.
Processor accounts also give you a dashboard where you can see all your transactions, issue refunds, download receipts for taxes, and dispute chargebacks. Most offer phone support if a payment fails or a customer disputes it. Setup takes 10 to 20 minutes and usually requires a business bank account.
Card-present terminals: reading the card aloud
A card-present terminal is a physical device (or an app on your phone that acts like one) that reads the card's magnetic stripe or chip. The customer hands you the card, you swipe or insert it, and the terminal encrypts the data and sends it to the processor. You never see the full card number — the terminal shows only the last four digits and the cardholder's name.
If you do not have a terminal but the customer is on the phone and wants to read their card number aloud, you can use a terminal app like Square Reader or Stripe Terminal on your phone. The customer reads the number, expiration date, and CVV, and you type it into the app. The app encrypts it immediately. This is legal and safe because the encryption happens before the data touches your computer or email.
Do not ask a customer to read their card number aloud unless you have a terminal or terminal app ready to receive it. Typing it into a text message, email, spreadsheet, or notepad is illegal under payment card industry rules and exposes you to fraud liability and fines. If you do not have a terminal, use a payment link instead.
What happens after the payment goes through
Once the payment is authorized, the money is not in your account yet. The processor holds it for one to three business days while they verify the transaction and check for fraud. During this time, the customer can dispute the charge with their bank, and the processor can reverse it if something looks wrong.
After the hold period, the money deposits into your business bank account. You will see it as a single deposit that includes all your transactions from that day or week, depending on your processor's schedule. Keep the receipt or transaction record for your records — you will need it if the customer disputes the charge later or if you need to issue a refund.
If the customer calls back and says the charge was wrong, you can issue a refund through your processor's dashboard. The refund goes back to their card within one to five business days. If the customer disputes the charge with their bank instead of asking you for a refund, the processor will contact you for proof that the transaction was legitimate — this is called a chargeback. Keep receipts and notes about what the payment was for.
Fees, timing, and what to charge the customer
Payment processing fees vary by method and processor. Payment links and processor accounts typically charge 2.6% to 2.9% of the transaction plus a flat fee of $0.10 to $0.30. Some processors charge a monthly minimum or a small monthly fee even if you take no payments. Check the pricing page of the processor you choose before you sign up.
You can absorb the fee (charge the customer the same price whether they pay by card or cash) or pass it on to the customer (add the fee to their bill). If you pass it on, be clear about it before they pay — tell them the fee amount and the total they will be charged. Some processors let you set a fee in their app so it is added automatically.
Timing depends on the method. Payment links and processor apps authorize the card instantly, but the money does not land in your account for one to three business days. If you need the money faster, some processors offer next-day deposits for an extra fee, or you can use a service like Stripe Connect that deposits money the same day (though fees are higher). For most small businesses, the standard one- to three-day timeline is fine.
Fraud protection and what to do if something goes wrong
The processor handles most fraud detection automatically. They check the card number, expiration date, CVV, and the customer's billing address against the card issuer's records. If something does not match, the payment is declined and you are notified. You do not have to do anything — the processor blocks it.
If a payment goes through and the customer later says they did not authorize it, the processor will ask you for proof. Keep a record of what the payment was for, when it was taken, and any communication with the customer (email, text, invoice). If you have that, the processor will usually side with you and the customer's bank will reverse the dispute. If you do not have proof, the processor will refund the customer and you lose the money.
If a customer disputes a charge because they say the service was bad or the product did not arrive, that is a different kind of dispute called a chargeback. The processor will ask you for proof that you delivered what you promised. An invoice, receipt, email confirmation, or tracking number all count. If you can show proof, you keep the money. If you cannot, you refund the customer and may be charged a chargeback fee (usually $15 to $100).
Frequently Asked Questions
Can I take a credit card payment over the phone without a terminal or app?
Yes, using a payment link. Send the customer a text or email with a secure link, they click it and enter their card, and you never handle the card number. This is the safest option if you do not have equipment or a processor account set up yet.
What if the customer's card is declined?
The processor tells you immediately and gives a reason — insufficient funds, expired card, address mismatch, or the bank blocked it as fraud. Ask the customer if they have a different card or if they want to call their bank to find out why it was declined. You can try the payment again, but do not keep trying the same card more than twice or the bank may block future attempts.
How long do I have to keep payment records?
Keep receipts and transaction records for at least one year. If a customer disputes a charge, the processor may ask for proof months later. Your processor's dashboard usually keeps records for at least two years, so you can download them if you need them.
Can I charge a customer extra for paying by credit card?
Yes, you can pass the processing fee to the customer, but you must tell them the fee amount before they pay. Some processors let you set a fee in their app so it is added automatically. Do not charge a fee for debit cards in most states — that is illegal.
What if I accidentally typed in the wrong amount?
If you notice it right away, cancel the transaction through your processor's app and take the payment again with the correct amount. If the customer already paid and you realize the mistake later, issue a refund for the difference through your processor's dashboard. The refund goes back to their card within one to five business days.