Apple and Google Billing for Drama Coins Explained

If a viewer buys coins inside your iOS or Android app, Apple and Google both require you to sell them through their own billing, and both take a commission. If the viewer buys coins on your own website, that purchase sits outside store billing, but the stores limit how far the app may point to it. The details differ by country and change, so this post quotes the rules as they stood in October 2026 and tells you where to re-check them.

The question matters most for coin-first apps. A white-label ReelShort clone earns on the coin pack, so the share of each pack that reaches you decides the margin on the whole business. This is a planning guide, not legal advice.

Why coins raise a store question

Both stores sort purchases into two buckets. Physical goods and services consumed outside the app, such as a taxi ride, can use any payment method. Digital goods consumed inside the app must use store billing. A coin is a digital good by design: it has no use except to unlock episodes in your app, so a coin unlock is exactly the kind of in-app feature the rule describes.

Apple's App Store Review Guidelines, in 3.1.1, say that if you want to open features or functionality in an app, giving subscriptions, in-game currencies and access to premium content as examples, you must use in-app purchase. The same guideline says apps may not use their own mechanisms for this, naming license keys, QR codes and cryptocurrencies. Google's payments policy, in its section on in-app purchases, lists virtual currencies, subscriptions, app functionality and cloud services as items that need Google Play billing. Neither store has an exception for "it is only a small amount" or "the video is the real product".

A second, quieter rule matters for drama apps. Google's policy says virtual currency bought in an app must stay usable only in that title. Apple's 3.1.1 asks that credits bought by in-app purchase do not expire and that you offer a restore mechanism for restorable purchases. Both shape the wallet you design, which is why the wallet is a billing topic and not only a product topic. The wider mechanics of a coin balance are covered in how a coin economy works.

Inside the app versus on the web

An operator sells coins through up to three channels. The table compares them as the rules stood in October 2026.

The first two rows are the default for any store app. The third row is the reason many operators start on the web: the viewer pays a processor fee and nothing more, and the wallet works the same way. The fourth row is where the rules vary most, and the next two sections cover it.

What the stores take

Apple

Apple's newsroom statement on the App Store Small Business Program gives the standard commission as 30 percent for apps selling digital goods and services. Apple's Small Business Program page describes a reduced 15 percent commission for developers who earned up to 1 million USD in proceeds in the prior calendar year, including developers new to the App Store. It adds that if a participating developer passes the threshold in the current year, the standard rate applies to later sales. The same page mentions a further reduced 10 percent for developers on the alternative terms in the EU who are in the program, and for subscriptions after their first year. Treat these numbers as the outline and confirm your own eligibility on Apple's page.

Google

Google's service fees page was reorganized in 2026 and is now split by region and by when a user first installed your app. As of October 2026 it shows effective dates of June 30, 2026 for the EEA, the UK and the US and September 30, 2026 for Australia and Japan. For those regions, the rows tied to the first 1 million USD of annual earnings list 10 percent plus a 5 percent billing fee for auto-renewing subscriptions and for other transactions from new installs, and 20 percent plus the 5 percent billing fee for other transactions from existing installs. For the remaining markets the page lists 15 percent on the first 1 million USD a year, 30 percent above that, and 15 percent for auto-renewing subscriptions. It also has separate lines for transactions that start from external web links. This table has moved before and will probably move again, so read the live page on the day you set prices.

Take the two together and you can see why the stores' share is a design input. A coin app sells many small packs, so the percentage applies to a lot of transactions, and no part of it can be negotiated per title.

A worked example with example numbers

These numbers are an illustration, not a quote. Say one coin pack costs 10 and a processor charges 3 percent on web sales.

• Sold on the web: the processor keeps 0.30, so you receive 9.70.
• Sold in the app at a 30 percent commission: the store keeps 3.00, so you receive 7.00.
• Sold in the app at a 15 percent commission: the store keeps 1.50, so you receive 8.50.

The gap between the first and second lines is 2.70 on every pack, or 27 percent of the sticker price. If a viewer spends 40 in a month, that is 10.80 that either reaches you or does not. Taxes, refunds and fixed processor fees are ignored here, and your own numbers will differ. The exercise is still useful because it tells you whether the store apps are a profit channel or a reach channel for your first year. Pack sizing and bonus coins are covered in micro drama coin pricing.

Exceptions vary by region and change

The default rule, store billing for in-app digital goods, has regional exceptions. Each one has a set of conditions, and each one can be changed by a regulator or a court. Here is what the primary pages say as of October 2026.

Apple

Guideline 3.1.1(a) says developers may apply for entitlements to include a link to a website they own so customers can buy digital content there. It then says these entitlements are not needed to include buttons, external links or other calls to action in apps on the United States storefront. For specific other regions, the StoreKit External Purchase Link Entitlement lets an app include a link informing users of other ways to buy, and the guideline says the link may inform users that items may be available for a comparatively lower price. For every other storefront, the guideline says apps and their metadata may not include buttons, external links or other calls to action that direct customers to purchasing mechanisms other than in-app purchase. The same guideline says an app that engages in misleading marketing or fraud around the entitlement can be removed and the developer can be removed from the program.

The guideline does not say, in the section quoted above, what Apple's commission on link-out purchases is for each region. That is set in the entitlement agreements. If you plan to use a link, read those terms before you model margin.

Google

Section 4 of Google's payments policy says apps may not lead users to a payment method other than Google Play billing, in listings, in-app promotions, webviews or user flows, except as allowed under sections 3, 8 and 9. Section 8 covers alternative billing in eligible countries for developers enrolled in the matching program, and section 9 covers directing users outside the app to other payment methods in eligible regions, again with enrollment. Google's external offers program page says the program is currently limited to the EEA, requires approval of the app and the linked destinations, and cannot be combined with Google Play billing in the same app. It also lists fees that apply within 24 hours of a click on an external link, effective June 4, 2026: 10 percent on auto-renewing subscriptions, 20 percent on other digital items, and a per-install charge for app downloads.

The practical reading: outside the US on iOS, and outside enrolled programs on Android, the app should assume it cannot direct viewers to a web top-up. Where a program applies, the link is available but not free, and it comes with rules about placement and reporting. Regional detail for markets with their own payment habits is in regional pricing and local payments for a drama app.

Web top-up as a route

A web top-up is a coin purchase made in a browser, on your own domain, with a hosted checkout page from your processor. It is the standard way operators keep full margin, and it is not what the store rules are about. They are about what the app may do. Four points follow from the quoted text.

1. A viewer who finds you on the web can buy there. The web app is a separate product with a separate checkout. Apple's 3.1.1(a) and Google's section 4 both speak about apps and their metadata or flows, not about your own website.
2. The app cannot assume it may link to that checkout. Check the storefront rule above. In many regions the safe design is that the app shows in-app packs only.
3. Spending web coins in the app is allowed under Apple's multiplatform rule, with a condition. Guideline 3.1.3(b) says apps that operate across multiple platforms may allow access to content, subscriptions or features acquired on other platforms or the web, including consumable items, provided those items are also available as in-app purchases in the app. So if coins bought on the web open episodes in your iOS app, the same coin packs must also be on sale inside it.
4. Your marketing outside the app is a separate question. An email, a social post or a search ad for your website is not an app or app metadata. Whether a given message could be read as steering is a judgment for your lawyer, since the quoted rules do not address off-app marketing.

What the build supports

Our ReelShort clone app ships a web app, a Flutter store app and an operator console on one API and one wallet. For billing, the delivered build includes the following:

• Hosted checkout through PayPlus as the primary web path, with Stripe, Razorpay and Flutterwave switches in the console. Merchant accounts are yours and we connect them during delivery.
• An Apple in-app purchase flow in the iOS app for coins and plans, set up with you during delivery.
• A Google Play billing switch in the Android app, with a store product key on each coin pack, tying the console record to the in-app product it represents.
• One wallet and one unlock record across web and app, so coins bought in one place spend in the other and an episode unlocked on the web is already open in the app.
• Two balances: purchased coins, which do not expire, and reward coins from check-ins, quests and ads, which expire after a window you set. Spending draws reward coins first.

Store products are created in your own Apple and Google accounts and mapped to the packs in the console. Those accounts, their fees and the commission are yours; our ReelShort clone features page lists the wallet and checkout pieces in full, and the ReelShort clone development cost page lists store accounts and commission among the running costs outside the platform price. We prepare builds and help with submission, but Apple and Google decide whether a listing is accepted and how coin sales must be billed.

We also set up regional prices per country for your build.

Pricing app and web separately

Because the app channel costs more per pack than the web channel, many operators set prices by channel. Treat the steps below as a planning sequence; whether it fits depends on the storefront rules you operate under and on what your lawyer says about how you describe the difference.

1. List every pack and plan you want to sell. Write the viewer price, the coin count and any bonus coins for each.
2. Work out net revenue per channel. Use the live commission pages and your processor's fees, as in the worked example above.
3. Decide the store price tiers first. Apple and Google sell products at price points the store defines, so the in-app price is picked from their list and the in-app pack is built around it.
4. Set the web pack to the same coin count or a deliberate variant. A different bonus is a business choice, but it must be explained clearly to the viewer wherever you are allowed to explain it.
5. Keep the wallet identical. A coin is a coin whatever route bought it, so spending, expiry and refunds do not depend on the channel.
6. Disclose prices honestly. Google's section 6 asks that prices shown in the app match what the Play billing interface displays, and Apple requires subscription terms to be clear before the viewer subscribes.
7. Review quarterly. Both stores revise terms, and the 2026 pages show how much the fee tables can change in a year.

Review risks

Apple and Google decide whether your app is accepted. These are the points the quoted guidelines make that most often matter for a drama app.

The same reviewers will look at your content, not only your billing. If viewers can post comments, the user-generated content rules apply too, which is covered in app store review for user-generated content.

Subscriptions and passes next to coins

Many drama apps sell a time-limited pass beside coins. Apple's guideline 3.1.2(a) says an auto-renewable subscription must provide ongoing value, the period must be at least seven days, and it must work across all of the user's devices. It lists episodic content and large, continually updated media collections as examples of acceptable subscription value. It also says subscriptions may be offered alongside a la carte offerings, and may include consumable credits or gems. That fits a pass that opens a library for a window while coins still pay for single episodes. Google lists subscriptions in the same payments-policy section as virtual currency.

The design question is not whether the stores allow both. It is whether the pass is a clear product: what it opens, for how long and at what renewal price. A pass that renews weekly raises the same disclosure duties as one that renews yearly.

Who to ask and what to do next

Start with the primary sources, which are the two policy pages and the two fee pages listed under this post. Read the sections on in-app purchase, virtual currency and external links as they stand on the day you decide, because the dates in this post will go out of date.

Then take these steps in order:

1. Pick the launch channel. Web first gives full margin and the fastest start; store apps give reach and a billing flow viewers trust.
2. Open the Apple Developer and Google Play accounts early. Approval timelines run on their own clocks.
3. Model one pack at store and web margins using the live commission figures for your eligibility tier.
4. Ask a lawyer who knows your market to confirm how you may describe web top-up, and whether any program enrollment fits.
5. Submit with a demo account, complete products and honest price text.

If you want a working wallet and both store flows already built, the ReelShort clone script page lists what ships. Start there, then talk through your channel plan with us before you set coin prices.