Base44 In-App Purchases: Add Apple Subscriptions Without Rebuilding

    Quick answer

    Base44 apps can ship to the Apple App Store with real In-App Purchases — Wanilla wraps the existing Base44 web app in a native iOS shell and wires up the native framework, so nothing has to be rebuilt in Swift.

    • Apple rejects thin web wrappers under Guideline 4.2 — native In-App Purchases is what clears review.
    • Most apps are submitted to Apple within 24 hours of kickoff; review typically takes another 24–48 hours.
    • Digital subscriptions must run through Apple in-app purchase (StoreKit 2), not web-only Stripe billing.
    Wanilla bridging Base44 web apps to native iOS with In-App Purchases

    Stop losing revenue. Wrap your AI-coded Base44 project natively and deploy to the App Store in minutes.

    Read the Docs

    The Limits of Base44 for Mobile Monetization

    You built a working app in Base44. Now you want to charge for it on iOS — and you've hit the Apple wall. Apple requires native StoreKit for any digital purchase. Stripe is not allowed. Web-only paywalls get rejected at review. And building StoreKit yourself means rewriting your Base44 app as a native Swift project — defeating the whole point of building in Base44. Wanilla is the App Store launch and growth partner for Base44 founders. We wrap your existing Base44 app in a native iOS shell, wire up Apple in-app purchases and subscriptions, handle App Store Connect, and ship the build to review — usually inside 14 days. You keep editing in Base44. We handle the iOS side.

    How to Implement In-App Purchases in Base44 using Wanilla

    Wanilla adds native in-app purchase capabilities to your Base44 app by embedding StoreKit and Google Billing Library into the native wrapper. Define your products in App Store Connect, map them in Wanilla, and trigger purchases from your Base44 app with a simple JavaScript call. Receipts are validated server-side and purchase events are sent to your backend.
    Your Base44Web AppWanilla EngineInjects In-App PurchasesNative BuildApp Store ReadyExport / ConnectStoreKit · WebKit · PushiOS App Store
    How Wanilla converts your Base44 web app into a native app with In-App Purchases

    Code Integration Example

    The in-app purchase integration supports all product types: consumables for credit-based systems, non-consumables for permanent unlocks, and auto-renewable subscriptions for recurring revenue. Wanilla manages the complete lifecycle — from purchase initiation to receipt validation to renewal tracking. Family Sharing and promotional codes are supported out of the box.

    Earning under $1M/year on the App Store? You qualify for Apple's reduced 15% commission. Read our full Apple Small Business Program guide →

    How Apple IAP is added to a Base44 app, step by step

    1. Products are created in App Store Connect. Consumables, non-consumables or auto-renewing subscriptions, with pricing, free trials and introductory offers, plus the localised descriptions Apple requires before review.
    2. StoreKit 2 is wired into the native layer. Purchases, renewals, refunds and family sharing are handled natively rather than through a web checkout, which is what keeps the app clear of guideline 3.1.1.
    3. Entitlements are written back to Base44. Base44's database has no transaction table, so a small entitlements record is added and updated over the bridge whenever a purchase, renewal or cancellation happens. Your existing Base44 logic then reads one field to decide what a user can see.
    4. Restore is implemented. Apple requires a visible restore path on any app selling non-consumables or subscriptions; missing it is one of the most common rejections.
    5. Sandbox testing before submission. Every product is bought, cancelled and restored in Apple's sandbox, including the upgrade and downgrade paths, so review does not hit a dead end.

    Stripe can stay in place for your web customers. The two are reconciled through the same entitlements record, so a subscriber who signed up on the web is recognised in the app and is not asked to pay twice.

    <script src="https://cdn.wanilla.co/sdk.js"></script>\n<script>\n  Wanilla.init({ appId: "your-base44-app-id" });\n  Wanilla.iap.purchase("premium_unlock", {\n    onSuccess: (receipt) => console.log("Unlocked premium:", receipt.transactionId),\n    onError: (err) => console.error("Purchase failed:", err)\n  });\n</script>

    Related Guides

    Once you've set up In-App Purchases, you might also want to add Adapty Alternative to Base44 or add App Store Publishing to Base44.

    Working with other AI builders? See our guide on In-App Purchases for Lovable or In-App Purchases for Replit.

    Explore our full breakdown of Base44 App Integration.

    How to publish your Base44 app with In-App Purchases

    Submitted to Apple within 24 hours$2,995 managed launch + $199/month
    1. 1

      Connect your Base44 app

      Share the live URL of your Base44 app. Nothing is rebuilt — the existing build stays the source of truth.

    2. 2

      Wire up native In-App Purchases

      Wanilla wraps the app in a native iOS shell and injects real native In-App Purchases support, so the app is not a thin web wrapper under Apple Guideline 4.2.

    3. 3

      Prepare the App Store listing

      Bundle ID, App Store Connect record, privacy nutrition labels, screenshots, description and keywords are prepared for submission.

    4. 4

      Configure pricing and paywall

      Subscriptions and in-app purchases are created in App Store Connect and wired to StoreKit 2, with the paywall configured remotely so pricing changes need no new review.

    5. 5

      Submit to Apple and go live

      The build is submitted to App Review — typically within 24 hours of kickoff — and Wanilla handles any reviewer feedback until the app is approved.

    Base44 + Wanilla vs. Custom Native Development

    FeatureBase44 Web AppCustom React NativeBase44 + Wanilla
    Development TimeMinutes (AI Generated)Weeks / MonthsMinutes
    App Store Ready No Yes Yes
    In-App Purchases Support❌ Web only (Stripe)✅ Native IAP✅ Native IAP
    Developer CostLowVery HighLow (SaaS)

    Frequently Asked Questions

    How long does it take to add Apple in-app purchases to a Base44 app?▾
    Most Base44 apps go from web-only to live on the App Store with subscriptions in 10–14 days. We handle the native wrapper, StoreKit integration, App Store Connect setup, and submission to Apple review.
    Do I have to rebuild my Base44 app in Swift?▾
    No. Your Base44 app stays in Base44. Wanilla wraps it in a native iOS shell that exposes Apple's StoreKit APIs to your existing web code, so subscriptions, restore purchases, and receipts all work natively.
    Is Wanilla a RevenueCat alternative for Base44 builders?▾
    Yes. Where RevenueCat is a self-serve SDK you wire up yourself, Wanilla is a managed launch partner: we configure StoreKit products, server receipt validation, and the subscription lifecycle for you, then keep them running.
    What does Apple take from in-app purchases?▾
    15% in year one for every developer under the Apple Small Business Program (under $1M/year). We enrol you in the program during onboarding so you keep 85% from day one.
    Can I sell physical goods through in-app purchases?▾
    No. Apple restricts in-app purchases to digital goods and services. For physical goods, keep Stripe on web and use IAP only for digital subscriptions, credits, or premium features.
    Will users be able to restore purchases on a new device?▾
    Yes. We wire up native restore-purchases flows for every non-consumable and subscription product, so users sign in on any iPhone and get their entitlements back instantly.

    Official Resource

    Book a Free Launch Review

    Sign up and connect your repository today. Go from web app to the App Store in under 24 hours.

    Or see the managed launch offer — $2,995 + $199/month
    Samuel Olsson, Co-founder of Wanilla

    Samuel Olsson

    Co-founder, Wanilla

    Connect on LinkedIn