In-App Purchases for Converted Web Apps: Store Rules Explained

In-app purchases and subscriptions for converted web apps: when Apple and Google require their billing, exemptions and entitlement sync.

Short answer

If your converted web app sells digital content, features or subscriptions used inside the app, Apple and Google generally require their own in-app purchase systems, while physical goods and real-world services can keep your existing web checkout. The technical challenge is syncing store purchases with the entitlements your web backend already manages.

On this page
  1. The rule that surprises web teams
  2. What needs in-app purchase and what does not
  3. Three ways to handle payments in a converted app
  4. Building option B with a web app
  5. Pitfalls that cause rejections or revenue loss
  6. Product setup and review
  7. A decision path
  8. FAQ
  9. Tools from the jocapps ecosystem

The rule that surprises web teams

Most web apps already take payments, usually through Stripe, Paddle or a similar provider. Wrap that web app as an iOS or Android app and the checkout keeps working technically. Whether it is allowed is another question.

Apple's App Review Guideline 3.1.1 states that unlocking features or functionality within an app, including subscriptions, premium content and in-game currency, must use in-app purchase. Google Play's payments policy has a comparable requirement for digital goods and services. Both stores take a commission on these transactions, with reduced rates for certain cases such as smaller developers or long-running subscriptions.

Rules have also been changing. Regulation in the EU, court decisions in the United States and arrangements in other regions have opened alternatives such as external purchase links or alternative billing in some storefronts, each with its own conditions. Always check the current guidelines for the regions you publish in.

What needs in-app purchase and what does not

What you sellTypical store treatmentExample
Subscriptions unlocking app featuresIn-app purchase requiredPro plan of an AI writing tool
Credits or tokens used in the appIn-app purchase requiredAI image generation credits
Digital content consumed in the appIn-app purchase requiredCourses, premium articles
Physical goodsYour own payment allowedOnline shop, food ordering
Real-world servicesYour own payment allowedBookings, tickets, ride or cleaning services
B2B software bought by organisationsOften handled outside the app; check the specific rulesCompany licences sold via sales contract
Reader apps (content bought elsewhere)No in-app purchase needed, limited external link options under specific programmesMedia, music, document libraries

The grey zones are B2B and person-to-person services. If your customers are companies that buy licences through contracts and your app simply lets their employees log in, many apps operate without in-app purchase and without any purchase option in the app. Describe this clearly in your review notes.

Three ways to handle payments in a converted app

Option A: no purchases in the app

The app is for existing customers who subscribe on your website. The app contains no purchase buttons, pricing pages or links to them on iOS. This is the simplest route and fits B2B and many reader-type apps, but it limits conversion inside the app and you must hide pricing and checkout elements when the web app runs inside the shell.

Option B: in-app purchase alongside web checkout

The app offers the same plans through the store's billing, while the website keeps Stripe. Users can buy either way, and your backend grants the same entitlement regardless of the source. This is the most common setup for consumer and prosumer AI apps.

Option C: physical goods or services only

If you only sell physical products or real-world services, keep your existing checkout. Make sure the app does not also sell digital add-ons, or those need in-app purchase.

Building option B with a web app

The challenge is that the purchase happens natively, but your business logic lives in the web app and its backend. A robust flow:

  1. The web app shows plans and, when running inside the app, calls the native layer to start a purchase for a specific product ID instead of opening Stripe.
  2. The native shell runs the StoreKit (iOS) or Google Play Billing (Android) purchase.
  3. The receipt or purchase token is sent to your backend, which validates it with Apple or Google server-side.
  4. Your backend grants the entitlement on the user's account, the same field that Stripe purchases set.
  5. Server notifications from Apple and Google (renewals, cancellations, refunds) update the entitlement over time.

WebViewGold includes in-app purchase support in its iOS and Android templates, exposing purchases to your web app through a JavaScript interface, so your existing web code can trigger them without a native rewrite. For the server side, you can validate receipts yourself or use a subscription management service that normalises Apple, Google and Stripe events into one entitlement model.

Pitfalls that cause rejections or revenue loss

  • Stripe checkout visible in the iOS app for digital features. Detect the app environment and hide it.
  • Links or text pointing to cheaper web prices in regions where this is not permitted.
  • No restore purchases button. Apple expects users to be able to restore previous purchases.
  • Entitlements only stored on the device. If the user logs in on the web, they must see their plan. Store entitlements on the server, linked to the user account.
  • Ignoring refunds and cancellations. Without processing server notifications, users keep access after refunds.
  • Different product names and prices across stores and web without clear communication, leading to support tickets.
  • Account deletion while a subscription is active. Tell users how to cancel the store subscription, since deleting the account does not cancel it.

Product setup and review

Create products in App Store Connect and Play Console before you submit, with clear names, descriptions and a review screenshot for each. Apple reviews in-app purchases together with the app version, and missing metadata delays approval. Test purchases with sandbox accounts on iOS and licence testers on Android, through TestFlight and internal testing tracks; see TestFlight and Play Console internal testing.

appsubmitter.io sets up products, pricing, subscription groups and the related review information in your developer accounts and handles rejections that cite payment guidelines, which are among the more nuanced ones to argue.

A decision path

  1. Do you sell anything digital that is used inside the app? If no, keep your checkout (option C) or no purchases in the app (option A).
  2. Are your buyers organisations under contract? Consider option A and document it.
  3. Do individuals subscribe to unlock features? Plan option B from the start, budget for store commission in your pricing, and use a shell such as WebViewGold that already bridges native purchases to your web code.

Related: converting a web app into iOS and Android apps, Google Play rejection reasons for web apps and Apple Guideline 4.2 for web-based apps.

FAQ

Can I use Stripe inside my 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 some regional exceptions under specific conditions.

Do I have to offer the same prices in the app and on the web?

No, prices can differ. Many companies price store purchases higher to offset commission, but check current rules on telling users about cheaper options elsewhere.

What if users already subscribed on my website?

They can log in and use their subscription in the app. Your backend grants access based on the account, regardless of where the purchase happened.

Does a converted web app support subscriptions?

Yes. With a native shell that supports in-app purchase and a backend that validates receipts and tracks renewals, subscriptions work as in a fully native app.

Tools from the jocapps ecosystem

Want this done right, and fast?

Talk to our AI Code Engineers and AI architects. In a free 30-minute call we look at your idea, prototype or roadmap and tell you honestly what it takes to ship it.

24/7 call support in English and German.

Free call

Free intro call

Tell us which task an AI agent should take responsibility for. We show how our platform, AI Code Engineers and operations plug into your stack.

  • 30 minutes, no obligation
  • Honest feasibility check
  • Concrete next step
Rather talk now? 24/7 call support in English and German+49 761 519 751 50