App store rules
Dating App Subscription Pricing After Store Fees
Dating app subscription pricing starts with what you keep after store fees. Price plans, boosts and credits with a worked 10-unit example and a checklist.
Short answer
Dating app subscription pricing has to start from what you keep after store fees and tax, because Apple and Google billing takes a share of every plan, boost and credit purchase. Set the member price so the net amount covers your costs, keep purchased credits non-expiring on iOS, and check current fee pages before you publish prices.
Key takeaways
- Price from what you want to keep: the member price must already include the store and tax share.
- Plans, boosts and credit bundles are different product types, and each follows its own store path and rules.
- On Apple, credits sold through in-app purchase cannot expire, so price bundles and promotions with that in mind.
- Subscriptions need clear terms before purchase and an easy way to cancel, which also protects your renewal rate.
- Fee percentages differ by program and country, so model with your real rates before you publish prices.
On this page 11 sections
- How store billing shapes dating app subscription pricing
- What you sell and how it is billed
- Subscription terms that protect your renewals
- Credits and gifts as consumables
- Example: what a 10-unit plan, a boost and a credit bundle leave you
- Building the plan ladder, trials and local offers
- Launching store billing and watching it afterward
- Web checkout, PayPal and price comparisons
- What to verify before you publish prices
- Common pricing mistakes on dating apps
- Fill in the pricing table for your own app

Dating app subscription pricing is set after store fees, not before them. Anything a member buys inside a dating app that unlocks features, such as a plan, a boost, credits or a gift, is a digital good, and Apple and Google expect it to be sold through their own billing. That billing carries a fee and tax share, so the price a member sees is not the amount you keep.
This post works through plan, boost and credit prices from the amount left after the store takes its share, with a worked 10-unit example. If you are building on a ready-made Bumble clone, the plans, in-app purchases and credits are in the product, and the pricing decisions below come before any code. Rules are described as of October 2026 and come only from Apple's and Google's own policy pages; check them before you submit. For the rule text across all creator apps, read our Apple and Google in-app purchase rules explainer; this post applies the rules to dating prices.
How store billing shapes dating app subscription pricing
Founders usually design pricing first and ask about payment later. On a dating app that order costs time, because the store path decides three things you cannot easily change afterward.
- What you can sell as what. A recurring plan, a one-off boost and a bundle of credits are different product types in each store, with different rules about expiry, restore and refunds.
- What you keep. Store billing carries a fee that comes out of every purchase. We do not quote percentages here because they differ by program and country and change; look up the current figures on each store's fee pages and build them into your plan prices.
- What you must show. Both stores require clear terms before purchase. Your paywall copy, trial wording and cancellation instructions are policy matters, not only design matters.
The question of how dating apps earn is in how dating apps make money. This post starts where that one ends: you have chosen the levers, and now you need to know how members pay for each one.
What you sell and how it is billed
Use this table as a first pass. It describes the standard path for each product type; confirm it against the current policy pages for your markets and accounts.
| What you sell | On iOS | On Android | On the web | Notes |
|---|---|---|---|---|
| Premium plan (recurring) | In-app purchase, auto-renewable subscription | Google Play billing, subscription | Your own payment method, subject to each store's rules on linking out | Must give ongoing value; clear terms and cancellation |
| Boost or similar one-off visibility | In-app purchase, consumable | Google Play billing, one-time product | Your own checkout | Show exactly what the member gets and for how long |
| Credits (virtual currency) | In-app purchase, consumable currency | Google Play billing, or an alternative where the program allows it | PayPal or another gateway | On Apple, credits sold by in-app purchase cannot expire |
| Virtual gifts bought with credits | Spent from the credit balance | Spent from the credit balance | Spent from the credit balance | The purchase is the credit bundle; the ledger tracks the spending |
| Ad-free option | Part of a plan or a one-off purchase | Same | Same | Treated like any other unlocked feature |
In the Bumble-style build, premium plans and in-app purchases go through the stores under your own accounts, and credits can also be bought on the website, or in the Android app with PayPal. Two cautions before you price around a non-store route.
On iOS, Apple's App Review Guidelines state that unlocking features or functionality, including subscriptions and in-game currencies, must use in-app purchase, and the listed exceptions in section 3.1.3 cover things such as reader apps, person-to-person real-time services and goods or services used outside the app, none of which describes a dating app's premium features.
On Android, Google's payments policy says Play billing is required for virtual currencies and subscription services, and it names dating among the subscription examples. It also describes alternative billing programs for developers in eligible countries who enroll and meet extra requirements. Whether your accounts and markets qualify is a question for the Play Console and for counsel, not for this post.
Subscription terms that protect your renewals
Apple's guidelines say an auto-renewable subscription has to deliver ongoing value over a term of at least seven days and work on all of the member's devices, with a clear description of what the member gets for the price. Google Play's subscription policy asks you to state the offer terms explicitly: how much the member is charged, how often and whether a subscription is required to use the app. It also requires an easy online way to cancel, and names must match the actual offer; a subscription named "Free Trial" is an example Google gives of a misleading label.
In the United States, the FTC's page on the Restore Online Shoppers' Confidence Act says sellers must clearly disclose all material terms of an online transaction and obtain the consumer's express informed consent to the charge. Other markets add their own duties. Ask counsel market by market; none of this is legal advice.
A practical paywall checklist
- Show the price, the billing period and the renewal in the same view as the buy button.
- Say what the plan unlocks in plain terms: unlimited swipes, boosts, location changes, analytics, enhanced visibility, an ad-free experience, whichever your admin has set.
- If you offer a trial or a local discount, state what the price becomes afterwards.
- Tell members where to manage or cancel, and offer a restore option for reinstalls.
The admin panel is where plan contents are set, which lets you change what a plan includes without a release. Each change to what a paying member receives is a change to the terms they agreed to, so keep a record of what each plan included on each date.
Credits and gifts as consumables
Credits and gifts are consumables: a member buys a bundle, spends it, and may buy again. The rules concentrate on how the balance behaves.
- Expiry. Apple's guidelines say credits or in-game currencies purchased with in-app purchase may not expire. If you want expiry as a business rule, apply it only to promotional credits you gave away, not to purchased ones, and check the wording with the store's current guideline.
- Restore. The same guideline asks for a restore mechanism for restorable in-app purchases. Consumable bundles that were spent are not restorable, but a balance that exists should survive reinstalling the app. Store the balance on your server tied to the member account.
- Ledger. Keep one clear record of every credit added, spent, refunded or granted, with dates and reasons. When a member says credits are missing, the ledger is your evidence and theirs.
- Clear prices. Show what a gift or a feature costs in credits, and what the credits cost in money, before the member confirms. Google's payments policy requires terms and pricing to be accurate and to match the billing screen.
- Refund wording. Do not write vague promises such as "credits are non-refundable" without checking that the statement is lawful where you operate. Say what happens to unused credits when an account is closed, and keep the wording consistent across the app, terms and support replies.
- Fraud. Credits are the part most exposed to chargebacks and stolen payment methods. Set limits, agree a refund routine and watch revenue reports. The admin panel includes fraud prevention controls and revenue reports for this purpose.
If your model also lets members go live and receive gifts, income sharing with hosts and payouts is a separate matter with its own rules. We set up payout flows for your build when your model needs them. For a deeper look at how a coin economy behaves under store rules in another category, see our post on app store billing for drama coins; the ledger principles carry over.
Example: what a 10-unit plan, a boost and a credit bundle leave you
These figures are illustrative and show the method. They are not real store fees or prices.
Say you plan a monthly plan at 10 in your local currency and the combined cost of store fees and tax comes to 30 percent for a particular member, a figure you would replace with the real number for your accounts. You keep 7 per subscriber per month before your own costs. Now say a boost costs 3 and the same 30 percent applies: you keep 2.10. A credit bundle priced at 5 leaves 3.50.
| Product | Price shown to member | Example store and tax share (30%) | Left for you |
|---|---|---|---|
| Monthly plan | 10.00 | 3.00 | 7.00 |
| Boost | 3.00 | 0.90 | 2.10 |
| Credit bundle | 5.00 | 1.50 | 3.50 |
Two things follow. First, price points are set before the fee: to keep 7 after a 30 percent share, divide by 0.70 and you get a price of 10. A boost that must leave 2.10 needs 3, and a credit bundle that must leave 3.50 needs 5. Second, test the same offer on the web only if the store's current rules allow your app to point to it; otherwise the comparison is not one you can run. The full model for how an operator combines these levers is on the how a Bumble-style app earns page, which covers plans, credits, gifts and local offers.
Building the plan ladder, trials and local offers
Once you know what each purchase leaves you, the next question is how many plans to show and how they relate. Most dating apps end up with a short ladder: a free tier that works well enough to produce matches, one paid plan that removes the daily friction, and sometimes a higher plan that adds visibility. Every extra rung is another product to configure in both stores, another line on the paywall and another case for support to explain.
Start with two paid options, not five
A founder with no conversion data cannot tell which of five plans members prefer, and a crowded paywall slows the decision. Begin with a single paid plan and offer two billing periods of it, such as monthly and a longer term. Read the first month of purchases, then decide whether a third option earns its place. The plan contents in the admin panel can be changed without a new release, so the ladder can grow once there is evidence for it. The Bumble clone features page lists what a plan can unlock, including unlimited swipes, boosts and location changes, so you can match each rung to something members can feel.
Decide where trials and discounts apply
Free trials and introductory prices are set in each store, under that store's rules, and the member sees them on the store's own purchase sheet as well as on your paywall. The two must agree. If the paywall promises a week free and the store sheet shows a different term, you create support tickets and risk a policy complaint. Write the offer once, in plain words, and copy it into the paywall, the store product description and the support macro.
Regional managers can offer local discounts and trial periods in this build, while admins keep overall control of monetization. That makes it practical to try a lower price in one city, watch the net revenue after fees, and only then copy what worked. Compare offers on the amount left after the store share, not on the sticker price, because a discount that lifts purchases but cuts the kept amount too far can be worse than no discount.
Read the ladder against your own costs
Take your monthly costs for hosting, moderation staff, support and marketing, and divide by the net amount per subscriber from the table above. The result is the number of paying members you need before the app covers its running costs. If that number looks out of reach for the market you plan to enter, adjust the price, the cost base or the market, not the store fee. The wider revenue design, including how credits and gifts sit beside plans, is covered on the Bumble clone business model page.
Launching store billing and watching it afterward
A launch sequence, step by step
Billing is easier to get right when it is built in a fixed order. This sequence works for a first release and avoids the usual rework.
- Open the developer accounts early. Both stores need identity checks, and the payment and tax profile in each console takes time to be accepted. Start this in the first week, not the week before submission.
- Write the product list on paper. For each plan, boost and credit bundle, record its type, its name, its price tier and what it unlocks. Names must describe the product, not the offer.
- Create the products in each store. Match the product identifiers to the ones the app expects. A single mismatched identifier is the most common reason a test purchase fails.
- Test with sandbox accounts. Buy every product at least once on each platform. Cancel a subscription, restore on a fresh install, and confirm the balance of purchased credits survives.
- Check the receipts reach your server. The balance and the plan status must be stored against the member account, so that a reinstall or a new phone does not lose them.
- Read the paywall as a stranger. Ask someone outside the team to find the price, the renewal period and the cancel instructions without help. If they cannot, a reviewer may not either.
- Submit with a review note. Explain how a reviewer can reach the paid features, and give them a test account if the app needs one.
Approval remains the store's decision and no vendor can promise it. What you can control is that the app does what the paywall says and that each rule discussed above has been checked against the current policy page. If a submission is rejected, read the stated reason, fix that one point and resubmit with a short reply.
Spotting billing problems before members complain
After launch, billing problems show up in numbers before they show up in reviews. Watch a small set of signals weekly, and you will catch most faults while they are cheap to fix.
| Signal | What it can mean | First thing to check |
|---|---|---|
| Purchases fall sharply after a release | A product identifier or paywall change broke the buy path | Run a test purchase on the new build in each store |
| Many members ask where their credits went | The balance is not tied to the account, or a restore step failed | Compare the ledger with the member's purchase history |
| Cancellations spike right after the first charge | The renewal terms were not clear before purchase | Re-read the paywall copy next to the buy button |
| Refund requests cluster on one product | The product description promises more than it delivers | Compare the description with what the plan really unlocks |
| Chargebacks from a few payment methods | Fraud on credit purchases | Set purchase limits and review the revenue report |
Keep a simple weekly note with the date, the number of purchases per product, the refund count and any change you shipped. Over a few months that note becomes the evidence behind every pricing decision, and it is the first thing counsel or an accountant will ask for if a dispute arises. If you are still comparing budgets, the Bumble clone development cost page sets out what is included before you plan the billing work.
Web checkout, PayPal and price comparisons
The website and the app are separate shops, and a member who buys credits on your website with PayPal and then spends them in the app is a common pattern. It is the reason a credits balance should live on your server, tied to the account, not to a device or a store receipt. Whether the app may mention or link to a cheaper outside price has been changing, so read the current text in both policies and in the explainer on Apple and Google in-app purchase rules; ask counsel before building a revenue plan that depends on a link-out.
Refunds affect net revenue too. Store-billed purchases are normally refunded through the store under its rules, so your support team should point members there. Gateway purchases, such as PayPal on the web, are yours to refund, and a member can dispute a charge with their payment provider. Write one refund policy that covers both routes.
Your accounts, your relationship
The Apple Developer and Google Play developer accounts, the payment and tax set-up in each store, and any gateway account for PayPal belong to you. You pay the fees, hold the member relationship and handle refunds and support. The stores decide whether to approve the app and its in-app products. See the Bumble clone features for the plans, purchases and admin controls that support this, and how a Bumble-style app earns for the wider revenue design.
What to verify before you publish prices
- Every digital item is in the store's product list with the right type: subscription, consumable or one-time.
- Prices, billing periods and renewal terms appear next to the buy button and match the store's billing screen.
- A restore purchases action exists and works on a fresh install.
- Purchased credits do not expire on iOS, and the balance is stored on your server.
- Free trials and discounts are named accurately and state the price afterwards.
- A test purchase for each product has been made in each store's sandbox.
Report and block tools, published contact details and in-app account deletion are separate submission checks; our post on dating app moderation covers the first two.
Common pricing mistakes on dating apps
- Planning margins on list price. Always model on what you keep after fees and tax.
- Selling credits through PayPal inside the iOS app. The guidelines describe in-app purchase as the route for in-app currencies.
- Letting credits expire silently. It breaks Apple's expectation for purchased credits and creates complaints.
- Naming plans for the offer, not the product. A plan called a free trial invites a rejection under Google's rules.
- Changing plan contents without a record. A member can say they bought something different from what they now have.
- Ignoring tax. Digital sales carry tax duties that vary by country; set up with your accountant before the first sale.
Fill in the pricing table for your own app
Whether you start from a white-label dating app like Bumble or something else, write down every item you plan to sell and fill in the table in this post for it: type, iOS path, Android path, web path. Then open the current Apple and Google pages and check each row.
Decide your target net amount, your refund wording and your credit expiry rule before you configure the plans in the admin panel. Our published pricing is on our pricing page, and the live demo lets you walk the paywall. If you want to confirm the payment set-up for your build, contact us and we will confirm the scope at kickoff.
GetFame is an independent vendor and is not affiliated with Apple, Google, Bumble, Tinder or any dating brand named here; the names describe a category of app or a platform you publish to. Store rules are described as of October 2026 from their own policy pages and change. This is not legal advice; ask counsel about consumer, tax and subscription rules in each market.
Questions and answers
How should I price a dating app subscription?
Start from the amount you want to keep per subscriber, then add the store and tax share, because the member price must already include it. As an example only, keeping 7 at a 30 percent share needs a price of 10. Use the real rates for your accounts from Apple's and Google's fee pages.
Can I use PayPal instead of store billing?
Store billing is the normal path for digital purchases in store-distributed apps. PayPal can serve a web checkout; alternative in-app billing and external links depend on each storefront, applicable program, entitlement and current terms. Confirm eligibility before implementing either route.
Do the stores take a cut?
Yes, the stores charge fees on purchases made through their billing, and the terms differ by program, product type and country. We do not quote percentages here because they change. Read Apple's and Google's current fee pages for your accounts and model your margins on those numbers, then price plans with the store fee already inside.
How do I handle refunds?
Store-billed purchases are usually refunded through the store, under its rules, not through your admin panel. For purchases you bill yourself, write a refund policy and follow local consumer law. Avoid vague promises about credits. Say plainly what is refundable, when, and how a member asks, and keep a record of each request and decision.
Can I sell credits on the web only?
You can sell on the web, but the app must follow each store's rules about what it shows and links to, and those rules vary by region and change. Some stores restrict steering members to outside payment. Check the current policy for your markets, and ask counsel before you make a web-only credit model the core of your design.
What if the app is rejected?
Read the reason in the store's message, fix the point and resubmit, or reply with an explanation. Common causes are missing report and block tools, unclear subscription terms, a missing restore option or payment flows that bypass store billing. Approval is the store's decision, and we cannot guarantee it. Test the billing path on a test build first.
Do members need to be told when a subscription renews?
They must be told the terms before they pay: price, billing period and how to cancel. Google Play's subscription policy requires clear terms and an easy online way to cancel, and Apple asks that you describe what the member gets for the price. Consumer law in your markets may add notice duties. Ask counsel what applies.
Sources
- Apple App Review Guidelines (in-app purchase, subscriptions and exceptions; also 1.2 and 5.1.1(v))
- Google Play: Payments policy
- Google Play: Subscriptions policy
- Google Play: User Generated Content policy
- FTC: Restore Online Shoppers' Confidence Act (ROSCA)
Checked in October 2026. Rules, fees and programme terms change; confirm on the source before you rely on them.