Skip to main content

In-App Purchases for AI-Built Apps: Store Rules Explained

By the OnlineAppCreator editorial team4 min read

Short answer

If your AI-built app sells digital content, features or subscriptions that are used inside the app, Apple and Google generally require their own in-app purchase systems, so a Stripe checkout from your web app is not enough in the store version. Physical goods and real-world services can keep using Stripe or other payment providers. The practical solution is native in-app purchases in the app shell, synced with the same entitlements your web app already uses.

On this page
  1. The core rule: digital versus physical
  2. Exceptions and regional changes
  3. Comparing the main payment setups
  4. Implementing in-app purchases in a web-based app
  5. Pitfalls that cause rejections and support tickets
  6. Where to go from here

Payments are where many AI-built apps hit a wall in review. A Lovable or Base44 app typically integrates Stripe for subscriptions, which works perfectly on the web. Package that same app for iOS and Android, and the reviewer may reject it because digital purchases inside store apps must use the store's billing. This article explains which rules apply, how they differ between Apple and Google, and how to implement in-app purchases in a web-based app without rebuilding your business logic.

The core rule: digital versus physical

Apple's Guideline 3.1.1 requires in-app purchase for unlocking features or functionality within the app, including subscriptions, premium content, digital currencies and upgrades. Google Play's Payments policy similarly requires Google Play Billing for digital goods and services sold within the app. Both stores exclude physical goods and services that are consumed outside the app. A marketplace for furniture, a booking app for hair appointments or a food ordering app can use Stripe, PayPal or any other provider.

The distinction is not always obvious. Consulting sessions delivered by a real person over video, for example, are treated differently from AI-generated reports delivered in the app. If an AI feature in your app produces the value, assume it counts as digital. When in doubt, read the current guidelines and describe your model in the review notes.

Exceptions and regional changes

There are several exceptions. "Reader" apps that provide previously purchased content such as magazines, music or video may let users access what they bought elsewhere, and under specific programs may link to an external website for account management. Enterprise services sold to organizations, not individual consumers, can also be treated differently. In addition, the rules on linking to external payment options have changed in recent years in some regions, including the EU under the Digital Markets Act and the United States after court decisions. These rules differ by storefront, come with their own conditions and are still evolving, so check Apple's and Google's current documentation for your target markets rather than relying on older articles.

What has not changed is the baseline: an app that shows a "Subscribe with card" button for in-app digital features, without store billing, is very likely to be rejected in most storefronts.

Comparing the main payment setups

SetupAllowed for digital features in store appsTypical use
Stripe checkout inside the appGenerally no, except where regional rules allow itPhysical goods, real-world services, web version
Apple in-app purchase and Google Play BillingYesSubscriptions, premium features, credits
Purchase on web, use in app (no in-app buying)Only for specific cases such as reader apps or certain business appsContent services, B2B tools
Both: store billing in app, Stripe on webYes, if entitlements are syncedMost consumer SaaS apps

Implementing in-app purchases in a web-based app

The usual pattern keeps your existing entitlement model and adds store billing as an additional payment source. Your database already knows whether a user is "pro". You add a second way to become pro: a verified store purchase.

  1. Create the products and subscription groups in App Store Connect and the Play Console, with identical product logic on both platforms.
  2. Enable in-app purchases in your native shell; a template like WebViewGold supports them out of the box and exposes them to your web app through a JavaScript bridge.
  3. In your Lovable, Base44 or Bolt app, detect whether it runs inside the store app and show the native purchase button instead of the Stripe checkout.
  4. Send the purchase receipt or token to a server-side function that validates it with Apple or Google.
  5. Set the user's entitlement in your database after successful validation, exactly as your Stripe webhook does today.
  6. Subscribe to the stores' server notifications to handle renewals, cancellations and refunds.
  7. Add a "Restore purchases" option, which Apple expects for non-consumable products and subscriptions.

Some teams use a subscription management service to unify Apple, Google and Stripe purchases. That can reduce work, but adds a dependency; evaluate it based on the number of products and platforms you sell on.

Pitfalls that cause rejections and support tickets

Showing prices or "cheaper on our website" messages inside the iOS app is prohibited in most storefronts, as is directing users to external purchase pages without an applicable entitlement. Make sure every paywall in the app uses store billing and that subscription terms, price, period and renewal conditions are displayed clearly before purchase, with links to your terms and privacy policy. Reviewers will test purchases in the sandbox, so provide a demo account that is not already subscribed.

On the operational side, users who subscribe on the web and on iOS can end up paying twice. Check entitlements before showing a paywall and explain in your account screen where the subscription is managed. Refunds for store purchases are handled by Apple and Google, not by you, which surprises support teams used to Stripe.

Where to go from here

In-app purchases touch your product, your backend and your store listings at once, which makes them a common source of review loops. For broader preparation, see our list of rejection reasons for AI-built apps and the store listing checklist, which covers subscription disclosures. If you want help with product setup, sandbox testing and review communication, AppSubmitter handles the publishing process until the app is live. And if monetization is part of a larger question about turning the app into a business, our company building team works on exactly that.

Frequently asked questions

Can I use Stripe in my Lovable iOS app?

For physical goods and real-world services, yes. For digital features, content or subscriptions used in the app, Apple generally requires in-app purchase, with regional exceptions that have their own conditions.

Do I need to remove Stripe from my web app?

No. Your web app can keep Stripe. You add store billing in the native apps and sync both into the same entitlement in your database.

Who handles refunds for in-app purchases?

Apple and Google handle refunds for purchases made through their billing systems. Your backend should listen to their server notifications to revoke access when a refund occurs.

Is a restore purchases button required?

Apple expects apps with non-consumable purchases or subscriptions to offer a way to restore them, for example after reinstalling the app or switching devices.

Want this done right, the first time?

OnlineAppCreator takes products from idea to operation. Tell us where you stand and get a concrete plan in a free 15-minute call.