Mobile Development October 26, 2026 5 min read

Tap to Pay on iPhone: Accept Cards in Your Own App

How to add Tap to Pay on iPhone and Android to your business app: payment SDKs, Apple's entitlement process, field-ready UX and the pitfalls that delay launch.

For businesses that take payments in the field, such as service technicians, event staff, delivery drivers, mobile salons and pop-up retail, card readers have always been one more thing to charge, pair, carry and lose. Tap to Pay removes the hardware: the phone itself accepts contactless cards, phones and watches.

Off-the-shelf point-of-sale apps already offer it. But if your business runs on its own app, tying the payment to the job, the ticket or the customer record is where the real value is. This guide covers what it takes to build Tap to Pay into your own app.

What Tap to Pay Is

Tap to Pay on iPhone lets a supported iPhone accept contactless credit and debit cards, Apple Pay and other digital wallets using its built-in NFC, with no extra hardware. Android has an equivalent, often called Tap to Pay on Android, on NFC-capable phones.

You don't build the payment processing yourself. You integrate through a supported payment provider, such as Stripe, Square or Adyen, whose SDK handles card reading, security and settlement. Your app handles the business side: what's being paid for, by whom, and what happens next.

Why Build It Into Your Own App

One workflow. The worker completes the job and takes payment on the same screen, without switching to a separate POS app and re-typing the amount.
Payments linked to records. Every payment is tied to the right job, ticket or customer automatically, which makes reconciliation far easier.
Tips and receipts. Tip prompts and digital receipts can follow your business rules and branding.
No hardware fleet. No readers to buy, charge, pair or replace.

The Building Blocks

1. Choose a payment provider

Pick a provider that supports Tap to Pay on both iPhone and Android in your markets, with SDKs for your app's technology. If you use React Native, check that the provider offers a maintained React Native SDK or plan for a native bridge. Compare fees, payout timing and how well its reporting fits your accounting. Our mobile payments integration guide compares common options.

2. Request Apple's entitlement early

Tap to Pay on iPhone requires a special entitlement that Apple grants to your developer account. This is the step that most often delays launch:

You request it from Apple with information about your app and business.
Approval typically comes first for development, so you can build and test, and distribution approval for App Store and TestFlight builds is a separate step.
Your provisioning profiles must actually include the entitlement. A profile created before the grant, or an invalid one, will silently leave it out, and the feature won't work in TestFlight even though it works in development.
If your app moves between developer accounts, confirm which account holds the entitlement.

Start this process at the beginning of the project, not the end.

3. Follow the platform's experience guidelines

Apple publishes requirements and guidelines for the Tap to Pay experience, such as how merchants are introduced to the feature and how the payment screen is presented. Review them before designing your screens, because App Review checks them.

4. Build the backend connection

The payment SDK needs a secure connection token or session from your server, and your server should record each payment against the job or customer and confirm the final status from the provider, not just from the app. Never treat "the app said it worked" as proof of payment. Confirm it on the server.

Designing for the Field

Few taps to payment. The amount should already be filled in from the job.
Clear instructions for customers. Show where to tap and confirm success with a big, unmistakable screen.
Graceful failures. Declined cards, timeouts and lost connections need clear next steps, such as retry, another card or a payment link sent by text.
Offline realities. Know how your provider handles poor connectivity, and don't let the app lose track of a payment that's in progress.
Device support. Tap to Pay requires recent phones. Check your crew's devices and set a minimum supported model.

For more on building for field conditions, see field service mobile apps.

Testing and Launch

Test with provider test cards in development, including declines and errors.
Verify the entitlement in a TestFlight build, not just a development build, before planning a launch date.
Reconcile end to end. Confirm that a test payment appears in the provider dashboard, your database and your accounting with matching amounts.
Pilot with a small team before rolling out to everyone.

Frequently Asked Questions

Do I need a card reader for Tap to Pay?

No. Tap to Pay uses the phone's built-in NFC to accept contactless cards and digital wallets. Chip-and-PIN or swipe-only cards still need a separate reader, so some businesses keep one as a backup.

Which iPhones support Tap to Pay?

Tap to Pay on iPhone requires a recent iPhone model running a current version of iOS. Check Apple's and your payment provider's current requirements and set a minimum device for your team.

How long does Apple's Tap to Pay entitlement take?

It varies. Plan for it to take time, and request it at the start of the project. Remember that development and distribution approval can be separate steps, and your provisioning profiles must be regenerated to include it.

Can React Native apps use Tap to Pay?

Yes, if your payment provider offers a React Native SDK or you build a native bridge to its iOS and Android SDKs. See our React Native for business apps guide.

Open Door Digital builds mobile apps with payments built into the workflow, from entitlement to reconciliation. Talk to our team about taking payments in your app.