Apple Pay App Review checklist
Apple Pay is a checkout tool, not a way around StoreKit. Review readiness starts by classifying what is being sold and whether Apple Pay is the right payment route.
Use Apple Pay for eligible physical goods, real-world services, donations, or other supported payment scenarios, and keep digital content that must use IAP inside StoreKit. Apple PassKit documentation covers Apple Pay setup and payment requests. AppReviewReady interpretation: build a payment-route decision record before enabling the button.
Classify what the user is buying
Write whether the payment covers physical goods, real-world service, donation, ride, food, ticket, subscription outside the app, digital content consumed in the app, or mixed value. That answer determines whether Apple Pay, IAP, or another route is appropriate.
If a cart mixes digital and physical items, separate the payment paths before review. A single Apple Pay button that includes unlockable digital content can create obvious review friction.
Verify merchant and sheet setup
- Merchant identifier, entitlements, certificate, and payment processor should match production configuration.
- The Apple Pay button should appear only when Apple Pay is available for the current device and region.
- Line items should clearly describe subtotal, tax, shipping, discounts, and total.
- Shipping, pickup, billing, and contact requirements should match the actual order.
- Failed authorization, canceled sheet, and processor errors need useful recovery states.
Keep checkout copy aligned with fulfillment
The payment sheet is only one part of the checkout promise. Product pages, receipts, support pages, refund language, delivery estimates, and privacy disclosures should all describe the same transaction.
AppReviewReady interpretation: do not use Apple Pay branding to make a weak or unsupported purchase look safer. The app still owns fulfillment, support, and truthful item descriptions.
Run Apple Pay review tests
- Test supported and unsupported devices, regions, cards, shipping addresses, and canceled payments.
- Confirm no Apple Pay button appears for StoreKit-only digital goods.
- Verify receipts, order history, support contact, refund route, and account deletion behavior.
- Test fraud, duplicate tap, network timeout, and processor decline handling.
- Check privacy labels for payment contact fields, shipping details, and order analytics.
Prepare Apple Pay review evidence
If the app also sells digital goods, explicitly separate those paths in the review packet. The goal is to prevent payment-route confusion before it becomes a rejection.
Keep Apple Pay checkout separate from account-credit systems unless the purchased value is clearly tied to eligible real-world goods or services. Ambiguous stored value can create both review and support risk.
For marketplaces, document who is merchant of record and who fulfills the order. Apple Pay sheet copy, receipts, and support pages should all name the same responsible party.
Retest checkout after tax, shipping, or processor configuration changes.
Apple Pay review path: Goods/service type: [physical, real-world service] Merchant ID: [identifier] How to reach checkout: [steps] Test payment state: [sandbox/production-safe] Fulfillment promise: [delivery/pickup] Failure behavior: [cancel/decline] Digital goods excluded: [yes/no]
Primary references checked for this guide
Policy statements above are grounded in the linked Apple documentation. Operational recommendations are AppReviewReady's interpretation and should be tested against your app and the current guideline text.
Check Apple Pay readiness
Review payment route, merchant setup, sheet behavior, and support states before submission.
Open the tool