StoreKit/IAP Integration for Apple and Google to sell digital and have subscriptions. You don’t need it. Use stripe!!!! This is HUGE.

payment + review flow

1. Legal background (Epic v. Apple)

• Case: Epic Games, Inc. v. Apple Inc., Case No. 4:20‑cv‑05640‑YGR (N.D. Cal.).

• Result: Apple cannot block or punish apps for sending users to an external website (like Stripe) to pay instead of using Apple’s in‑app purchase system, for US App Store users.

• Apps are allowed to: • Show prices and “subscription” language inside the app. • Redirect users to a web page for payment (e.g., Stripe Checkout). • Return users to the app afterwards.

2. How this works with Base44 + Stripe

• The app itself is built in Base44 (web app wrapped for iOS/Android).

• Inside the app you: • Show subscription options and pricing. • When the user taps “Subscribe,” show a clear message like: “You are leaving the app to complete payment on our secure website (Stripe).” • Then redirect them to a Stripe Checkout URL in the browser / in‑app web view. • After payment, Stripe redirects back to a URL or deep link that re‑opens the app with the user marked as subscribed.

• Because the payment is processed on the web via Stripe, Apple and Google do NOT take the 15–30% cut; you just pay normal Stripe fees.

3. What we do in practice

• Build everything in Base44 (RealShield AI app).

• Integrate Stripe for subscriptions.

• Implement a “leaving the app to pay on the web via Stripe” confirmation box before redirect.

• Submit the wrapped app to: • Google Play (AAB file). • Apple App Store (IPA file).

4. If Apple rejects the app

• Sometimes reviewers still apply old rules and say you “must use in‑app purchases.”

• In that case, we DO NOT change the payment flow. Instead, we appeal.

• In the appeal, we: • Cite Epic Games, Inc. v. Apple Inc., Case No. 4:20‑cv‑05640‑YGR. • Explain that: – The app uses a clearly disclosed external web payment (Stripe). – Users see a neutral notice that they are leaving the app to pay on the web. – No Apple IAP is being used or hidden; the flow is consistent with the court decision and Apple’s updated US rules.

• Typical pattern:

  1. Submit with Stripe + external redirect notice.

  2. If Apple approves: done.

  3. If Apple rejects on payments: file an appeal referencing the Epic case and clarify that this is an allowed external payment flow.

Short version: Epic v. Apple opened the door for external web payments (Stripe) in US apps. A Base44 app can show prices and subscriptions, then send users to Stripe on the web and back. If Apple says “no,” you appeal and point to the Epic ruling instead of rebuilding the app or ripping Stripe out. I have also consulted with my lawyer and he confirms this. Im working out a few bugs on my app and turning into Apple and Google today. I’ll post on here what happens, if it gets approved or rejected.