Prepare Tap to Pay on iPhone for release
Separate development permission, publishing entitlement and App Store distribution, and design the required merchant journey.
Build the whole merchant journey
The app must support merchant onboarding, enabling Tap to Pay, merchant education and checkout. It must function without requiring a second app or device. Prepare the reader when the app starts or returns to the foreground. Retrieve terms acceptance from Apple instead of trusting a local flag. Follow the full source review checklist for conditional requirements.
Make regional behavior explicit
Use the approved localized product name. Include PIN and accessibility education where required. The regional source identifies a fallback payment method requirement for the UK, and regional surcharge display and receipt itemization requirements. These are review requirements, not a claim that every account supports surcharging or every region is commercially enabled. Market example Documented naming US / UK / Australia Tap to Pay on iPhone France Tap to Pay sur iPhone Netherlands Tap to Pay op iPhone Brazil Tap to Pay no iPhone
Request publishing entitlement
Apple publishing-entitlement review precedes distribution review. Supply videos of a new user, an existing user and checkout. Record with a separate device because the protected Tap to Pay screens do not appear in normal screen recordings. Enterprise distribution still requires an entitlement review for each app.
Release with the approved configuration
Keep the signing identity, entitlements, permitted regions and account configuration aligned with the reviewed app. Recheck the current SDK release bundle before publishing. This guide is an implementation checklist; approval remains with Apple and the payment program.