App Store RejectionGuideline 4.5.6 — Apple Sites and Services — Apple Pay

Your Apple Pay Integration Is Missing Required Elements

Apple Pay is powerful but comes with strict implementation requirements. Missing disclosure language, using it for prohibited transaction types, or not following the UI guidelines will get you rejected under 4.5.6.

What Apple said

“Your app's Apple Pay implementation does not comply with the Apple Pay guidelines. We noticed that the payment sheet does not include required merchant information and the purchase confirmation page is missing required disclosure language. Please review the Apple Pay guidelines and update your implementation.”

What this actually means

Apple Pay transactions must meet specific disclosure and UI requirements — the merchant name must be clear, total amounts must be displayed, and certain prohibited uses (like for recurring payments without IAP) aren't allowed. Apple audits Apple Pay implementations carefully because they put their brand directly on the checkout flow.

What Apple needs to see

  • Clear merchant name and accurate total amount displayed on the Apple Pay payment sheet
  • Required disclosure language for the type of transaction (physical goods, services, donations) as specified in Apple Pay guidelines
  • Apple Pay used only for permitted transaction types — physical goods, services, and allowed digital goods
  • A terms of service and privacy policy accessible before purchase is completed
  1. 1Review Apple's Apple Pay Human Interface Guidelines and Identity Guidelines, then audit your implementation against each requirement
  2. 2Verify your PKPaymentRequest includes accurate merchant identifier, currency, country code, and itemized line items
  3. 3Ensure the payment summary label on the sheet clearly identifies your business — vague labels are a common rejection cause
  4. 4Add links to your terms of service and privacy policy near the Apple Pay button — yourapp.baseterms.com/terms and /privacy work well here
  5. 5Test your complete payment flow in sandbox mode with a real device, not just the simulator

While you're at it — Apple also requires these pages for every app.

Fix this rejection, then make sure you're covered on the compliance side too. Apple requires every app to link to a hosted Privacy Policy, Terms of Service, Support page, and Data Deletion page. No link means another rejection — just for a different reason.

Privacy Policy
Terms of Service
Support Page
Data Deletion Page
Generate my compliance pages — $9

Common questions

Can I use Apple Pay for in-app subscriptions?
No. Subscriptions must use Apple's In-App Purchase system, which has its own payment flow. Apple Pay is for physical goods, services, and some specific digital goods sold outside of the IAP system. Using Apple Pay to work around IAP for subscriptions will get you rejected.
My app uses Apple Pay for a marketplace — are there special requirements?
Marketplace implementations have additional requirements around displaying the actual merchant's name and ensuring the transaction description is clear. Each transaction needs to accurately represent who's receiving the payment and for what.
Do I need special entitlements for Apple Pay?
Yes. Apple Pay requires a merchant ID registered in your developer account and the Apple Pay entitlement in your app. You also need to register your domains with Apple Pay if you're doing any web-based portion of the checkout. All of this must be configured before submission.