# Passing App Review with a Tap to Pay App: What Apple Checks

> Published: 2026-11-20
> Updated: 2026-11-20
> Author: Mathias Nielsen
> Canonical: https://finalpos.com/blog/tap-to-pay-app-review

Passing a Tap to Pay App Review takes more than working code. Learn what Apple checks in your UX, button labels, and merchant onboarding flow before granting distribution approval.

You can spend three weeks wiring up your payment service provider SDK, testing contactless cards on your local device, and celebrating your first successful sandbox transaction, only to get rejected by Apple within four minutes of submitting your build. Most developers assume that once the code works on a test phone, the hard part is over. With a Tap to Pay App Review, the code is barely half the battle.

Apple treats the iPhone payment sheet and the surrounding checkout flow as an extension of its own hardware brand. When you build an app that turns an iPhone XS or later into a payment terminal, Apple audits your button labels, your onboarding screens, your help documentation, and the exact phrasing you use to describe contactless payments. Improvise any of those pieces and your binary comes right back.

This scrutiny is just one piece of [how to accept card payments in your own POS app](/blog/accept-card-payments-custom-pos-app). Before you ever submit a binary to App Store Connect, you have to pass a distinct compliance gate between development and distribution. Knowing what reviewers look for will save you weeks of rejections.

## What is in the checklist Apple sends with the development entitlement?

Apple's Tap to Pay user experience requirements and marketing guidelines form a strict compliance checklist that arrives the moment they approve your development entitlement. You cannot legally distribute a Tap to Pay app on the App Store without proving your app meets every line item in this documentation.

**TL;DR:** Apple divides the entitlement into development and distribution phases. You only unlock the distribution entitlement after proving your app meets the UX and marketing checklist Apple emails you during the first phase.

The two-stage approval process trips up a lot of teams. When your Organization Account Holder requests [the Tap to Pay on iPhone entitlement](/blog/tap-to-pay-iphone-entitlement) (which requires an organization developer account backed by [a D-U-N-S number](/blog/duns-number-apple-developer)), Apple grants a development-only entitlement first. This lets your engineers compile the app locally and run transactions in a sandbox environment.

Along with that initial approval, Apple sends over the Human Interface Guidelines and marketing specifications for Tap to Pay on iPhone. Before Apple grants the distribution entitlement required to ship on TestFlight or the App Store, you have to re-request access and submit proof that your interface follows their rules.

The checklist covers five core areas:
* **Terminology and naming:** Exact phrasing for buttons, menus, and promotional banners.
* **Merchant onboarding and education:** How your app teaches a new user to enable the feature and run their first card.
* **Terms and Conditions:** How the merchant links their Apple ID and accepts Apple's Tap to Pay terms via the ProximityReader API.
* **Checkout UX:** Where the payment total sits and how fast the native Apple payment sheet appears after the cashier taps charge.
* **Fallback handling:** What happens on screen when a card read fails, requires a PIN, or needs a different payment method.

Treat this stage like a standard iOS library integration and you'll fail both the distribution entitlement review and the final App Store review. You have to build the exact screens Apple asks for.

## Button labels and entry points

What should the Tap to Pay button say in your checkout flow? According to Apple's Tap to Pay marketing guidelines, your primary action button must use the exact phrase "Tap to Pay on iPhone", or "Tap to Pay" in tight UI layouts where screen space is constrained.

![Smartphone displaying a clean checkout button and contactless wave icon for Tap to Pay on iPhone UX compliance](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/7e9b268c1b4f911e-tap-to-pay-app-review-section-2-v2-en-us.png)
*Your checkout button must trigger Apple's native system payment sheet immediately without custom intermediate screens.*


Teams still try inventing their own labels. They submit builds with buttons labeled "Apple Tap", "iPhone NFC", "Contactless Terminal", or "Wave Card Here". Every one of those triggers an automatic rejection during a Tap to Pay App Review.

Capitalization matters too. "Pay" and "Tap" are capitalized, "to" and "on" are lowercase, and "iPhone" always has a lowercase "i" and an uppercase "P". Never pluralize "iPhone" or stick the Apple logo next to the text.

Reviewers also check what happens the millisecond the cashier taps that button. Your app must invoke the native system payment sheet immediately. Don't put an intermediate custom screen between the "Tap to Pay on iPhone" button and Apple's native NFC prompt that mimics a card reader or tells the customer where to hold their card. Apple's system UI handles the animation, the sound, and the tap zone prompt. Your only job is to pass the transaction amount to your PSP SDK and get out of the way.

If your app supports external hardware readers alongside phone-based NFC, keep those entry points clearly separated. A cashier should know before tapping whether they're waking up a Bluetooth card reader or triggering Tap to Pay on the phone in their hand.

## Why does Apple reject merchant onboarding and terms acceptance flows?

Apple requires every app using the ProximityReader framework to guide merchants through a formal setup and terms acceptance flow before they take their first live payment. You can't bury this step in a hidden settings menu or run it silently in the background on launch.

During onboarding, the merchant has to connect their business Apple ID to their merchant account and accept Apple's Tap to Pay on iPhone Terms and Conditions. Your PSP SDK calls Apple's `PaymentCardReader` API to handle the legal handshake, popping up an Apple-hosted modal for the merchant to sign.

Reviewers look for three specific pieces around this handshake:

1. **An explicit activation prompt:** A clear screen inviting eligible users to enable Tap to Pay on iPhone and explaining what it does.
2. **Device compatibility checks:** Your app must verify in code that the device is an iPhone XS or later running a supported iOS version before showing the setup prompt. iPads don't support Tap to Pay on iPhone because Apple restricts the entitlement to iPhone hardware. If a reviewer opens your universal binary on an iPad and sees a broken "Enable Tap to Pay on iPhone" banner, they'll reject the build.
3. **Built-in merchant education:** Once enabled, your app has to show the cashier how to take a payment, specifically instructing the customer to hold their card or Apple Watch horizontally at the top of the phone over the contactless symbol.

## Testing evidence for reviewers

The reviewer in Cupertino doesn't have a live merchant account with your payment processor, and they aren't going to fill out a W-9 or link a bank account to test your checkout screen. If they log into your demo account and hit a "Verify Your Business Identity" wall, your app is dead on arrival.

![Developer filming a physical iPhone walkthrough video for a Tap to Pay App Review submission using a tripod setup](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/976b19d2cb19ed18-tap-to-pay-app-review-section-4-en-us.png)
*Because simulators cannot render the ProximityReader sheet, Apple requires a video walkthrough filmed on a physical iPhone to grant distribution entitlements.*


To pass both the distribution entitlement check and App Store Review, hand the reviewer a pre-configured demo login and video evidence.

When you re-request the entitlement for distribution, Apple asks for a video showing the complete user journey on a physical iPhone. Don't send a simulator recording. The simulator can't render the actual ProximityReader payment sheet. Film a real iPhone going through your merchant onboarding, accepting the Apple terms, ringing up an item, tapping the "Tap to Pay on iPhone" button, presenting the native payment sheet, and landing on the approved receipt screen.

When you submit the binary to App Store Connect, put these three things in the App Review Information notes:
* **Demo credentials** for an account already approved for card processing in a sandbox or test mode that still triggers the real ProximityReader sheet.
* **Exact navigation steps** to reach both the merchant education screen and the checkout button (e.g., "Tap Catalog > Select Coffee > Tap Charge > Tap 'Tap to Pay on iPhone'").
* **A link to the video walkthrough** you recorded for the entitlement team, in case the reviewer's test environment prevents them from completing a test card read.

## Common reasons a Tap to Pay app gets rejected

Even when the payment sheet works and the labels match the style guide, apps bounce back for configuration and architectural mistakes.

### Submitting with the development entitlement
Your local builds work fine with the `com.apple.developer.proximity-reader.payment.acceptance` entitlement configured for development. App Store Connect, however, requires a provisioning profile generated with the production distribution entitlement. Push a build before Apple upgrades your account to distribution — or forget to regenerate your provisioning profile after they do — and the upload or review fails.

### Splitting the transaction across two devices
Tap to Pay runs on a single device from start to finish. You ring up the sale on the phone, and the customer taps their card on that same phone. Some developers build a browser-based register or an iPad counter app and try using an iPhone strictly as a tethered NFC reader. That violates how the framework operates and how reviewers expect the POS flow to work; [whichever device takes the Tap to Pay payment must be the device the sale is rung up on](https://finalpos.com/help/take-a-tap-to-pay-payment).

### Failing on iPad compatibility checks
Leave the iPad destination checked in Xcode and App Review will test your build on an iPad. When the reviewer taps your payment button on an iPad and your app crashes or throws an unhandled error from the PSP SDK because `PaymentCardReader.isSupported` returned false, you get rejected under Guideline 2.1 (App Completeness). Check hardware support in code and hide the Tap to Pay on iPhone entry point on unsupported devices.

### Broken fallback or cancellation states
Reviewers test the unhappy path. They'll open the Tap to Pay sheet and immediately tap "Cancel", or let the sheet time out. If your app freezes on a loading spinner or marks the order as paid when the sheet closes without a token, you fail review. Return cleanly to the payment selection screen so the cashier can retry or switch to cash.

## Shipping without your own review: Final

Building a custom checkout flow for your shop or your agency clients shouldn't mean getting a D-U-N-S number, wiring up a low-level PSP SDK, filming compliance videos for Apple, and babysitting provisioning profiles through App Review.

![Customer tapping a contactless card on a merchant's smartphone at a minimal boutique counter using a pre-approved POS app](https://storage.googleapis.com/final-os-media/media/43399b6a-0d29-48b6-84dd-88ef01fcb193/generated/d5a3c1192a10edd8-tap-to-pay-app-review-section-6-en-us.png)
*With Final Station, Tap to Pay is already approved and live — letting you deploy custom checkout flows from Flow Studio to your phone on day one.*


We already went through all of that. At Final, our native Final Station app is approved, signed, and live with Final Pay and Tap to Pay on both iPhone and Android, alongside our hardware line (Final Move, Final Touch, Final Touch Pro, and Final Register).

Instead of spending two months building an iOS payment app and fighting through a Tap to Pay App Review, open Flow Studio and build a custom POS around your exact workflow in minutes. Most makers grab a ready-made flow from the Flow Library and adjust it, or describe what they need so Flow Studio builds it from the prompt. Every flow runs on real commerce rails (catalog, tax, inventory, and Final Pay), so your custom checkout comes wired for card-present payments out of the box.

Publish a change in Build and Run deploys it to Final Station on your iPhone immediately — no App Store wait. You get a [POS system with no monthly fee](https://finalpos.com/lp/pos-system-with-no-monthly-fee), 1,000 free build credits per day (up to 5,000 a month), and flat card-present processing rates: 1.99% + $0.10 CAD in Canada, 0.99% + €0.10 in Europe, and 2.49% + $0.10 in the US and worldwide. Cash is always $0.

Skip the UX checklists, button-label audits, and physical device walkthrough videos. Open Final, build your checkout in Flow Studio, and download Final Station on the iPhone already in your pocket.

## FAQ

**Q: What does Apple check in a Tap to Pay app?**
A: Apple checks your app against the Tap to Pay user experience requirements and marketing guidelines they send when granting your development entitlement. Reviewers audit your exact button labels, the merchant onboarding and terms acceptance flow, built-in merchant education screens, and how cleanly your app triggers the native payment sheet on supported iPhones.

**Q: What should the Tap to Pay button say?**
A: Apple's marketing guidelines require your button to say "Tap to Pay on iPhone", or "Tap to Pay" in tight layouts where screen space is constrained. Custom variations like "Apple Tap", "iPhone NFC", or wrong capitalization will get your build rejected.

**Q: Why was my Tap to Pay app rejected?**
A: Most rejections happen because the team submitted the build before upgrading from the development entitlement to the distribution entitlement, used custom button labels, or skipped the mandatory merchant onboarding and education flow. Builds also get rejected if they show the Tap to Pay option on unsupported hardware like an iPad.