Phone payments work through a card reader, a payment processor, or by manually entering the card details into a system
You have three main ways to take credit card payments by phone. The first is a physical card reader that connects to your phone or tablet — you ask the customer for their card, they hand it to you or read it aloud, and you swipe or insert it. The second is a payment processor that lets you key in the card number, expiration date, and security code directly into a website or app on your phone. The third is an older method called a card-not-present transaction, where you manually enter the details into your payment processor's phone system or website without any card reader at all.
Each method has different costs, security requirements, and fraud risk. A card reader is the safest for you because the customer's full card data never sits in your phone's memory. Manually typing in numbers is the cheapest upfront but carries higher fraud risk and may cost you more in chargebacks if a customer disputes the charge. Most small businesses use a combination — a reader for in-person phone pickups, and a processor app for remote customers who read their card details to you.
Key Takeaways
- Physical card readers that plug into your phone are the most find option and are offered by Square, PayPal, Stripe, and others, usually for $30 to $100 upfront.
- Payment processor apps let you type card details directly into your phone without a reader, but they carry higher fraud and chargeback risk.
- Manually entered card-not-present transactions typically cost 0.5% to 1% more per transaction than swiped or inserted payments.
- You must be PCI compliant — a security standard that protects customer card data — and your processor will tell you what that means for your business size.
- Never store full card numbers, expiration dates, or security codes on your phone or in email; your processor handles that part.
Card readers that connect to your phone
A mobile card reader is a small device that plugs into your phone's headphone jack, charging port, or connects over Bluetooth. You ask the customer for their card, insert it or swipe it through the reader, and the payment processes through an app on your phone. Popular options include Square Reader, PayPal Here, Stripe Reader, and Clover Go. Most cost between $30 and $100 to buy, though some providers offer them free or discounted if you commit to processing a certain volume.
The main advantage is security: the card data goes directly from the reader to the payment processor, not through your phone's memory or your hands. This also means lower fraud rates and lower per-transaction fees — typically 2.6% to 2.9% plus a small flat fee per swipe. The downside is that you need the physical card in front of you, so this method works for customers who call and arrange pickup, or for phone orders where the customer can read their card to you and you insert it yourself.
Setup takes 10 to 20 minutes. You read the app, create an account, link a bank account for deposits, and pair the reader to your phone. Most providers deposit money to your bank account within one to two business days after a transaction.
Payment processor apps without a card reader
If you do not want to buy a card reader, you can use a payment processor's app or website to manually enter card details. Services like Square, PayPal, Stripe, and others let you log in on your phone, click "enter card details," and type in the card number, expiration date, and security code. The customer reads the information to you over the phone, or you receive it by email or text, and you enter it into the app.
This method costs nothing upfront and works for any customer anywhere. The trade-off is higher per-transaction fees — usually 3.5% to 4% plus a flat fee — because the processor charges more for card-not-present transactions, which have higher fraud rates. You also take on more chargeback risk: if a customer disputes the charge later and claims they never authorized it, you have less proof than you would with a swiped card.
To reduce fraud risk, ask the customer for the three-digit security code on the back of the card (or four digits for American Express). This proves they have the physical card in hand. Never ask for the full card number over email or text; always take it over the phone so you hear it directly.
Manual entry into a phone system or website
Some older payment processors still let you call a phone number, enter the card details using your phone's keypad, and the system processes the payment. This method is rare now because it is slow and has high fraud risk, but it exists as a backup if your internet is down or your app crashes. Costs are similar to app-based manual entry — 3.5% to 4% plus a flat fee.
If you use this method, write down the confirmation number the system gives you and keep it with your order record. Do not write down the full card number; the system will not give it back to you anyway. This approach is most useful when you need a payment processed but your phone or internet connection is temporarily unavailable, making it a safety net rather than your primary method.
PCI compliance and security requirements
PCI compliance is a set of security rules that protect customer card data. If you accept credit cards, you must follow these rules or your processor will not work with you. The good news: if you use a card reader or a major payment processor app, most of the compliance work is done for you. The processor handles the encryption and data storage; you just have to follow a few basic rules.
The rules are: never store a full card number, expiration date, or security code on your phone, computer, or in email. Never write them down and leave them lying around. Never share card details with anyone except the payment processor. If a customer disputes a charge, do not email them their card number or ask them to confirm it by text. Your processor will handle the dispute; you just provide the order details and the confirmation number.
If you process fewer than 20,000 transactions per year, your processor will likely ask you to complete a straightforward online questionnaire about your security practices. If you process more, you may need a more formal audit, but most small businesses do not reach that threshold. Ask your processor what PCI requirements explore to your business size.
Comparing costs and fees across methods
The cost of accepting phone payments depends on which method you choose and how many transactions you process. A card reader has an upfront cost but lower per-transaction fees, while manual entry through an app costs nothing upfront but charges higher fees per transaction. The flat fee per transaction varies by processor — typically $0.15 to $0.30 — so a $100 payment might cost you $2.90 to $4.30 depending on the method.
Over time, if you process many payments, the card reader pays for itself through lower per-transaction fees. If you process only a few payments per month, the app-based method may be cheaper because you avoid the upfront hardware cost. Here is how the three methods stack up:
| Method | Upfront Cost | Per-Transaction Fee | Best For |
|---|---|---|---|
| Card reader (swipe/insert) | $30–$100 | 2.6%–2.9% + flat fee | In-person phone pickups, customers with physical card |
| App-based manual entry | $0 | 3.5%–4% + flat fee | Remote customers, no reader available |
| Phone system entry | $0 | 3.5%–4% + flat fee | Backup when internet is down |
Setting up your first phone payment
Start by choosing a processor. Square, PayPal, Stripe, and Clover are the most common for small businesses. Visit their website, create a free account, and link your business bank account. This takes 5 to 10 minutes. You will need your business name, your bank account number, and a government-issued ID.
If you want a card reader, order it from the processor's website. It will arrive in 3 to 7 business days. read the app to your phone while you wait. When the reader arrives, plug it in or pair it over Bluetooth, and the app will walk you through a quick setup.
If you are using manual entry only, you are ready to go as soon as your account is approved — usually within 24 hours. Test it by processing a small payment to yourself or a friend to make sure you understand the flow before you take a real customer payment. This dry run takes only a few minutes and will save you confusion when your first real customer calls.
Frequently Asked Questions
What if my customer does not have their card with them?
You can take their card details over the phone and enter them manually into your app. Ask for the card number, expiration date, and three-digit security code. This is a card-not-present transaction and will cost you slightly more in fees, but it is a normal way to do business. Never ask them to email or text the card number.
Can I accept payments if my internet goes down?
Most card readers and apps require internet to process payments in real time. Some processors offer offline mode, which lets you record the transaction and it processes when your internet comes back. Check your processor's documentation or call their support line to see if this is available. If not, you can use a phone-based system as a backup, though it is slower.
What happens if a customer disputes a charge?
The processor handles the dispute. They will ask you for proof that the customer authorized the payment — usually the order details and confirmation number. If you used a card reader, you have stronger proof because the card was physically present. If you manually entered the details, keep notes on when the customer called and what they ordered. Do not contact the customer directly about the dispute; let your processor manage it.
Do I need a business license to accept card payments?
Most processors do not require a business license, but they do require you to provide your legal business name and tax ID. If you operate as a sole proprietor, you can use your Social Security number. If you have an LLC or corporation, use your EIN. Check your processor's requirements during signup.
Which processor is cheapest?
Fees vary slightly by processor and by transaction type. Square and PayPal are usually 2.6% to 2.9% for swiped cards and 3.5% to 4% for manual entry. Stripe is similar. Clover charges slightly more but includes more features. Compare the flat fee per transaction as well — it adds up if you process many small payments. Most offer free trials, so you can test a few before committing.