Short answer
There are two ways. To take cards on your smartphone, use a payment provider's app with Tap to Pay on iPhone (iPhone XS or later) or an NFC-enabled Android phone, or pair a Bluetooth card reader. To take a card over a phone call, key it into a virtual terminal or send a payment link, never write the number down, and expect higher card-not-present costs.
How do you accept credit card payments on a phone? It depends which phone you mean. You can turn your smartphone into a card reader with tap to pay or a small Bluetooth reader, or you can take a customer's card details during a phone call and enter them into a virtual terminal. Both work. They just don't cost the same, and they don't suit the same businesses.
This guide covers both meanings: what you need for Tap to Pay on iPhone and on Android, when a Bluetooth reader is the better tool, how to take a card over a phone call safely, and what each method costs in card-present and card-not-present terms.
What are the ways to take card payments with a phone?
There are four practical options. Three use your smartphone as the payment device, and one uses a phone call.
| Method | What you need | Card present? | Best for |
|---|---|---|---|
| Tap to Pay on iPhone | iPhone XS or later, the latest iOS, and a supported payment app | Yes | Contactless cards and wallets anywhere you are |
| Tap to pay on Android | An NFC-enabled Android phone and a provider's tap-to-pay app | Yes | The same, for Android users |
| Bluetooth card reader | A small reader paired with your phone or tablet | Yes | Chip cards, plus taps, in the field |
| Virtual terminal or payment link | A web browser and a virtual terminal account | No | Orders, deposits, and bills taken over a phone call |
How do you take payments with Tap to Pay on iPhone?
You enable Tap to Pay on iPhone inside a supported payment app, enter the amount, and hold the phone out for the customer to tap. Apple's business page says it requires an iPhone XS or later and works best with the latest version of iOS. Apple announced the feature for US merchants in February 2022.
According to Apple's developer site, Tap to Pay on iPhone accepts contactless credit and debit cards, Apple Pay, Apple Watch, and phones with other digital wallets, with no extra terminal or hardware. You don't get it from Apple directly. It comes through a payment app, and the app's payment service provider processes the payments and supplies the certified setup that runs on your iPhone.
Here's how to get started:
- Check your phone. You need an iPhone XS or later, updated to the latest iOS.
- Choose a provider whose app supports Tap to Pay on iPhone. Apple's developer site keeps a list of supported providers by country.
- Turn on Tap to Pay in the app's settings and follow the setup prompts.
- To charge someone, enter the amount and present the phone. The customer taps a card, phone, or watch against the iPhone.
- Send a receipt by text or email from the app.
On security, Apple said at launch that Tap to Pay transactions are encrypted and processed using the iPhone's Secure Element. The bigger practical limit is reach: it only takes contactless payments. Apple's developer site notes that over two thirds of US credit and debit cards are issued contactless-enabled, which still leaves plenty of cards that can only be dipped or swiped.
Can you accept tap payments on an Android phone?
Yes, through a payment provider's app on an Android phone with NFC. Visa's Tap to Phone page describes merchants accepting contactless payments on the near-field enabled Android and Apple smartphones they already own, simply by downloading an app.
The difference from iPhone is who sets the rules. Apple publishes one set of requirements. On Android, each payment provider decides which phones and software versions its app supports, so the list varies. Your phone needs working NFC hardware; Google's Android documentation on NFC describes how Android devices use it to read NFC tags and to act as a card for a point-of-sale reader. Before you buy a phone for this, ask your provider:
- Which phone models and which minimum Android version are supported?
- Does the app require Google Play services or a recent security update?
- Can customers enter a PIN on the phone when their card asks for one?
- Which card brands and digital wallets can you accept?
- Is the solution on the PCI Security Standards Council's list of validated mobile payment solutions?
That last question matters more than it sounds. PCI SSC's Mobile Payments on COTS standard covers solutions that let merchants accept cardholder PINs or contactless payments on a smartphone or other off-the-shelf device, and the Council's solution listings are meant to help businesses choose one.
When is a Bluetooth card reader the better choice?
Use a Bluetooth reader when you need chip cards as well as taps, or when you want a dedicated device that isn't your personal phone screen. A small reader pairs with your phone or tablet and handles the card while the app handles everything else. Our POS cost guide lists current reader prices alongside terminals and registers.
A reader makes sense when:
- Some customers have chip cards that don't tap.
- You work in places where handing over your own phone feels awkward.
- You want a backup that still works if tap to pay has a bad day.
- You process enough in person that a fast, familiar checkout matters.
Chip transactions also carry EMV's one-time security code, the protection that stops copied card data from working at the point of sale. Our explainer on what EMV is covers why that matters for counterfeit fraud.
What does it cost to take cards on a phone?
Taps and chip reads on your smartphone count as card-present transactions. Card details typed in during a phone call are card-not-present, and on Visa's published schedule those fall into higher interchange categories. Interchange is the part of each fee that goes to the bank that issued the card, and it's set by the card networks.
Here's a concrete example from the Visa USA interchange schedule we checked in October 2026, for a debit card from a bank that's exempt from the federal debit cap:
| How the card was accepted | Visa interchange category | Rate | Cost on a $100 sale |
|---|---|---|---|
| Tapped or dipped at a retail sale | CPS/Retail, Debit | 0.80% + $0.15 | $0.95 |
| Card present but number keyed in | CPS/Retail Key Entry, Debit | 1.65% + $0.15 | $1.80 |
| Card not present (phone or online) | CPS/Card Not Present, Debit | 1.65% + $0.15 | $1.80 |
The same schedule lists 0.05% plus $0.21 for regulated debit cards from large banks, whether or not the card is present. Credit cards have their own categories. Rates change, so treat this as an example of the gap, not a quote. Your processor's markup sits on top of interchange, which is why the pricing model matters; our credit card processing fees guide and our comparison of interchange-plus vs flat-rate pricing explain how to see it.
One practical lesson: if the customer is standing in front of you, tap or dip the card. Don't key it in because the reader is in the truck. On that debit card, keying the number costs almost twice as much as tapping it, and it skips the chip's protection.
The gap adds up. Say a cleaning company keys in $8,000 a month of those exempt Visa debit cards when it could have tapped them on site. The rate difference is 0.85 percentage points, so that's $68 a month, or $816 a year, on one card type alone.
How do you take a credit card payment over a phone call?
Use a virtual terminal: a secure web page where you type the card details while the customer is on the line, or better, send the customer a payment link so they enter the details themselves. Either way, the card number goes straight into the payment system and never onto paper.
Here's the process for a keyed phone payment:
- Log in to your virtual terminal on a secure, up-to-date device that only authorized staff use.
- Enter the amount and a description or invoice number.
- Ask for the card number, the expiration date, the security code, and the billing ZIP code. The ZIP code and security code feed the address verification and card code checks that help screen out stolen cards.
- Submit the payment and wait for the approval before ending the call.
- Email or text the receipt so the customer has a record with your business name on it.
Payment links are often the better choice for anything that isn't urgent. The customer pays on their own device, your staff never hears the card number, and nobody has to read sixteen digits over a bad connection. Clearo's virtual terminal handles phone and email payments, invoices, and payment links, plus recurring billing for regular customers, which we cover in our guide to recurring billing.
How do you keep phone payments secure?
Phone payments are safe when card data goes straight into the system and nowhere else. Use this checklist:
- Never write card numbers on paper, in notes apps, or in your customer records.
- Never keep the security code. The PCI Security Standards Council says PCI DSS strictly prohibits storing card verification codes after authorization, even if encrypted.
- Pause or mask call recordings while customers read out card details. PCI SSC's guidance on telephone payments says sensitive authentication data captured in a recording must be deleted.
- Turn on address verification and security code checks for keyed payments.
- Give each staff member their own virtual terminal login, and remove access the day someone leaves.
- Lock your phone with a passcode and keep its software updated if you use it for tap to pay.
- Be wary of first-time phone orders that are large, rushed, or shipped somewhere other than the billing address.
Common mistakes when taking payments by phone
Most phone payment problems come from habits, not technology. These are the ones to train out of your team:
- Keying in a card that's right in front of you. Tap or dip it instead.
- Writing a card number on a job ticket "just for a minute." That minute is how card data ends up in a filing cabinet.
- Asking customers to email or text their card details. Send a payment link instead.
- Sharing one virtual terminal login across the whole team, which makes it impossible to see who ran what.
- Taking payments on a phone with no passcode.
- Skipping the receipt. A receipt with your business name on it helps customers recognize the charge when their statement arrives.
Which phone payment method should you use?
Match the method to where the customer is. If they're in front of you with a tap-ready card or phone, use tap to pay. If their card only works with a chip, use a Bluetooth reader. If they're on the other end of a call, send a payment link, and fall back to the virtual terminal when they need to pay right now.
Two examples. A mobile dog groomer in Phoenix can run almost everything through Tap to Pay on an iPhone, with a Bluetooth reader in the van for the occasional chip-only card. A plumbing company in Charlotte that books jobs by phone can take deposits with payment links, collect the balance with tap to pay on site, and keep the virtual terminal for customers who want to pay during the call. Our home services page covers that kind of setup.
If you're choosing a dedicated counter device instead, our guide to credit card machines for small business compares the options.
Set it up with the right pricing
Phone payments are easy to start and easy to overpay for, because keyed transactions cost more and that difference is easy to miss on a statement. Clearo's mobile payments include tap to pay and mobile card readers, and our virtual terminal covers phone, email, and invoice payments, all on interchange-plus pricing with no long-term contract. If you already take cards, start with a free statement review to see what your keyed payments are really costing you, or contact us to set up a phone payment option that fits how you work.
About this guide
Written by the Clearo Payments team. Clearo provides interchange-plus payment processing to merchants in the US and Canada, with no long-term contracts and no cancellation fees. Card network rules and laws change, so check the sources below before you act on anything here. Our editorial standards explain how we source and update guides. Questions about your own setup? Ask our team.
Sources
Official and primary sources we checked while writing this guide.
- Tap to Pay on iPhone - Apple (apple.com)
- Tap to Pay on iPhone - Apple Developer (developer.apple.com)
- Apple unveils contactless payments via Tap to Pay on iPhone - Apple (apple.com)
- Visa Tap To Phone | Visa (visa.com)
- Near field communication (NFC) overview - Android Developers (developer.android.com)
- Mobile Payments on COTS (MPoC) - PCI Security Standards Council (pcisecuritystandards.org)
- Visa USA Interchange Reimbursement Fees (usa.visa.com)
- Are merchants allowed to request card-verification codes/values from cardholders? (PCI SSC FAQ) (pcisecuritystandards.org)
- Information Supplement: Protecting Telephone-Based Payment Card Data (PCI SSC, November 2018) (listings.pcisecuritystandards.org)
- Product & Solutions Listings Overview - PCI Security Standards Council (pcisecuritystandards.org)