📘
Currently Tap to Pay is in Beta Release. If you would like to participate, please reach out to your Account Manager.

Use this page to review Apple’s user experience requirements for Tap to Pay on iPhone and prepare your app for publishing entitlement review.

Apple evaluates your app across four parts of the Tap to Pay on iPhone user journey:

Onboarding merchants
Enabling Tap to Pay on iPhone
Educating merchants
Checking out

General requirements

This section covers requirements that apply across the full Tap to Pay on iPhone experience. The requirement number matches the code in the checklist you complete for Apple app review.

❗️
IMPORTANT
An app that uses Tap to Pay on iPhone must be able to function without the need for any
additional secondary apps. For example, a merchant must be able to open your app and complete the Tap to Pay on iPhone onboarding and checkout flow without requiring any other apps.

If you are considering allowing third-party apps to invoke your app for Tap to Pay on iPhone functionality, you must also provide an SDK that third parties can integrate directly into their applications.

If your Tap to Pay on iPhone app accepts payments when the checkout flow is initiated from another device, such as an iPad or a website, the user must be able to complete payment acceptance within the iPhone app as a standalone app, without requiring another device or interface.

Before you submit for review, confirm that your app:

Runs on supported devices only
Retrieves Terms & Conditions acceptance status from Apple
Warms up Tap to Pay on iPhone when the app launches or returns to the foreground
Follows Apple Human Interface Guidelines and Marketing Guidelines when those rules apply

Req	Status	Description
1.1	Required	Your app must support Tap to Pay on iPhone only for compatible devices (iPhone XS and later).
1.2	Required	If Tap to Pay on iPhone is the main feature of your app, you must set the iOS Deployment Target in Xcode to the minimum version supporting your Tap to Pay.
1.3	Required	For iOS versions prior to 16.4, your app must handle the PaymentCardReaderError.osVersionNotSupported error by displaying a message informing the user to update to the latest version of iOS.
1.4	Required	Your app must trigger the initial preparation and warm-up of Tap to Pay on iPhone at launch or when your app comes to the foreground. Check with your PSP for implementation details.
1.5	Conditional	If your app supports Tap to Pay on iPhone as the sole payment acceptance method, ensure that only compatible devices can download the app by requiring iPhone-iPad-minimum-performance-a12 with UIRequiredDeviceCapabilities.
1.6	Required	The status of whether a merchant has accepted the Tap to Pay on iPhone Terms & Conditions should be retrieved from Apple, not from a local variable in your app. Check with your PSP for implementation details.
1.7	Conditional	Apps on the public App Store must adhere to the Human Interface Guidelines.
1.8	Conditional	Apps on the public App Store must adhere to the Marketing Guidelines.

Onboarding merchants

Use this section to review how merchants discover, complete, and return to onboarding in your app.

Apple requires an in-app digital onboarding flow for apps available on the public App Store. During onboarding, the user registers as an authorized merchant to accept payments with Tap to Pay on iPhone. While you can require additional verification for some users, such as background or risk checks, most eligible users should be able to complete onboarding quickly in your app.

In accordance with local regulations, the onboarding process should take no longer than 15 minutes on average from application completion to first payment acceptance. If merchant approval is not instant, confirm approval through multiple channels, such as push notifications, email, or SMS, so the user can return to the app and finish onboarding.

Allow existing users, such as merchants, business account owners, and consumer account owners, to access Tap to Pay on iPhone with their existing login credentials. If a merchant cannot use existing credentials, provide a path in your app to create the credentials required to use Tap to Pay on iPhone. When possible, reduce the number of separate logins required.

If location services are required for your app to accept payments, show a pre-alert screen during onboarding that explains why location access is needed.

Onboarding merchants requirements

These onboarding requirements apply to all apps on the public App Store.

If there is no mechanism for users to onboard to your app, you must distribute it through programs such as Unlisted apps, Custom apps, or the Apple Developer Enterprise Program (ADEP).

Req	Status	Description
2.1	Required	The process for creating an account and/or gaining access to Tap to Pay on iPhone must be easily discoverable for a new user who has just downloaded your app.
2.2	Required	The process for creating an account and/or gaining access to Tap to Pay on iPhone must include a digital onboarding experience triggered from your app that can be fully completed on an iPhone.
2.3	Required	Digital onboarding must take less than 15 minutes_ for most of your users, from information submission (or access request for existing merchants) to accepting payment with Tap to Pay on iPhone.

Enabling Tap to Pay on iPhone

Use this section to review how your app introduces Tap to Pay on iPhone and guides eligible users to enable it.

The app must provide at least one in-app awareness moment to all eligible users, informing both new and existing users that Tap to Pay on iPhone is available in the app.

As a best practice, provide the awareness moment as a full-screen modal. In addition to a full-screen modal, you can give other awareness moments via in-app notifications, information cards, or notification badges.

For new users, enabling Tap to Pay on iPhone must be part of the digital onboarding flow after the merchant is approved for in-person payment acceptance. For example, after a new merchant is approved, present a full-screen modal to enable Tap to Pay on iPhone immediately. While your app isn’t required to make enabling Tap to Pay on iPhone mandatory, ensure the merchant can enable the feature promptly. This helps prevent the merchant from having to wait to enable Tap to Pay on iPhone at a critical moment (for example, right before accepting a customer payment).

For existing users, your app must provide at least one communication to let them know that Tap to Pay on iPhone is available. As a best practice, provide multiple communication channels in addition to a full-screen modal on login to encourage existing users to enable Tap to Pay on iPhone.

Requirements

The Enabling Tap to Pay on iPhone requirements apply to all apps in the public App Store.

If you distribute your app through programs such as Unlisted apps, Custom apps, or the Apple Developer Enterprise Program (ADEP), these requirements apply when users are expected to accept Terms and Conditions using an Apple ID on the iPhone.

Before you review the checklist below, confirm that your app:

Shows Tap to Pay on iPhone to eligible users at least once
Provides a clear path to accept Terms and Conditions
Gives users a way to enable Tap to Pay on iPhone outside the checkout flow
Tells non-admin users to contact an admin when they are not authorized to enable the feature

Req	Status	Description
3.1	Required	Your app implements a highly visible, easily discoverable communication channel for Tap to Pay on iPhone.
3.2	Recommended	Your app implements a full-screen modal for Tap to Pay on iPhone.
3.3	Required	Your app displays Tap to Pay communications to all eligible users at least once.
3.4	Required	Your app clearly shows how to enable Tap to Pay on iPhone at the end of every new merchant onboarding flow.
3.5	Required	Your app must support Tap to Pay on iPhone. You must have a clear action to trigger acceptance of Tap to Pay on iPhone Terms and Conditions.
3.6	Required	Your app provides a way to enable Tap to Pay on iPhone outside the communications and checkout flows (for example, in your app settings).
3.7	Required	Your app must provide a trigger to enable Tap to Pay on iPhone within your checkout flow, or require Tap to Pay on iPhone enablement before the checkout flow.
3.8	Required	Tap to Pay on iPhone Terms and Conditions must be accepted only by an administrator user or another authorized party on the merchant's behalf.
3.8.1	Required	If a non-admin user attempts to enable Tap to Pay on iPhone, a message must instruct them to contact their admin.
3.8.2	Conditional	For enterprise deployments (e.g., Custom App, Unlisted App, or Apple Developer Enterprise Program), you must support accepting Terms and Conditions outside the app. Check with your PSP for implementation details.
3.9	Recommended	Once Terms and Conditions are accepted and the user has completed the Tap to Pay on iPhone tutorial, your app displays a dedicated screen prompting the user to try Tap to Pay on iPhone.
3.9.1	Required	Your app must provide a configuration progress indicator using PaymentCardReader.Event.updateProgress(_:) (or the equivalent call from your PSP SDK). This screen displays the progress of Tap to Pay on iPhone readiness as the device is configured. This screen informs the user that Tap to Pay on iPhone is not yet ready for use, both during initial setup and during typical use, while the reader is preparing.

Educating merchants

Use this section to review the education content merchants must see after Tap to Pay on iPhone is enabled.

Your app must provide merchant education as part of the in-app user experience.

Begin the merchant education after the merchant accepts the Tap to Pay on iPhone Terms and Conditions.

Merchant education must include clear instructions on how to accept payments with Tap to Pay on iPhone using contactless cards, Apple Pay, and digital wallets, as well as the payment methods accepted (e.g., Visa, Mastercard).

Use the visual assets and copy on the Marketing Guidelines page to create the merchant education experience for your app. Consider using the Merchant Education video as a simple way to provide this educational moment.

Requirements

These merchant education requirements apply to all apps in the public App Store.

If you distribute your app through programs such as Unlisted apps, Custom apps, or the Apple Developer Enterprise Program (ADEP), these requirements are strongly recommended but not required if merchant education is provided through other communications.

Your app must provide region-specific educational content. For more details, refer to Appendix C: Regional Requirements of this document.

Req	Status	Description
4.1	Required	Your app must display the education screens immediately after successfully enabling Tap to Pay on iPhone and accepting the Terms and Conditions.
4.2	Required	Your app must make merchant education screens accessible for reference in either the Settings or Help section.
4.3	Required	Your merchant education screens must align with marketing guidelines for visual assets and copy.
4.4	Required	Merchant education must demonstrate how to accept contactless cards with Tap to Pay on iPhone.
4.5	Required	Merchant education must demonstrate how to accept Apple Pay and other digital wallets with Tap to Pay on iPhone.
4.6	Conditional on Region	Merchant education must demonstrate support for PIN Entry, with an explicit mention of the accessibility options available on the PIN screen if the region you deploy to supports PIN entry. Check with the PSP SDK for this feature and see the Regional Requirements for more details.
4.7	Conditional on Region	Merchant education must demonstrate a fallback to an alternate payment method if Tap to Pay on iPhone cannot read a payment card (e.g., Payment Link) in a region that requires a Fallback Payment Method.

Checking out

Use this section to review the checkout experience Apple expects once Tap to Pay on iPhone is available to the merchant.

Ensure that Tap to Pay on iPhone is configured so the merchant can accept payments without delays.

Check with your PSP for guidelines on preparing Tap to Pay on iPhone when the user opens the app or when your app transitions to the foreground.

See Apple’s Human Interface Guidelines (HIG) and Localization strings for Tap to Pay on iPhone within Appendix C for details on how to display the Tap to Pay on iPhone button in your app. Display the "Tap to Pay on iPhone" button prominently during payment acceptance, and use the appropriate copy to indicate the number of payment methods accepted.

During checkout, make sure the Tap to Pay on iPhone action is visible, available, and followed by clear processing and outcome states.

Requirements

Req	Status	Description
5.1	Required	Users must have an obvious, prominent button to initiate a Tap to Pay payment on iPhone during checkout.
5.2	Required	The button that invokes Tap to Pay on iPhone must be in a visible location (without scrolling) for the user to select at the time of checkout. Tap to Pay on iPhone should be at the top of the list when multiple payment acceptance options are available.
5.3	Required	The button that invokes Tap to Pay on iPhone must never be altered, grayed out, or otherwise hidden based on whether the user has enabled Tap to Pay on iPhone. If the user has not yet enabled Tap to Pay on iPhone, the button will invoke that path.
5.4	Conditional	If there are multiple payment options, the button that invokes Tap to Pay on iPhone must use the proper copy for your region. Refer to Localization strings for Tap to Pay on iPhone in Appendix C for more details.
5.5	Conditional	If using iconography in the button, the symbol used must be wave.3.right.circle or wave.3.right.circle.fill from SF Symbols.
5.6	Required	When the Tap to Pay on iPhone screen closes after a successful card read, a “processing” screen must appear to indicate that the transaction is being processed.
5.7	Required	There must be clear communication of the outcome after the processing screen to the user. This would highlight to the user approved, declined, or timed-out transactions.
5.8	Required	When the transaction is processed, regardless of the outcome (approved or declined), it must be possible to send a digital receipt to the customer confidentially. For example, the digital receipt may be sent by SMS, email, QR code, or using Activity views.
5.9	Conditional on Region	Comply with regional requirements for the deployment location. See Appendix C, "Regional Requirements," for more details.
5.10	Conditional	If the user is not authorized to accept Tap to Pay on iPhone Terms and Conditions, display a message telling them to contact an admin to enable Tap to Pay on iPhone.