Tap to Pay on iPhone for business: the setup steps, and the cards it will still refuse

Tap to Pay on iPhone for business needs no reader, no dongle and no hardware order: you turn it on inside a payment app you already use, and your customer taps a contactless card or phone against yours. Setup takes about ten minutes. The part most guides skip is the list of cards and amounts a tap still cannot take, and what you do when one of them turns up at your stall.

Everything below comes from Apple's own developer pages, Stripe's Terminal documentation and Square's US help article, all read on October 23, 2026. Requirements, fees and country lists on those pages change without notice, so check the current version of each page before you rely on a number.

What Tap to Pay on iPhone for business gives you, and what it does not

Apple's feature is a contactless reader built into the phone. Apple's developer page says a supported payment app can accept "contactless payments from contactless credit or debit cards, Apple Pay, Apple Watch, and smartphones with other digital wallets", and that Tap to Pay on iPhone requires a supported payment app and the latest version of iOS.

Two things follow from that sentence. First, there is no slot and no magnetic stripe: the phone reads a tap, so a chip-only card or a worn stripe card has nowhere to go. Second, Apple does not sell this to you directly - it licenses it to payment service providers, so your options are whichever processors offer it in your country. Apple's regions page listed 60 countries and regions on the day we read it, with Granito in Brazil marked "Coming soon", and it states that availability depends on a provider supporting the feature in your market.

Apple also puts two warnings on that page, in its own words: "Some contactless cards may not be accepted by your payment app" and "Transaction limits may apply." The vendor docs below say what those two lines mean in practice.

The quiet extra is reading without charging. Apple says a merchant can read a card "without making a charge" to add it to a customer's file or look up an earlier purchase, and that NFC loyalty, discount and points cards in Apple Wallet can be read as well. Whether your app exposes either is up to the app.

How to set up Tap to Pay in the Stripe Dashboard app

Stripe's no-code route is the Stripe Dashboard mobile app - no custom point of sale, no reader. Stripe's no-code in-person guide lists the requirements as a Stripe account, the Dashboard app, location permissions enabled, and on iOS "iPhone XS or later. The device must have a passcode set and be signed into iCloud." It also tells you to enable NFC on the device before your first payment.

The flow, as the guide gives it:

1. Download the Stripe Dashboard app and sign in to your Stripe account.
2. Enable NFC and grant location permissions on the phone.
3. Tap the add symbol from any tab and select Charge a card or send an invoice.
4. Enter the amount to charge.
5. Select Tap to Pay as the payment acceptance option.
6. When the Tap to Pay symbol appears, ask the customer to tap their card or phone and follow the on-screen instructions.

That route accepts contactless Visa, Mastercard, American Express and Discover cards plus Apple Pay, Google Pay and Samsung Pay, according to the same page. If a tap will not go through, the identical screen lets you key the card number in by hand - Stripe's guide says that if you cannot accept a Tap to Pay payment in the Dashboard app, you can manually charge a card from the same Charge a card or send an invoice flow. Minimum and maximum charge amounts are the same as Stripe's online limits.

Stripe is listed in our Payments & Banking category, and its Dashboard app is the fastest path we know of from a standing start to a first contactless payment, because there is nothing to build and nothing to ship.

How to turn it on in Square Point of Sale

Square puts the switch in the app's settings rather than in the payment flow. Square's help article says to use "an iPhone XS or newer", to make sure "your iOS software is updated to the latest version", and to set Date & Time to automatic. It also says plainly: "Tap to Pay on iPhone is not available on iPads."

The steps it gives:

1. Sign in on the iPhone and turn on a passcode in the Face ID & Passcode settings.
2. In the Square app, go to More > Settings > Account and turn on Tap to Pay on iPhone.
3. Verify that the correct Apple Account is shown, and switch accounts if it is not.
4. Tap Agree & Continue to finish.

Square's US article also publishes the per-transaction ceilings: "a per-transaction limit for contactless payments of $50,000" and "a per-transaction limit for physical contactless cards of $10,000". The gap between those two numbers is the clearest example of Apple's "transaction limits may apply" line - a phone wallet and a plastic card are not treated alike.

On price, Square's US fees page lists in-person card-present rates of 2.6% + 15¢, 2.5% + 15¢ and 2.4% + 15¢ depending on plan, described as applying "to in-person payments when a card is present". It does not publish a separate Tap to Pay rate, so in our view you should treat your normal in-person rate as the rate until your own dashboard shows otherwise. Square is also listed on Upfynd.

Which iPhone models support Tap to Pay, and which software versions

The hardware floor is consistent across the vendors we read; the software floor is not stated the same way twice.

Third-party guides we saw while researching this post gave the minimum as iOS 16, iOS 16.4 and iOS 17.4 - three different answers on one results page. None of the vendor pages we read names a single fixed minimum build. Stripe's doc instead points at Apple's Business Register documentation for the supported iOS list and warns that "device and minimum SDK version requirements can change due to updated compliance requirements or security vulnerabilities". Our reading: do not plan around a floor version at all. Keep the phone on current release iOS, keep it off the beta channel, and keep a second phone that is also eligible.

Five times the tap fails, and what to do instead

This is the section worth bookmarking. Each case below is named in Stripe's Tap to Pay documentation or Square's help article, not inferred.

The amount is above the contactless verification limit. Above a certain figure, the card scheme wants a PIN. Stripe's support page lists those contactless limits by market: 100 GBP in the United Kingdom, 250 CAD in Canada, 50 EUR across most eurozone countries, 200 NZD in New Zealand, 15,000 JPY in Japan, and 100-200 AUD in Australia depending on the scheme. Transactions above those amounts "might require PIN verification, depending on issuer requirements". Tap to Pay can collect that PIN on screen from iOS 16.4 - but only if your app has implemented it.

The card is offline-PIN only, in Canada or Finland. Stripe's doc is blunt here: "In Canada and Finland, many issued cards are offline PIN only, meaning that entering the PIN requires physical contact, such as insertion into a device, which isn't supported with Tap to Pay." There is no on-screen workaround. If you trade in either country, we would not treat a phone on its own as your only way to take a card.

A UK issuer insists on insertion. Per the same doc, in the UK "depending on the issuer, Strong Customer Authentication might require some cards to be inserted into a device", and when that happens the payment is declined before the PIN screen appears, with the reason `offline_pin_required`.

The card is simply not supported by your app. Apple's own wording - "some contactless cards may not be accepted by your payment app" - covers the long tail of regional and store cards. Stripe adds that regional schemes work only in their markets: eftpos in Australia, Interac in Canada, Cartes Bancaires in France.

The customer brought a chip-only or stripe-only card. There is nothing to insert or swipe, so there is nothing to do with it on the phone.

Stripe's recommended fallbacks for all of the above are to ask for a different card, use a physical card reader, or send a payment link. That matches what we would do, with one addition: decide which fallback you will use before the queue forms. Manual card entry inside the same app is the fastest of the three, a QR-code payment link needs only the customer's own phone, and a reader is the only option that solves insertion properly.

If your team is not on iPhones, check the Android list first

The equivalent feature exists on Android, and Stripe's Android documentation sets a longer list of conditions than the iPhone version does. A device must run Android 13 or later, have a security update installed from the past 12 months, use Google Mobile Services with the Play Store installed, be unrooted with an unmodified manufacturer OS and a locked bootloader, have Developer options disabled, and have a stable internet connection. Emulators are not supported.

PIN collection is stricter still: Stripe says a PIN can only be collected when Developer options are off, accessibility services are not running, screen recording is not active and there are no screen overlay windows, and that PIN collection fails if anyone attempts a screenshot. An old handset kept in a drawer is unlikely to clear all of that. Check your exact model against the supported list rather than assuming any modern phone with NFC qualifies.

What to do next

Start with your current processor, not a new one: if you already take card payments online, the app you have may be one tap-to-pay switch away from taking them in person. As of October 2026, Upfynd lists 124 products in Payments & Banking, including PayPal and Moneris alongside Stripe and Square, and whether a given provider's app supports Tap to Pay in your country is a question only its own support pages can answer. Tools for the rest of the counter - scheduling, stock, staff - sit in Operations.

Then run one test before a paying customer is involved: charge yourself a small amount on a plastic contactless card, not a phone wallet, because plastic is where PIN prompts and insertion requirements show up. If you build payment software yourself, our directory takes free product submissions.

None of this is legal or financial advice, and the limits above are market-specific. Where real money depends on a rule - a contactless ceiling, a Strong Customer Authentication requirement, a surcharge you plan to add - read the current rules for your own market and take professional advice.