Skip to content
Desk

How to take a card payment on Android without buying a reader

Tap to Pay turns a compatible Android phone into the reader in Desk. See when that's enough, when you need manual entry or a payment link, and what each one costs.

Desk Team

7 min read

Leer en español

What you'll take away

  • What Tap to Pay on Android actually needs, and why it depends on the app
  • The two fallback options for a card that won't tap, and what each one costs
  • A plain-language comparison of Tap to Pay, manual entry, and payment links
  • How to turn it on in Desk, step by step

about 10 minutes, if your phone and Stripe account already qualify

Can you really take a card without buying anything?

Short answer: yes, if you have a compatible Android phone. Tap to Pay turns the phone itself into the payment terminal for contactless cards, Apple Pay, Google Pay, and other digital wallets - no separate reader, no extra hardware. The condition is real, though: it only works on supported devices, running a current enough Android version, inside an app that has specifically built the feature in - it's not something every card-taking app on Android does automatically.

For everything else - a card that won't tap, or a payment you're taking over the phone - you still get paid without a reader, just through a different path. That's what the rest of this covers.

Tap to Pay: what it needs and what it can't do

Short answer: Tap to Pay on Android needs a specific device and software bar, and only works inside an app that supports it. It reads contactless cards and digital wallets only - it can't read a card that has no contactless chip.

Stripe's version, Tap to Pay on Android, needs a phone that meets a fairly specific bar: a working NFC sensor, an ARM-based processor, Android 13 or later, a security update installed in the past 12 months, Google Mobile Services with the Play Store, a hardware-backed keystore, a stable internet connection, and a phone that isn't rooted or bootloader-unlocked. Meet all of that, and the phone can read contactless Visa, Mastercard, Amex, and Discover cards, plus wallet taps from Apple Pay, Google Pay, and Samsung Pay - PIN entry included when a card needs it.

Tap to Pay on Android works with a variety of Android devices... You can only discover and connect to devices that meet all of the following criteria: [...] Runs Android 13 or later [...] Uses Google Mobile Services and has the Google Play Store app installed [...] Isn't rooted and device bootloader is locked and unchanged.

Two honest limits to plan around:

  • Availability. Not every Android phone qualifies, and the certified device list is narrower than Apple's for iPhone - check your specific model against Stripe's requirements before you rely on it. It also depends on your payment provider supporting it in your region.
  • Card type. It reads contactless cards, Google Pay, Samsung Pay, Apple Pay, and other tap-capable wallets. A card with no contactless chip - still common with some older or international cards - won't tap, full stop.

When a customer's card won't tap

Short answer: you have two fallback options that still need no extra hardware - typing the card number in manually, or sending a payment link. They're not interchangeable: one costs more and carries more risk, the other is better suited to payments you're not taking face to face.

A phone with only tap capability has no slot for a chip or a swipe. So when a card doesn't tap - or the phone itself doesn't qualify for Tap to Pay - you're choosing between two things: keying in the card details by hand, or sending a secure link so the customer pays from their own device. Both skip the reader entirely. They just trade convenience for cost, or for timing.

What manual card entry actually costs you

Short answer: typing a card number in by hand usually costs more per transaction than tap or chip. If the charge turns into a dispute, the merchant is typically the one holding the risk.

Card networks price a manually keyed transaction higher than the same card tapped or dipped. There's no physical or contactless proof the card was actually present, so the risk moves onto you. One payment processor's public fee guide puts it in concrete terms:

"While swipe transactions might have fees around 2.6% plus $0.10, keyed transactions can cost about 3.5% plus $0.10."

That's not a number any specific processor promises you - rates vary by provider and card type - but the direction is consistent across the industry: keyed entry costs more per swipe than tap or chip.

There's a second cost that doesn't show up on the statement. If a keyed transaction is later disputed as fraud, the business - not the card network - is usually the one left covering it. There's no chip or tap record to prove the card was physically there. None of that means you should avoid manual entry entirely. It means treat it as the fallback for the odd card that won't tap, not as the default way you take payments.

Short answer: a payment link is a page you send the customer, and they pay from their own phone or computer. It's useful for a deposit, a no-show fee, or any charge where the customer isn't standing in front of you.

A link skips your device's card-reading step altogether, unlike Tap to Pay or manual entry. You send it by text or email. The customer types their own card into a secure page, and the charge goes through without you ever seeing the number. That fits phone bookings, a deposit taken before the appointment, or a client calling later to settle a balance - cases where there's no card in the room to tap in the first place.

Want the full picture on when a deposit link fits your business? How to reduce no-show appointments covers the deposit side of this in more detail.

Ready to put this to work instead of comparing options? Desk Free covers the appointment and client side with no limit and no subscription. Connecting Stripe for payments is one setup step inside the app, not a separate purchase.

Getting your phone ready to take a payment in Desk

Short answer: the owner authorizes a payment provider once, adds where the business operates, and chooses whether the phone alone is enough or a separate device joins it. Budget about 10 minutes if the phone already qualifies.

This groundwork happens once per business, not once per client. Skip any piece of it and the charge screen simply won't let a transaction through until it's filled in - there's no way to accidentally take a payment before the account is authorized.

Two things unlock everything else. First, authorizing the payment provider from inside the app. Second, telling it where the business is physically based - a requirement from the processor's side, not Desk's, since in-person charges need a real address on record. After that, the owner decides whether tapping the phone itself is the plan, or a separate handheld device should back it up. If the phone qualifies for Tap to Pay, the first real tap triggers a short, one-time walkthrough from the phone's own operating system. If it doesn't, a physical Stripe reader - WisePOS E, Reader S700, Verifone P400 - pairs through a browser on Desk's web dashboard instead.

Important. From that point on, one charge screen offers every way to get paid at once. Tap the phone or a paired device, type the number in by hand, or text a secure link - a single client isn't limited to whichever method you set up first.

Whichever path collects the money, Desk turns it into an invoice on its own, and a client who has agreed to texts sees the receipt land in their messages.

Which option should you use today?

Short answer: default to Tap to Pay for anything face to face if your phone qualifies, reach for a payment link when the customer isn't in front of you, and keep manual entry as the occasional fallback, not the plan.

Situation Best option Why
Customer is in front of you, your phone qualifies and the card taps or they use a wallet Tap to Pay No reader to buy, no keyed-entry markup
Customer is in front of you, card has no contactless chip, or your phone doesn't qualify Manual Card Entry Works on any Android phone, no setup beyond a Stripe account
Customer is on the phone, or paying a deposit before the visit Payment link No card ever entered on your device
You want every physical card format covered, including swipe/dip, or your phone isn't on the qualified list A physical card reader, paired from the web dashboard Trades a small hardware cost for handling every card type and every device

None of these require buying anything up front except the optional physical reader. Tap to Pay, manual entry, and payment links all run on a phone you already own - Tap to Pay only if your specific model and Android version qualify.

Sources

Setting up payments is one step inside Desk Free - appointments and client records come with no limit and no subscription, and SMS and payment processing are billed separately as you use them.

All articles