Tap to Pay on iPhone and Android: Take Cards With No Terminal — and What It Really Costs

Your customer is ready to pay. Their card is already out — or more likely, their phone is. And the card reader? Dead battery, left in the van, still in the shipping box you never opened. Here is the good news: the phone in your pocket can be the reader. With Tap to Pay, you can accept contactless payments directly on an iPhone or Android device, with no extra hardware at all.

This is not a gimmick or a beta feature anymore. It is a mainstream way for mobile and micro merchants — farmers market vendors, house-call tradespeople, pop-up sellers, solo consultants who occasionally get paid in person — to take cards from day one. But "no hardware" does not mean "no cost," and a phone is not always the right terminal. This guide covers how Tap to Pay works on each platform, what you actually pay versus buying a card reader, what you give up, and how to keep the bookkeeping clean.

How Tap to Pay Turns Your Phone Into a Card Reader​

At checkout, you enter the amount in a supported payment app, present your phone to the customer, and they tap their contactless card, phone, or watch against it. The payment completes over NFC, the same technology behind Apple Pay and Google Pay. Receipts go out by text or email from the app.

Tap to Pay on iPhone​

Apple's Tap to Pay on iPhone lets merchants accept Apple Pay, contactless credit and debit cards, and other digital wallets through a partner-enabled iOS app — no additional hardware needed. The requirements are straightforward:

• An iPhone XS or later, ideally running the latest iOS (PIN entry support requires iOS 16.4 or later).
• A supported payment app from a participating platform — Stripe, Square, Shopify Point of Sale, Adyen, and others all offer it. Apple provides the capability; your processor provides the app, the account, and the rates.
• A merchant account with that processor and a linked bank account for payouts.

At checkout, the customer holds their iPhone, Apple Watch, contactless card, or other wallet near your iPhone, and NFC completes the payment. Larger contactless transactions may prompt the customer to enter a PIN on your phone, and accessibility options are built in.

Tap to Pay on Android​

Android phones with NFC can do the same job through supported payment apps — most notably Stripe Terminal's Tap to Pay on Android, plus options from Square, PayPal, and others. You need an NFC-enabled Android phone, the provider's app, and a merchant account. In practice, if your Android phone can pay with Google Pay, it almost certainly has the NFC hardware needed to accept taps too.

One practical note: the feature lives inside specific apps, not in the phone's settings. You cannot just enable it on a bare phone — you sign up with a processor, download their app, connect it to your account, and the Tap to Pay option appears where you take payments.

What It Costs vs. Buying a Card Reader​

Here is the part most "free card reader" headlines skip: Tap to Pay eliminates the hardware purchase, not the processing fee. Every tapped sale still pays the standard card-present rate. The real comparison has three parts: hardware cost, per-transaction rate, and any Tap-to-Pay-specific surcharge.

The hardware you skip​

Entry-level mobile readers are cheap but not free. A contactless-and-chip reader runs about 59 dollars from Stripe or Square, and countertop smart terminals climb to 249 dollars and above. Tap to Pay brings that line item to zero — attractive if you take in-person payments occasionally, work from a truck or market stall, or need a backup when the reader dies.

The per-transaction rates (US, 2026)​

Phone taps are priced as card-present transactions, the same category as a dipped or tapped card on a physical reader. Representative US rates from the two biggest providers:

• Stripe Terminal: 2.7% + 5 cents per successful in-person transaction, whether the tap lands on your phone or a Stripe reader.
• Square: about 2.6% + 10 cents for in-person tap, dip, or swipe on its standard plan, with Tap to Pay included at no extra charge.

Other providers differ — Bluevine's Tap to Pay, for example, runs 2.7% plus 30 cents per transaction with no setup fee — so check your own provider's current pricing before you commit. Rates change, and the numbers above are a snapshot, not a quote.

To make it concrete: on a 50-dollar sale, Stripe's 2.7% + 5 cents comes to 1.40 dollars, and Square's 2.6% + 10 cents comes to exactly the same 1.40 dollars. The headline rates look different; on typical tickets they are often pennies apart. Run your own average ticket through both formulas before assuming one is cheaper.

The small-print surcharge​

Some providers add a small per-tap fee for phone acceptance. Stripe, for instance, has charged around 10 cents per Tap to Pay authorization on top of standard processing in the US. That sounds trivial until you multiply it: 500 phone taps a month means 50 dollars a month in surcharges — at which point the 59-dollar reader you skipped would have paid for itself in about five weeks. This is the single most important line in the phone-vs.-reader math, so confirm whether your provider charges it.

A quick break-even rule​

• Under ~100 in-person sales a month: phone-only Tap to Pay almost always wins. Zero hardware, near-zero fixed cost.
• A few hundred taps a month with a per-tap surcharge: do the division. Hardware cost divided by the per-tap surcharge equals the number of taps where a reader breaks even. A 59-dollar reader against a 10-cent surcharge breaks even at 590 taps.
• High volume at a fixed counter: buy the reader (or a countertop terminal) and keep Tap to Pay as the backup for line-busting, sidewalk sales, and the day the reader walks off.

What You Give Up With Phone-Only Acceptance​

Tap to Pay is genuinely capable, but a phone is a compromise terminal. Go in with open eyes about the trade-offs.

Battery and availability​

Taking payments drains the same battery you need for calls, maps, and everything else. A busy market day can flatten a phone by mid-afternoon, and a phone on a charger behind the table is not taking taps. A dedicated reader has one job and its own battery. If you go phone-only, a power bank is not optional — it is part of the point of sale.

Chip-insert fallback​

Some cards and some large transactions still need a chip dip or another verification step the phone cannot do alone. Above certain issuer-set contactless limits, the customer may need to insert the card or complete extra verification — fine if you have a reader as backup, awkward if the phone is all you brought. Wallets like Apple Pay and Google Pay generally sail through higher amounts thanks to biometric authentication, but a physical card tapped for a four-figure invoice can hit issuer limits.

The customer-facing experience​

Handing a customer a reader feels like checkout. Asking them to tap your personal phone can feel odd the first time — for them and for you. Most buyers adapt instantly, but consider the ergonomics: no customer-facing display, PIN entry on your screen, and your phone notifications potentially lighting up mid-sale. A cheap phone stand and Do Not Disturb mode during selling hours solve most of this.

Multi-staff and high-throughput selling​

One phone means one checkout lane. Two employees selling at opposite ends of a booth need two logged-in devices. Dedicated terminals also pair better with barcode scanners, cash drawers, and receipt printers. Phone-only shines for solo operators; it strains as headcount and throughput grow.

Security and Transaction Limits​

The security story is strong — this is the same NFC rails-and-encryption stack as any contactless terminal. With Tap to Pay on iPhone, payment data is protected by the same technology that makes Apple Pay private and secure, and Apple does not store card numbers on the device or on Apple servers. Card numbers and transaction data stay between the customer, the processor, and the card network. Standard PCI compliance is handled through your processor's certified app, which is far simpler than certifying your own terminal setup.

On limits: Apple itself does not impose a transaction cap on Tap to Pay on iPhone — any ceiling comes from the customer's bank or card issuer, and from regional contactless rules abroad. In practice this means small and mid-size sales go through untouched, while very large taps may ask for PIN or fail over to chip. If your business routinely collects large sums in person — think contractors taking final payments on-site — test a large transaction before you depend on phone-only, and keep a reader or an invoiced bank-transfer option in reserve.

Keeping the Books Clean on Phone Taps​

Money that arrives by phone tap is still revenue, and the tax rules do not care which device captured it. Three habits keep Tap to Pay income audit-ready.

Book the gross sale and the fee separately​

Your processor deposits the net amount — the sale minus its cut. Do not record the net deposit as revenue. Record the full sale as revenue and the processing fee as its own expense. On a 50-dollar sale with a 1.40-dollar fee, your books should show 50 dollars of revenue and 1.40 dollars of merchant fees, reconciling to the 48.60-dollar deposit. Netting the two understates both your revenue and your deductible expenses, and it makes reconciliation against payout reports needlessly painful.

Reconcile payouts to the bank, not vibes​

Processors batch taps into payouts on their own schedule — daily, weekly, or with a holding delay for new accounts. Each payout bundles many sales minus fees and sometimes reserves or refunds. Monthly, tie every payout line in your bank statement back to the processor's payout report. The gaps that surface — a missing payout, a reserve hold you forgot, a refund you never recorded — are exactly the discrepancies that snowball into a year-end mess. If you want a visual check, Fava's reports make it easy to scan payout batches against bank balances.

Expect a 1099-K and keep it consistent​

Payment processors report your gross processing volume to the IRS on Form 1099-K. The thresholds for third-party settlement organizations have seesawed for years; the One Big Beautiful Bill retroactively restored the pre-2021 rule, so these organizations generally report only when a payee exceeds 20,000 dollars and 200 transactions in a year — but states can and do set lower thresholds, and card-transaction reporting follows its own rules. Whatever lands in your mailbox, the number on the 1099-K is gross volume: it must tie to the gross revenue in your books, not to your net deposits. The gross-minus-fees habit above is what makes that tie-out work. For the mechanics of recording these flows in plain-text books, the Beancount documentation covers income and expense accounts in detail.

Processing fees themselves are an ordinary and necessary business expense — deductible, but only if you recorded them, which is one more reason to split them out of every deposit.

Who Should Go Phone-Only — and Who Should Buy the Reader​

Go phone-only if you:

• Take in-person payments occasionally or seasonally (markets, fairs, pop-ups, house calls).
• Are starting out and want zero upfront cost before you know your volume.
• Need a backup for your main terminal more than a replacement for it.
• Sell solo, with one checkout lane and typical tickets under a few hundred dollars.

Buy the reader if you:

• Run a fixed counter with steady foot traffic.
• Process enough volume that a per-tap surcharge exceeds the hardware cost within weeks.
• Routinely take large in-person payments that may need chip fallback.
• Have multiple staff taking payments at once.

Many businesses land in the sensible middle: a reader at the counter, Tap to Pay enabled on the owner's phone as the free backup. That combination costs almost nothing extra and covers nearly every failure mode.

Getting Started Checklist​

1. Pick a processor on total cost for your volume — rate, fixed cents, and any Tap to Pay surcharge — not on the hardware price alone.
2. Confirm your phone qualifies: iPhone XS or later with a current iOS, or an NFC-enabled Android, plus the processor's app.
3. Complete identity verification early. Processors hold first payouts until verification clears; do it days before your first selling day, not during it.
4. Do a test tap with your own card for a small amount (then refund it) to confirm payouts reach your bank.
5. Set up receipt delivery and sales tax in the app before you sell — retroactively fixing tax collection is nobody's idea of fun.
6. Pack a power bank, enable Do Not Disturb while selling, and decide where the phone sits so customers can tap without handling your device.

Keep Your Payment Records Organized​

Taking cards on your phone removes the hardware barrier, but every tap still creates a sale, a fee, and a payout that your books need to reflect accurately. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.