Guideline 3.1.1 rejection: creator payments that pass review in 2026

Which creator app payments need Apple in-app purchase and which can use Stripe, 2026

TL;DR

A guideline 3.1.1 rejection in 2026 usually means your app sells something digital and collects the money outside Apple's in-app purchase. Live streaming and social video apps hit it often, because viewers pay for content that plays on the screen.

  • Paid public streams, tips and coins go through in-app purchase. Apple's commission is 15% in its Small Business Program.
  • A real-time service between two individuals, such as a private one-to-one stream request, may use Stripe under guideline 3.1.3(d). One-to-few and one-to-many may not.
  • Paying creators out is a separate flow. Stripe Connect charges $2 per monthly active account plus 0.25% + 25ยข per payout when you set your own pricing.
  • Stripe-hosted card fields keep you at PCI SAQ A. Card data sent straight to the API means SAQ D.

Why creator payment apps fail review

If the app sells features, content or currency used inside the app, the sale goes through in-app purchase. Guideline 3.1.1 also bans your own mechanisms for the same job, such as license keys and QR codes.

A creator app trips this three ways: paid live streams, coins that viewers spend on creators, and tips. Each is digital content in Apple's reading, so a Stripe card form in front of any of them invites rejection.

Tips are the trap founders miss. Guideline 3.1.1 lets apps use in-app purchase currencies to tip digital content providers, which means the allowed route runs through Apple. Insight Timer learned this in 2024: Apple had approved 47 updates of the meditation app with teacher tipping, then decided the payments were digital goods purchases, as Michael Tsai summarized from the press reports.

October 2026: the rules in force and the fee still in court

The current App Review Guidelines were last updated on October 16, 2026. Guideline 3.1.1(a) lets United States storefront apps include buttons and external links to web checkout without any entitlement. Every other storefront still bans them unless you hold one of Apple's link entitlements.

The price of that link is not settled. According to MacDailyNews, Apple has charged zero commission on US link-out purchases since the 2025 contempt ruling in Epic v. Apple. The Ninth Circuit upheld the contempt finding but let the district court set a commission limited to costs that are genuinely and reasonably necessary. In August 2026 the Supreme Court declined to pause the rate proceedings while it reviews the contempt finding. Apple proposed 15% for standard apps, 10% for some partner programs and renewals, and 5% for Small Business Program apps.

So a US web checkout link is allowed and free today. Build it so the fee can change without a new release.

When in-app purchase is required and when Stripe Connect works

Sort every money flow by what the buyer gets and where they get it. App Review sorts it the same way.

What the viewer pays forRoute on iOSGuideline
Paid public stream, replay, subscriptionIn-app purchase; US storefront may also link to web checkout3.1.1, 3.1.1(a)
Coins, credits or tips spent on creatorsIn-app purchase currency3.1.1
Private real-time stream booked by one viewer from one creatorStripe or another processor allowed3.1.3(d)
Group class or one-to-few live sessionIn-app purchase3.1.3(d)
Merch, tickets to a physical eventStripe, Apple Pay or card entry; in-app purchase not allowed3.1.3(e)
Optional gift with 100% to the creator, tied to no contentOutside in-app purchase allowed3.2.1(vii)

The private stream row carries the most weight. A viewer who books one creator to film a place for them, live, buys a real-time service between two individuals, the kind 3.1.3(d) illustrates with tutoring and real estate tours. Open the same stream to an audience and it becomes one-to-many, and in-app purchase is back. That is our reading; App Review decides per app, so describe the flow plainly in the review notes.

The gift row is narrow. Under 3.2.1(vii), a gift connected at any point with digital content must use in-app purchase, so a tip that buys a shout-out on stream is not a gift.

Credits versus dollars

Founders want prices in dollars, because viewers and creators think in dollars. The App Store has no objection to a dollar-denominated credit. It objects to how the credit is bought.

On iOS, credits bought for use in the app are an in-app purchase currency. Guideline 3.1.1 adds that credits bought through in-app purchase may not expire. Price points come from Apple, and Apple keeps its commission, 15% for members of its Small Business Program, so a viewer who pays $9.99 for credits does not put $9.99 into the creator pool.

The workable pattern:

  • Sell credit packs through in-app purchase and price streams per minute in credits, with dollar values shown.
  • Keep two numbers in your ledger: what the viewer paid and what the platform received after the store fee. Creator earnings come from the second.
  • On the US storefront, offer the same packs on the web through Stripe and link to them from the app.

What a subscription nets on each route is compared in our guide to in-app vs out-of-app billing.

Paying creators out with Stripe Connect

The payout side never touches App Review. Three Stripe limits shape it.

Money takes time. A new connected account waits for its first standard payout, usually seven days from the first live payment, says Stripe support; the payouts guide says 7 to 14 days. With separate charges and transfers, a transfer tied to an unsettled charge becomes available to the creator only when the charge funds become available to the platform. Viewer access cannot wait for that. Grant access when the charge succeeds and settle the creator later.

The API has a ceiling. Stripe's rate limits are 100 requests per second in live mode and 25 in a sandbox, with 25 per endpoint unless noted and 15 payout creations per second. Per-minute billing that polls Stripe for balances will hit them, so keep balances in your own ledger and reconcile in batches.

The platform carries the losses. With separate charges and transfers your balance absorbs refunds and chargebacks, and a refund does not reverse the creator's transfer by itself.

Price it in: Stripe Connect costs $2 per monthly active account plus 0.25% + 25ยข per payout.

What to build before the first payout dispute is covered in our guide to marketplace dispute resolution.

Why card fields belong to Stripe, not to your UI

A custom card form moves you into a different compliance class.

Stripe's PCI guide puts Checkout, Elements and the UI components of the official iOS and Android SDKs on SAQ A, the shortest self-assessment. Card data passed directly to Stripe's API puts you on SAQ D, the most demanding one. Stripe's integration security guide says a business handling card data directly may need to meet more than 300 PCI DSS controls.

Keep card entry inside Stripe's hosted fields and SDK sheets, and only for flows that may use Stripe at all. The app we redesigned for Grant's Interest Rate Observer includes payment gateway integration for client-side PCI compliance.

When a wallet starts to look like a bank

A wallet feels like good product design: top up once, spend in small amounts. Regulators see something else.

31 CFR 1010.100 excludes a person that only acts as a payment processor for a good or service by agreement with the seller, or that accepts and transmits funds only as an integral part of selling goods or services. FinCEN's prepaid access FAQ excludes closed loop prepaid access limited to $2,000 or less on a device on any day. A wallet that only buys content in your app stays near those exclusions. One that lets users send or withdraw balance moves toward money transmission.

Design rules that keep you out of bank territory:

  • Credits are spent in the app and never cashed out by viewers.
  • Creator earnings live in the creator's Stripe connected account, not in a balance you hold.
  • No peer-to-peer transfers of balance between viewers.
  • Manual payout holds stay short. Stripe allows funds to sit in a US connected account for up to 2 years and 90 days in most other countries, per its manual payouts guide, but a long hold makes you look like the custodian.

This is a map, not legal advice. Have a payments lawyer sign off on the wallet.

What social video and music buyers bring us

These shares come from our presales records for social video, live streaming and music products, counted by hand. They describe buyers, not the market.

Around 65% wanted monetization in the first release: subscriptions, paid discovery, per-minute billing or in-app subscriptions. Around 35% planned a payment flow that collided with store billing, either a card-based scheme for in-app content or a Stripe web subscription that had to coexist with in-app subscriptions. Around 35% needed to pay creators or artists out, not only take money in.

The risks we flagged on one live streaming marketplace cover the whole topic. Its card-based monetization carried a high risk of App Store rejection. Collecting cards in our own UI instead of Stripe-hosted flows would have pulled the product into PCI DSS scope. A balance held for users raised the question of holding funds like a bank. Stripe onboarding that asks creators for sensitive data could cost sign-ups. Transfers could arrive too late for immediate viewing, and rate limits could break real-time balances. The founder also wanted prices in dollars, not tokens.

Draw the money map before the screens

A guideline 3.1.1 rejection is usually decided in the first design sprint, when someone draws a checkout screen before anyone draws where the money goes.

Start with a one-page map. Every arrow is a payment: viewer to platform, platform to creator, creator to platform for promotion. Label each arrow with the buyer, what they get and the route: in-app purchase, US web link, or Stripe under 3.1.3(d) or 3.1.3(e). Then design screens. Review risk, PCI scope and money transmission get settled there, before any payment code.

We have built apps since 1999, with 500+ engineers, and our apps reach more than 40 million users. Social video is part of that history: Shots, a social network that attracted over 8 million teenagers. For the two-sided version of this problem in music, see our guide to a swipe music discovery app, and for the healthcare version, our article on healthcare app payments.

Written by Rob Devereaux, Chief Operating Officer at Mercury Development. Rob has run the firm's operations from Hudson, Ohio since 2019 and has over 20 years of operational and financial experience. The presales records behind this article's buyer section sit in the operations he oversees.

Send us your money flow and we will mark the review risks

Tell us who pays, for what, and who gets paid. We will mark each flow as in-app purchase, web link or Stripe, flag where review, PCI scope or a stored balance can hurt you, and outline the payout design.

Which of your payments will Apple reject?

Feel free to contact us and we'll respond as soon as possible.

Frequently asked questions

Sources

  1. Tsai, M. IAP Required for Insight Timer Tips. Published 2024-02-23. (BlogPosting)
  2. Apple. App Review Guidelines. Undated. (WebPage)
  3. MacDailyNews. U.S. Supreme Court clears path for App Store commission showdown as Apple must defend its rates in lower court. Published 2026-08-14. (NewsArticle)
  4. Apple. App Store Small Business Program. Undated. (WebPage)
  5. Stripe. Delay for first payout for connected accounts. Undated. (WebPage)
  6. Stripe. Receive payouts from Stripe. Undated. (TechArticle)
  7. Stripe. Create separate charges and transfers. Undated. (TechArticle)
  8. Stripe. Rate limits. Undated. (TechArticle)
  9. Stripe. Pricing information | Stripe Connect. Undated. (WebPage)
  10. Stripe. A guide to PCI compliance. Undated. (WebPage)
  11. Stripe. Integration security guide. Undated. (TechArticle)
  12. Mercury Development. Grant's Interest Rate Observer. Undated. (WebPage)
  13. Office of the Federal Register. 31 CFR 1010.100 General definitions. Undated. (Legislation)
  14. FinCEN. Frequently Asked Questions regarding Prepaid Access. Published 2016-03-24. (WebPage)
  15. Stripe. Using manual payouts. Undated. (TechArticle)
  16. Mercury Development. Mobile App Development and Wearable Solutions. Undated. (WebPage)
  17. Mercury Development. Shots Case Study: Brand Identity and Digital Experience. Undated. (WebPage)
  18. Devereaux, R. Swipe music discovery app: two-sided paid discovery in 2026. Published 2026-11-10. (BlogPosting)
  19. Devereaux, R. HIPAA compliant payment processing in health apps 2026: Stripe vs IAP. Published 2026-10-30. (BlogPosting)
  20. Mercury Development. Internal media and entertainment presales records, aggregated. Undated. (Dataset)