In-App Purchases and Subscriptions for a Lovable App

By jocapps5 min read

Short answer: A Lovable app that sells digital features or content inside its iOS and Android apps generally has to use Apple In-App Purchase and Google Play Billing there, while Stripe can remain the checkout on the web. The clean setup is a single entitlement table in Supabase that every payment source updates through verified server-side events, so users get the same access wherever they paid.

On this page

The rule that shapes everything

Apple's Guideline 3.1.1 and Google Play's payments policy require that digital goods and services consumed in the app, such as premium features, subscriptions, credits or content, are sold through the store's own billing system. Physical goods and real-world services, such as a delivered product or a booked appointment, can use Stripe or other processors. Rules on linking to external purchases vary by region and have changed in recent years, so check the current terms for the countries you serve.

For a typical Lovable SaaS with Stripe subscriptions, this means the web keeps Stripe, while the iOS and Android apps need store billing for the same plans, or must avoid selling inside the app where the rules allow a reader-style or account-only approach.

Choosing your monetization model per platform

Decide this before writing code, because it affects pricing, margins and the review story.

  • Store billing in apps, Stripe on web: the most common setup. Users can subscribe anywhere and the app unlocks features accordingly.
  • Web-only purchase: the app offers login for existing customers but no purchase. Suitable for B2B tools sold through contracts; check the store rules carefully for your category.
  • Store billing everywhere on mobile: simplest for consumer apps that are mostly mobile, with the store handling taxes, refunds and family sharing.
  • Consumables: credits or tokens, for example for AI generations, sold as consumable in-app purchases and recorded in your own ledger.

Architecture: one source of truth for access

The most important design decision is that your Lovable app never asks "did this user pay through Stripe?" or "did they pay through Apple?". It asks "does this user have the pro entitlement?". A Supabase table such as entitlements holds user ID, entitlement name, source, expiry date and status. Row Level Security lets users read only their own entitlements; only server-side code can write them.

Three writers update that table: a Stripe webhook handler for web purchases, a handler for Apple App Store Server Notifications, and one for Google Play Real-time Developer Notifications. Each verifies the event server-side before granting access. Subscription management services such as RevenueCat can consolidate the store side and send one unified webhook, which saves considerable work on receipt validation and renewals.

Need a hand? WebViewGold helps with exactly this. Book a call for free and get a clear plan in 15 to 30 minutes.

Implementation steps with a native wrapper

WebViewGold's native bridge exposes 40+ native APIs to your web code, so the purchase itself runs natively while the Lovable front end stays the place where you build and update the paywall.

  1. Create the products and subscription groups in App Store Connect and the Play Console with matching identifiers and price tiers.
  2. Sign the paid applications agreements and complete tax and banking information in both stores; products stay unavailable until this is done.
  3. Detect in the web app whether it runs in the iOS app, the Android app or a browser, and show the matching purchase button.
  4. Call the wrapper's purchase function from the paywall, then send the resulting transaction information to a Supabase edge function.
  5. Verify the transaction with Apple or Google, or via your subscription service, and write the entitlement.
  6. Subscribe to server notifications for renewals, cancellations, refunds and billing retries so access stays correct over time.
  7. Add a "Restore purchases" button, which Apple expects for non-consumable products and subscriptions.
  8. Test with sandbox testers on iOS and license testers on Android, including renewals and cancellations.

Review requirements that trip up subscription apps

Store reviewers check paywalls carefully. The subscription screen must show the price, billing period, what the user gets and how to cancel, along with links to your terms and privacy policy. Free trials must state clearly what happens when they end. The in-app purchase products need to be submitted with the app version that first uses them, including a review screenshot of the purchase screen.

Avoid showing Stripe checkout or web pricing inside the iOS app unless the rules for your region explicitly permit it. A common mistake is a Lovable pricing page that the wrapper loads unchanged, complete with "Pay with card" buttons. Hide or replace those elements when the app detects the native shell. appsubmitter.io reviews paywalls against current store rules before submission and handles reviewer questions about payments if they come up.

Pricing and margin considerations

Store commissions reduce your margin on mobile purchases. Both Apple and Google offer reduced rates for small businesses below a revenue threshold and for subscriptions after the first year, under conditions that you should verify in their current programs. Some companies price mobile plans slightly higher to offset commission; others keep prices identical for simplicity and accept the margin difference as a customer acquisition cost.

Whatever you choose, keep plan names and features identical across platforms. Users who switch from phone to laptop should see the same entitlement and the same plan, regardless of where they paid. WebViewGold handles the native purchase layer, and a free call is a quick way to map out the rest for your specific product.

Frequently asked questions

Can I use Stripe for subscriptions in my Lovable iOS app?

For digital features and content used in the app, Apple generally requires In-App Purchase. Stripe is allowed for physical goods and real-world services. Some regions now permit external purchase links under specific conditions and fees, so check Apple's current guidelines for your storefronts before relying on that option.

Will a user who subscribed on the web have access in the app?

Yes, if you design entitlements centrally. When access is stored per user in Supabase rather than per payment source, a web subscriber logs into the app and gets the same features. Make sure the app does not push them to buy again and that cancellation instructions point to where they originally paid.

Do I need RevenueCat for a Lovable app?

Not strictly, but it helps. You can verify Apple and Google transactions yourself in Supabase edge functions, which requires handling receipts, renewals, grace periods and refunds for both stores. A subscription service handles that complexity and sends unified events, which many small teams find worth the cost.

Also useful for this

Talk to an AI Code Engineer, free of charge

Tell us where you are and where you want to go. In a short call we map out the fastest path, whether that is a workshop, a launch in the App Store and Google Play or a full AI-native product.

No obligation. English or German. Run by jocapps, ISO 27001 and ISO 9001 certified. Prefer the phone? 24/7 call support: +49 761 519 751 50

Book a call for free

Related guides

Book a call for free