App Store
Rejected under Guideline 3.1.1 for Stripe payments: selling subscriptions in a wrapped web app
If your iPhone app unlocks digital features or a subscription, Guideline 3.1.1 says it must use Apple's in-app purchase, and a Stripe checkout inside the app is not allowed unless you hold a region-specific entitlement (for example Apple's alternative payment terms in the EU). The United States storefront lets you add a button or link to your web checkout; elsewhere that needs a region-specific entitlement. Physical goods are the opposite case: they must not use in-app purchase. Guideline text below is quoted from the version last updated on 2026-10-16.
What you are seeing
The rejection arrives on the App Review page of your app in App Store Connect and cites Guideline 3.1.1 (In-App Purchase), sometimes together with 3.1.1(a) (Link to Other Purchase Methods) or 3.1.3 (Other Purchase Methods). The wording depends on what the reviewer saw, so read the full message, including any screenshot attached to it. Typical things a reviewer finds in a wrapped web app:
- An "Upgrade" or "Go Pro" button that opens a Stripe Checkout page or a Stripe payment form.
- The website's pricing page, reachable from the app's menu or settings.
- Premium features that unlock because the account paid on the website, with no way to buy them in the app.
- Text such as "cheaper on our website" or "subscribe at example.com".
None of this is a bug in the usual sense. The web app was built to sell on the web, and the wrapper brought the whole sales flow into the iPhone app unchanged.
How to check it yourself
Work through these on your own project before you change anything. They tell you which rule applies to you and how much of the app is affected.
1. Decide what you are actually selling
Guideline 3.1 treats different kinds of purchases very differently. Find your case:
- Digital features, content or a subscription used in the app (AI credits, premium tools, unlimited projects, courses): 3.1.1 applies and in-app purchase is required.
- Physical goods, or services used outside the app (a delivered product, a booked repair, a ride): 3.1.3(e) says you must use payment methods other than in-app purchase, such as Apple Pay or card entry. Stripe is fine here.
- Real-time services between two people (tutoring, a medical consultation, a fitness session): 3.1.3(d) allows other payment methods. One-to-few and one-to-many real-time services must use in-app purchase.
- Software sold only to organisations for their employees or students: 3.1.3(c) lets enterprise users access what was bought outside the app. Consumer, single-user and family sales must use in-app purchase.
- Magazines, newspapers, books, audio, music and video: the "reader" rules in 3.1.3(a).
Most apps built with AI tools fall in the first group. If yours is in another group, the rejection may be a misunderstanding, and you can explain the case in your reply to App Review.
2. Find every place the app takes money
Open the code your AI tool produced (for Lovable, the GitHub repository it syncs to) and search it from a terminal in the project folder:
grep -rniE "stripe|checkout|customer-portal|billing|upgrade|pricing|subscribe" src supabase/functions \
--include=*.ts --include=*.tsx
ls supabase/functionssupabase/functions from the command if your project has no such folder. Every match in a screen the iPhone app shows is a place a reviewer can find.Lovable's own Stripe integration, for example, runs the payment through backend functions, opens Stripe Checkout in a new tab and, by default, checks subscription status directly with Stripe (Lovable docs: Stripe). In a wrapped app that means the iPhone app sells and unlocks through Stripe unless you change it.
3. Find where "paid" is stored
In the Supabase dashboard open SQL Editor and run these read-only queries. They list columns and database functions that look like subscription state, so you know what decides whether a user is paying:
select table_name, column_name, data_type
from information_schema.columns
where table_schema = 'public'
and column_name ilike any (array['%stripe%', '%subscri%', '%premium%', '%plan%', '%tier%'])
order by table_name, column_name;
select p.proname as function_name
from pg_proc p
join pg_namespace n on n.oid = p.pronamespace
where n.nspname = 'public'
and p.prokind in ('f', 'p')
and pg_get_functiondef(p.oid) ilike '%subscri%';4. Walk through the app as the reviewer did
- Install the build on an iPhone (TestFlight is fine) and sign in with a free account.
- Tap every button that mentions price, upgrade, plans or limits. Write down what opens: a Stripe page inside the app, a browser sheet, your website, or nothing.
- Look for text that mentions buying elsewhere or a lower web price.
- Sign in with an account that paid on the website and note which features unlock. Under 3.1.3(b) that is allowed, provided the same items are also available as in-app purchases in the app.
- In App Store Connect, check which countries and regions the app is available in. The rules for links to your web checkout are different on the United States storefront from everywhere else.
Why it happens
The core rule, from Guideline 3.1.1:
“If you want to unlock features or functionality within your app, (by way of example: subscriptions, in-game currencies, game levels, access to premium content, or unlocking a full version), you must use in-app purchase.”
The same guideline adds that apps "may not use their own mechanisms to unlock content or functionality". This guide treats a Stripe payment form or Checkout page shown inside your app's own WebView as exactly that, on every storefront where you do not hold an alternative payment entitlement. In the EU, Apple allows an alternative payment processor inside the app under separate terms, with the StoreKit External Purchase Entitlement and the External Purchase APIs (Apple: alternative payment providers in the EU). Stripe's own iOS guidance for digital goods is a link out to Checkout in a browser, and only for the United States (Stripe: in-app purchases on iOS and Android).
What changed for the United States is the link-out. Guideline 3.1.1(a) says the StoreKit external purchase link entitlements are not needed there:
“These entitlements are not required for developers to include buttons, external links, or other calls to action in their United States storefront apps.”
Outside the United States, the same section says apps "may not include buttons, external links, or other calls to action that direct customers to purchasing mechanisms other than in-app purchase", except through StoreKit External Purchase Link Entitlements, which are limited to specific storefronts and platforms. So one binary with one "Upgrade on our website" button can be fine for American users and a rejection everywhere else.
Your existing web customers are not the problem. 3.1.3(b) Multiplatform Services lets users access subscriptions or features they bought on your website, "provided those items are also available as in-app purchases within the app". The web checkout can stay. What the app needs is its own way to buy.
How to fix it
For an app that sells digital features, the change that works in every storefront is: in-app purchase in the iPhone app, Stripe on the website, and one record of who has paid that both feed. The steps below assume a Capacitor wrapper and a Supabase backend. For an Expo or React Native app the same plan applies with RevenueCat's Expo SDK.
1. Set up the products in App Store Connect
- Sign the Paid Apps Agreement: in App Store Connect choose Business, then on the Agreements tab find Paid Apps and accept the terms. Only the Account Holder can do it, and it must be active before you can submit in-app purchases (Sign and update agreements). Add tax and banking details while you are there.
- In your app, open Monetization, then Subscriptions, and create one subscription group. Apple's help page calls a single group the best practice for most apps, because a user can hold only one subscription per group at a time (Offer auto-renewable subscriptions).
- Inside the group, create each plan: reference name, product ID, duration, price, availability, and under Review Information anything that helps the reviewer (the page has room for a screenshot and notes).
- Plan the release: Apple requires your first auto-renewable subscription and your first subscription group to be submitted together with a new app version.
2. Add in-app purchase to the Capacitor app
Apple's purchase framework, StoreKit, is a native Swift API, so a web app needs a plugin to reach it. One option is RevenueCat, a third-party service with a Capacitor SDK (RevenueCat: Capacitor). Install it with npm install @revenuecat/purchases-capacitor followed by npx cap sync, and enable the In-App Purchase capability for the iOS target in Xcode. Then identify the buyer with the same user ID your Supabase auth uses, so a purchase belongs to an account and not only to a phone:
import { Capacitor } from "@capacitor/core";
import { Purchases, PURCHASES_ERROR_CODE } from "@revenuecat/purchases-capacitor";
const ENTITLEMENT_ID = "pro"; // the entitlement you created in RevenueCat
export async function startPurchases(supabaseUserId: string): Promise<void> {
if (Capacitor.getPlatform() !== "ios") return;
await Purchases.configure({
apiKey: import.meta.env.VITE_REVENUECAT_IOS_PUBLIC_KEY,
appUserID: supabaseUserId,
});
}
export async function buyFirstPackage(): Promise<boolean> {
const offerings = await Purchases.getOfferings();
const pkg = offerings.current?.availablePackages[0];
if (!pkg) throw new Error("No subscription is available right now.");
try {
const { customerInfo } = await Purchases.purchasePackage({ aPackage: pkg });
return ENTITLEMENT_ID in customerInfo.entitlements.active;
} catch (error: unknown) {
const code = (error as { code?: string }).code;
if (code === PURCHASES_ERROR_CODE.PURCHASE_CANCELLED_ERROR) return false;
throw error;
}
}
export async function restore(): Promise<boolean> {
const { customerInfo } = await Purchases.restorePurchases();
return ENTITLEMENT_ID in customerInfo.entitlements.active;
}- Add a visible "Restore purchases" button. Guideline 3.1.1 asks for a restore mechanism for restorable purchases.
- Before the user subscribes, say clearly what they get for the price (3.1.2(c)).
- On iOS, hide or replace every Stripe button and web pricing link found in check 2. Keep them on the website.
3. Keep one record of who has paid
A user who pays on the web and then opens the app, or the other way round, should see the same access. There are two common ways to do it. RevenueCat can import Stripe subscriptions bought on your website, as long as the app uses the same App User ID that the Stripe purchase was recorded under (Importing external purchases). Or you keep the record in Supabase and let webhooks from Stripe (Supabase example) and from RevenueCat (RevenueCat webhooks) write to it from Edge Functions. A minimal table for the second way:
create table public.entitlements (
user_id uuid not null references auth.users (id) on delete cascade,
source text not null check (source in ('stripe', 'app_store')),
product_id text not null,
expires_at timestamptz,
updated_at timestamptz not null default now(),
primary key (user_id, source)
);
alter table public.entitlements enable row level security;
grant select on public.entitlements to authenticated;
grant select, insert, update, delete on public.entitlements to service_role;
create policy "Users can read their own entitlements"
on public.entitlements
for select
to authenticated
using ((select auth.uid()) = user_id);
create or replace function public.has_active_entitlement()
returns boolean
language sql
stable
security invoker
set search_path = ''
as $$
select exists (
select 1
from public.entitlements e
where e.user_id = (select auth.uid())
and (e.expires_at is null or e.expires_at > now())
);
$$;profiles.is_pro column from front-end code. Anyone can call your Data API with your public key and their own login, so access must be granted only by server-side code that has checked the payment with Stripe, Apple or RevenueCat.4. Optional: a web checkout link on the United States storefront
On the US storefront you may also show a button that opens your Stripe Checkout in the browser, next to in-app purchase. Stripe's link-out guide describes the flow and suggests StoreKit's storefront to detect where the app was downloaded from. With RevenueCat you can read it in JavaScript; StoreKit reports a three-letter country code (Storefront.countryCode):
import { Browser } from "@capacitor/browser";
import { Purchases } from "@revenuecat/purchases-capacitor";
export async function canShowWebCheckoutLink(): Promise<boolean> {
try {
const { countryCode } = await Purchases.getStorefront();
return countryCode === "USA";
} catch {
return false; // unknown storefront: show in-app purchase only
}
}
export async function openWebCheckout(checkoutUrl: string): Promise<void> {
await Browser.open({ url: checkoutUrl }); // SFSafariViewController on iOS
}npm install @capacitor/browser and npx cap sync. Stripe's guide opens Checkout in Safari and returns to the app with a Universal Link as success_url. If you want to match it exactly, open the URL in the system browser (for example with @capacitor/app-launcher) instead of an in-app browser sheet, and set success_url to a Universal Link.Outside the US, hide the button and any "buy on the web" text. Guideline 3.1.3 does allow you to tell your users about other purchase methods outside the app, for example by email.
5. Reply and resubmit
Submit the subscriptions with the new build, and use the Review Notes to say where the paywall and the restore button are and that the iOS app no longer links to web checkout outside the US. If your app is in one of the exceptions from check 1 (physical goods, person-to-person services, enterprise), reply to App Review from the App Review page in App Store Connect and explain which guideline applies. If you believe the reviewer misunderstood the app, you can appeal to the App Review Board, once per rejected submission (App Review).
When to get help
- You already have paying web customers and need their access to carry over to the app without anyone losing what they paid for.
- Your product mixes cases (physical goods plus a digital subscription, or live sessions plus recorded content) and you are not sure which guideline covers which part.
- Webhooks from Stripe and Apple or RevenueCat need to land in one table, and you do not want to test that on real customers.
- The rejection came close to a launch date and you want the next submission to be the last.
Sources
Primary documentation this guide was checked against. Platforms change - if something here no longer matches, the source wins.
- App Store Review Guidelines, 3.1 Payments (last updated 2026-10-16)Apple Developer
- In-App PurchaseApple Developer
- Offer auto-renewable subscriptionsApp Store Connect Help
- Sign and update agreementsApp Store Connect Help
- App Store Small Business ProgramApple Developer
- Storefront.countryCodeApple Developer Documentation
- App ReviewApple Developer
- Apps using alternative payment providers in the EUApple Developer
- Accept in-app purchases on iOS and AndroidStripe docs
- Digital goods on iOS with a prebuilt payment pageStripe docs
- Stripe integrationLovable docs
- Capacitor installationRevenueCat docs
- Importing external Stripe purchasesRevenueCat docs
- Browser pluginCapacitor docs
- Handling Stripe webhooksSupabase docs
- Tables not exposed to the Data API automaticallySupabase changelog
Frequently asked questions
- Can I use Stripe in my iOS app at all?
- Yes, for physical goods and services used outside the app, where Guideline 3.1.3(e) actually requires a payment method other than in-app purchase, and for real-time one-to-one services under 3.1.3(d). For digital features, content or subscriptions used in the app, 3.1.1 requires in-app purchase.
- Is a link to my website's pricing page allowed?
- On the United States storefront, yes: Guideline 3.1.1(a) says no entitlement is needed for buttons, external links or other calls to action there. In other storefronts, links that send users to a non-Apple purchase are not allowed unless you hold a StoreKit External Purchase Link Entitlement, which is available only in specific regions.
- Do I have to stop selling through Stripe on my website?
- No. Under 3.1.3(b), users can access in the app what they bought on your website, provided the same items are also available as in-app purchases in the app. The web checkout stays; the app adds its own.
- Can the app be free and only sell on the web?
- For digital content used in the app, only in the narrow cases the guidelines list: reader apps (3.1.3(a)), enterprise services sold to organisations (3.1.3(c)), and free companion apps to a paid web tool for VoIP, cloud storage, email or web hosting with no purchasing or purchase calls to action (3.1.3(f)). Person-to-person services (3.1.3(d)), physical goods and services outside the app (3.1.3(e)) and advertising management apps (3.1.3(g)) are separate exemptions, covered in check 1. Otherwise 3.1.3(b) expects the items to be available as in-app purchases too.
- Do I need RevenueCat?
- No. It is one way to reach Apple's StoreKit from a Capacitor or Expo app without writing Swift. You can also write a small native plugin around StoreKit yourself. Either way the products are created in App Store Connect and Apple processes the payment.
- How much does Apple take?
- Apple charges a commission on in-app purchases. Through the App Store Small Business Program, developers with up to 1 million USD in proceeds in the prior calendar year, and developers new to the App Store, can qualify for a reduced 15% rate. You have to enroll; it does not apply automatically.
Related guides
Fixed-price audit
Want someone to check the whole app, not just this?
A review of data security, production readiness and App Store readiness for apps built with AI tools. 900 USD, a ranked list of fixes within 5 business days.