Apple In-App Purchases for Replit Apps

The Limits of Replit for Mobile Monetization

Replit projects usually charge through Stripe on the server. Apple does not allow that for digital goods bought inside an iOS app: the purchase has to go through StoreKit, and the receipt has to be validated against Apple rather than trusted from a Stripe webhook.

You shipped a real product in Replit. The next step — taking payments inside an iOS app — is where most AI-built apps stall. Apple requires StoreKit 2 for any digital goods sold in-app, and that means:

A real native binary. Stripe, Lemon Squeezy, and Paddle web flows are rejected under App Store Review Guideline 3.1.1 for digital goods.
Apple Developer + App Store Connect plumbing. Products, pricing, tax categories, sandbox testers, receipt validation.
Server-side verification. Without it, jailbroken devices and refund abuse eat your margin.

An SDK like RevenueCat assumes you've already cleared all of that. You haven't.

How to Implement In-App Purchases in Replit using Wanilla

Wanilla runs StoreKit 2 in the native layer and posts Apple-verified receipts to your existing Replit endpoints, so the entitlement logic you already wrote keeps working — with Apple as the payment source of truth and Stripe still handling your web customers.

Wanilla is a managed App Store launch and growth partner — not an SDK. We take your Replit app, wrap it in a native iOS binary, wire StoreKit 2 IAPs into your existing backend, and ship to the App Store for you.

What you get instead of installing an IAP SDK:

Native StoreKit 2 subscriptions, one-off purchases, and consumables — configured on your Apple Developer account.
Server-side receipt validation against Apple's App Store Server API, with entitlement state written back to your Replit backend.
Apple Small Business Program enrolment (15% commission instead of 30%) if you qualify.
Paywall design, copy, and pricing iteration handled by our team.
Apple Review submission end-to-end, including responses to reviewer pushback.

Already evaluating SDKs? See the RevenueCat alternative for Replit and Adapty alternative for Replit breakdowns.

How Wanilla converts your Replit web app into a native app with In-App Purchases

Code Integration Example

Wanilla vs RevenueCat vs DIY StoreKit

	Wanilla	RevenueCat	DIY StoreKit
Native binary	We build it	You build it	You build it
StoreKit setup	Managed	SDK install	You write Swift
App Store submission	We submit	You handle	You handle
Receipt validation	Server-side, done	SDK wrapper	You write it
Pricing model	Flat-fee launch	% of revenue	Your time
Best for	Pre-PMF Replit founders	Native teams at scale	Engineers who enjoy pain

Enrol in the Apple Small Business Program before your first payout to cut commission from 30% to 15%.

// Server-side StoreKit 2 receipt verification — runs in your Replit backend
// Wanilla posts the signed JWS transaction here after the user completes a purchase.

export async function verifyPurchase(req) {
  const { signedTransaction, userId } = await req.json();

  const res = await fetch("https://api.wanilla.co/v1/storekit/verify", {
    method: "POST",
    headers: { "Content-Type": "application/json", "Authorization": `Bearer ${WANILLA_KEY}` },
    body: JSON.stringify({ signedTransaction })
  });

  const { valid, productId, expiresAt } = await res.json();
  if (!valid) return new Response("Invalid receipt", { status: 400 });

  await db.entitlements.upsert({ userId, productId, expiresAt });
  return new Response("OK");
}

Related Guides

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

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

Explore our full breakdown of Replit App Integration.

How to publish your Replit app with In-App Purchases

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

1
Connect your Replit app
Share the live URL of your Replit app. Nothing is rebuilt — the existing build stays the source of truth.
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
Prepare the App Store listing
Bundle ID, App Store Connect record, privacy nutrition labels, screenshots, description and keywords are prepared for submission.
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
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.

Replit + Wanilla vs. Custom Native Development

Feature	Replit Web App	Custom React Native	Replit + Wanilla
Development Time	Minutes (AI Generated)	Weeks / Months	Minutes
App Store Ready	No	Yes	Yes
In-App Purchases Support	❌ Web only (Stripe)	✅ Native IAP	✅ Native IAP
Developer Cost	Low	Very High	Low (SaaS)

Frequently Asked Questions

Will Apple reject my Replit app for using Stripe instead of IAP?▾

For digital goods consumed inside the app, yes — Guideline 3.1.1 requires StoreKit. Wanilla wires StoreKit 2 in for you so the submission passes the first time.

Do I still need RevenueCat or Adapty?▾

No, not at launch. Wanilla replaces them end-to-end for early-stage Replit apps. You can layer either on later for experimentation without losing customers — see the <a href="/alternatives/replit/revenuecat-alternative/">RevenueCat alternative</a> breakdown.

How long does an IAP launch take?▾

10–14 days from kickoff to live on the App Store, including Apple Review. Most of the timeline is review queue, not engineering.

Official Resource

Replit Documentation — Official Replit developer documentation

Book a Free Launch Review

Or see the managed launch offer — $2,995 + $199/month

Samuel Olsson

Co-founder, Wanilla

Connect on LinkedIn