Hey there, let's break down exactly how to resolve this rejection—you're not alone with this one, it's a super common issue when apps use non-Apple payment methods for digital subscriptions.

First, let's clarify the root problem: Apple requires that all digital subscription features (or any paid digital content) must be purchased via their In-App Purchase (IAP) system. Using credit card payments directly (or any other non-IAP mechanism) violates this rule, which is why your app got flagged.

Here's a step-by-step plan to get your app approved:

1. Fully Remove Non-Compliant Payment Methods #

• Scrub your app clean: Delete every piece of code, button, text, or UI that lets users pay via credit card (or any other non-IAP method) for subscriptions. Don't overlook hidden spots like settings menus, help screens, or in-app notifications—reviewers will check every corner.
• Remove external references: If your app links to a website where users can pay directly, take those links out immediately. Even mentioning alternative payment options in your app's copy is a no-go.

2. Implement Apple In-App Purchase for Subscriptions #

• Set up subscriptions in App Store Connect: Log into your App Store Connect account, create subscription tiers (monthly, yearly, etc.) that match your original offering, and configure pricing, renewal terms, and localized descriptions correctly.
• Integrate StoreKit (or a wrapper): Use Apple's official StoreKit framework to build the purchase flow. If you want to simplify things, tools like RevenueCat can handle a lot of the heavy lifting (like receipt validation and subscription status tracking).
  • Make sure your paywall displays all required Apple disclosures: things like "Auto-renews until canceled" and clear pricing for each tier.
  • Test rigorously with Sandbox testers in App Store Connect to ensure purchases, renewals, and restores work flawlessly.

3. Update Your App's Metadata and Review Notes #

• Polish your App Store listing: Check your app description, screenshots, and promotional text—remove any mention of non-IAP payments. All references to subscriptions should align with Apple's IAP language.
• Add clear review notes: When resubmitting, write a detailed note in the App Review section explaining that you've removed all non-compliant payment systems and fully implemented Apple IAP for your subscription features. This helps reviewers quickly verify your fixes.

4. Handle Existing Subscribers (If You Have Them) #

• If you already have users who signed up via credit card, you need a compliant way to migrate them to IAP:
  • Offer a grace period where existing users can keep their subscription while you guide them to switch to Apple's IAP system.
  • Avoid any workarounds like redirecting them to a website—stick to in-app prompts that lead directly to IAP. Apple has guidelines for subscriber migration, so make sure to follow those closely.

5. Resubmit and Stay Patient #

• Once all fixes are done, resubmit your app. If you get rejected again, read the new rejection message carefully—sometimes reviewers miss a small detail. Address any remaining issues and resubmit promptly.

Quick reminder: Apple enforces this rule to ensure a secure, consistent payment experience for users, and to maintain their standard revenue share (30% for most apps, 15% for qualifying small businesses). Sticking to IAP not only gets you approved but also simplifies long-term compliance.

内容的提问来源于stack exchange，提问作者Dileep Kumar