Apple in-app purchase for OTT app
Apple in-app purchase for OTT app on Flicknexs: StoreKit product IDs mapped to plans and per-title prices, purchases recorded from the iOS app.
Flicknexs maps App Store product identifiers to the plans and per-title prices in its admin, so the iOS app can sell through StoreKit and the platform can record the purchase and open the content.
Trusted by industry leaders
50+ streaming companies powered by Flicknexs
Apple in-app purchase for OTT app means the iOS app sells subscriptions and single titles through Apple's StoreKit, with Apple collecting the money at the store's published fee. On Flicknexs, product IDs are mapped to plans and per-title prices in the admin, and the platform records each purchase reported by the app and grants access.
Flicknexs provides apple in-app purchases as part of its white-label OTT platform. Flicknexs maps App Store product identifiers to the plans and per-title prices in its admin, so the iOS app can sell through StoreKit and the platform can record the purchase and open the content.
Why Apple in-app purchase is a decision, not a feature toggle
An operator who ships an iOS app faces a choice they do not face on the web. Apple decides when a purchase inside an app must go through Apple's in-app purchase system, and the store's published fee applies to every sale made that way. Some operators sell only on the website and let the iOS app be a viewing surface. Others sell inside the app because that is where the audience is, and accept the fee for the convenience. Either way, the platform must handle the StoreKit purchase correctly and record it against the right plan or title.
Flicknexs handles the in-app side as follows. The iOS app presents the subscription plans and pay-per-view titles that have an App Store product identifier mapped to them in the admin. The viewer buys through StoreKit, Apple charges the viewer's Apple ID, and the app reports the completed purchase to the platform, which records it and grants access to the plan or the title. Prices shown in the app are Apple's prices for that product in the viewer's storefront, set in App Store Connect rather than in the Flicknexs admin.
The rules on when in-app purchase is required, what content may be sold outside it, and how subscriptions behave are written by Apple in the App Store Review Guidelines and the StoreKit documentation, and they change by region and over time. This page describes what the platform does with a StoreKit purchase; it does not interpret Apple's rules for your app. Read the guidelines, particularly the section on in-app purchase, before deciding whether to sell inside the app at all, and re-read them at each major release.
What the Apple in-app purchase integration does on Flicknexs
Each row is behavior present in the Flicknexs iOS app and admin on the date checked, stated in Apple's own terms.
StoreKit purchases
The iOS app sells subscription plans and pay-per-view titles through StoreKit, charged to the viewer's Apple ID.
Product ID to plan
Each subscription plan in the admin can carry the App Store product identifier that sells it.
Product ID to title
Each pay-per-view title can carry its own App Store product identifier and price mapping.
Purchase recorded from the app
After StoreKit completes, the app reports the purchase and the platform records it against the viewer.
Access on every device
A plan bought in the iOS app is attached to the account and works in the web and other apps.
Store pricing
The price the viewer sees is Apple's price for that product in their storefront, set in App Store Connect.
Revenue reports
In-app purchases recorded by the platform appear in the monthly subscription and pay-per-view reports alongside web sales.
Source: Flicknexs platform documentation and architecture specification, 2026-09-03.
How an Apple in-app purchase flows through the Flicknexs iOS app
From the product identifier in App Store Connect to the access record on the platform, this is the path a purchase takes.
Products are defined in App Store Connect
The admin maps identifiers to plans and titles
StoreKit runs the purchase sheet
The app reports the purchase and the platform records it
Access follows the account, not the device
What stays with Apple
Setup for Apple in-app purchase, from App Store Connect to the admin
Five steps in order. The first two happen inside Apple's tools; the last three in the Flicknexs admin and the app build.
- 1
Accept Apple's paid apps agreement and set up banking
In App Store Connect, the account holder accepts the paid applications agreement and enters banking and tax details. Apple will not sell anything inside your app until this is complete, and the review of those details is Apple's timeline, not the platform's. Start it early; it is the step operators most often discover late.
- 2
Create the products in App Store Connect
Create an auto-renewable subscription product for each plan you want to sell inside the app, grouped in a subscription group, and a non-consumable or similar product for each pay-per-view title you want to sell there. Give each a clear identifier and choose its price tier. Note the identifiers; you will paste them into the admin.
- 3
Map identifiers to plans and titles in the admin
Open each subscription plan in the Flicknexs admin and enter its App Store product identifier. Open each pay-per-view title you intend to sell in the app and enter its identifier and price mapping. Plans and titles with no identifier are not offered for purchase inside the iOS app, which is a useful way to keep some content web-only.
- 4
Test with a sandbox Apple ID
Build the iOS app with your mappings, sign in on a test device with a sandbox Apple ID from App Store Connect, and buy a plan and a title. Confirm that the app shows Apple's price, that the purchase completes on Apple's sheet, that the platform records it on the subscriber record, and that the content opens on the device and on the website with the same account.
- 5
Submit for review with in-app purchases attached
Attach the in-app purchase products to the app version in App Store Connect and submit for review. Apple reviews the products alongside the build. After approval, make one real purchase of a low-priced title from a personal Apple ID and check it in App Store Connect and in the admin before promoting in-app purchase to viewers.
Limits: what the Apple in-app purchase integration does not do
Stated plainly so the decision to sell inside the app is made with the current build in view.
No server-side receipt validation
No App Store Server Notifications
Prices and offers are set in App Store Connect
Coupons do not apply inside the app
Apple's rules decide when in-app purchase is required
Worked example: a kids education service selling on iPhone and iPad
Checklist before you sell through Apple in-app purchase
Run every line with a sandbox Apple ID first, then repeat the purchase line once with a real account after review.
- The paid applications agreement is accepted in App Store Connect and banking and tax details are complete, so Apple can pay you.
- Every plan sold in the app has an auto-renewable subscription product in App Store Connect and its identifier on the plan in the admin.
- Every pay-per-view title sold in the app has a product in App Store Connect and its identifier and price mapping on the title.
- Plans and titles that should stay web-only have no identifier, and the iOS app does not offer them for purchase.
- A sandbox purchase of a plan shows Apple's localized price, completes on Apple's sheet, and appears as active on the subscriber record.
- A sandbox purchase of a single title records a pay-per-view purchase and opens the title on the device and the website.
- Your support desk knows that cancellations and refunds happen in Apple's systems and that the subscriber record in the admin is updated by hand afterward.
- Your team has read the App Store Review Guidelines section on in-app purchase and knows what the app may sell outside it.
- In-app purchase products are attached to the app version submitted for review, and one real low-priced purchase has been checked after approval.