How Dating Apps Can Cut Apple and Google App Store Fees With Web Subscriptions

Dating apps depend on renewals. A member signs up in March, sticks around for eight months, and the app store takes a cut from every payment during that time. That makes subscription billing very different from selling a one-time download. You are not paying a commission once and moving on. The fee keeps coming back with every renewal, growing as the subscriber base you worked to build grows.

So the fix looks simple: sell memberships on your own site and keep more of each charge. Then the harder questions show up. Do Apple and Google let you send members off-platform, and under what conditions? Who tracks attribution once money changes hands outside the store? Will a browser checkout convert at anywhere close to the level of trust that native purchase members already have?

Let's break down what a web subscription actually is, what the two stores currently permit, and what needs to be running behind the scenes before a dating app makes the move.

Why App Store Fees Hit Dating Apps Harder Than Most Subscription Categories

The two stores no longer work from the same baseline. Apple still starts at 30%. Google Play does not. 

The two stores no longer work from the same baseline. Apple still starts at 30%. Google Play does not.

Apple. Standard commission is 30% on digital goods. It drops to 15% under the App Store Small Business Program, open to developers who earned under $1 million in proceeds in the prior calendar year. Proceeds means what you keep after Apple's cut, not gross consumer spend, so at 15% the real ceiling sits closer to $1.18 million in sales. Cross the threshold mid-year and standard rates apply to future sales. Apple also drops to 15% on any subscription once the member has paid for a full year.

Google Play. Google replaced its fee structure on 30 June 2026 following its settlement with Epic. Auto-renewing subscriptions are now 10% for every developer, from the first billing cycle. Other in-app purchases are 20% for members who installed on or after that date and 25% for members who installed before it. The first $1 million in annual earnings is 10% across the board. Use Google Play Billing, and a separate 5% billing fee applies on top. Use alternative billing or an external web link, and it does not apply.

The rollout is staggered, so where your members are matters. The new rates took effect on 30 June 2026 in the US, UK and EEA. Australia and Japan follow on 30 September 2026, Korea on 31 December 2026, and the rest of the world on 30 September 2027. An app serving mostly outside those first three markets is still on the old rates today.

Lifetime value gets taxed, not the initial sale. A member who stays twelve months is charged twelve times, and the store takes a cut on each one. The rate is not flat across that curve: Apple charges 30% or 15% for the first year and 15% after; Google charges 10% throughout. But the fee never stops, and it scales with exactly the thing you are trying to grow. 

Stack that against dating economics. Paid acquisition in this category is expensive and getting more so.

A meaningful share of new members churn inside the first month, before their subscription earns back what it cost to acquire them. Net margin after ad spend is already thin.

So the platform fee competes for the same dollars that fund your next cohort of installs.

Web subscriptions are one lever against that pressure. Pricing structure, retention, and dispute control are others, and most operators need more than one working at once.

3 Ways Dating Apps Can Handle Web Subscriptions

“Web subscription” can mean a few different things. Each setup comes with its own fees, rules, and risks. So before going further, it helps to look at what each one actually involves.

Standalone Web Checkout 

A member discovers your site through search, social, or a marketing email, subscribes in a browser, and then logs in to the app with those credentials. No link from inside the app points them there. Apple and Google have no claim on the transaction and no fee attached to it, because the purchase never touched their storefronts.

In-app External Purchase Link 

A button or notice inside the app sends the member to a web checkout. This one still lives under store policy. It requires an entitlement or program enrollment, specific disclosure screens, transaction reporting, and, in most regions, a commission still applies to purchases attributed to that link.

Alternative Billing Inside the App

The member picks a non-store payment method without leaving the app. This is mostly a Google Play mechanism today. The store still charges a service fee, reduced by a set amount, and the developer still reports the transactions.

Sitting above all three is the web-to-app funnel: acquiring or converting subscribers in a browser, then syncing entitlement into the native app so the member's paid status follows them. That pattern is what makes standalone web checkout viable at scale.

What Apple and Google Allow for Web Subscriptions in 2026

Apple and Google's external payment rules are products of litigation, including Epic v. Apple and Epic v. Google, as well as regulatory pressure, such as the EU's Digital Markets Act. Terms have shifted quarterly, and they differ by country. Confirm current policy on Apple's and Google's own developer pages.

Apple

Qualifying apps can use Apple's StoreKit External Purchase Link Entitlement to send members to a web checkout. Terms vary by storefront.

Three things to know about the rules:

• The United States, the EU under the DMA, and other regions each operate under separate rulesets.

• Apple has revised the US terms. Following court rulings in the Epic Games antitrust litigation, Apple is currently blocked from charging a commission in the US storefront.

• Check Apple's external purchase link documentation for what applies to your markets.

The link does not automatically mean fee-free. In several regions, Apple applies a commission to purchases attributed to an external link within a defined window after the tap. Developers also have to report those transactions on a fixed schedule.

Dating apps are already in a distinct regulatory bucket. Apple ran a dating-app-specific entitlement in the Netherlands after an order from the Dutch competition authority.

That is a useful signal. Regulators treat the dating category separately rather than lumping it in with all subscription software.

One operational catch worth flagging early. In some regions, adopting an external purchase entitlement limits whether the app can keep offering standard in-app purchase alongside it. It is not always additive, and that changes the migration math.

Google Play

Google runs two programs worth knowing:

• User choice (alternative) billing: Members pay through a non-Google method without leaving the app.

• External content links: You point members to a web purchase page. Under the external content links program, Google charges an app download event fee for an install occurring within 24 hours of a link click.

Both require enrollment through the Play Console. A design change on your side is not enough.

Google has also moved toward a service fee plus billing fee structure. It applies to subscriptions no matter which payment method the member picks. The lower tier is tied to a developer's first $1 million in annual revenue.

Percentages shift, so skip the secondhand numbers. Pull them straight from Google's service fee schedule and the alternative billing help pages.

One more thing. Reporting duties and fee effective dates have already changed at least once.

Someone on your team needs to track that on an ongoing basis. This is not a launch-and-forget setup.

How to Build a Compliant Web Subscription Setup, Step by Step

1. Audit Your Subscriber Base by Storefront and Region 

Before choosing a program, look at where your revenue is really coming from. You may find that just two markets make up most of your fee exposure.

2. Pick Your Model 

Standalone web checkout puts you furthest from app store policies, but it usually brings in less traffic. In-app links can drive much more volume, but they also come with more rules around entitlements. 

The right choice comes down to how much risk you can take on and how much engineering work your team can handle.

3. Build or Buy the Attribution and Reporting Pipeline 

If you use in-app links, you need to track each purchase back to the tap that led to it and report it within the required time.

4. Line Up a Processor Built for Recurring, High-Dispute Billing 

A generic payment facilitator may limit your volume or shut down your account if chargebacks start to climb. For dating apps, solid underwriting matters more than finding the lowest rate.

5. Design the Required Disclosure Screens

Apple presents a system sheet before a member leaves the app, and copy requirements differ by region. Get this reviewed before submission, not after a rejection.

6. Set Up Dunning, Failed-Payment Recovery, and Self-Serve Cancellation 

A hard-to-find cancel button is a common reason dating subscription disputes turn into chargebacks. Make the cancellation process easy to find and use, and you can avoid many frustrated members and unnecessary refunds.

7. Schedule a Quarterly Compliance Review 

These rules can change, so keep an eye on them. Put a recurring calendar reminder on someone’s schedule, and give them the authority to pause the program if the terms change.

Real Risk Points Before Moving Dating App Subscription Billing to the Web

App Review and Entitlement Risk

A misconfigured link, a missing disclosure screen, or an entitlement enabled in the wrong storefront is a common cause of rejection. Entitlements can be revoked, and losing one mid-quarter takes your web funnel offline with little warning.

Attribution and Reporting Risk 

Both stores require transaction reports on a set schedule after a purchase originates from an in-app link. Late or incomplete reporting can trigger fees, audits, or removal from the program.

Regional Fragmentation 

Rules split by storefront and country. A dating app operating across North America, the EU, and Asia may need three different purchase paths rather than one universal checkout, which multiplies engineering and QA work.

Dispute Exposure Moves to You 

Inside store billing, the platform handles a share of refunds and complaints. On a web checkout, your team and your processor own fraud screening, refund policy, and chargeback responses. Dating already has elevated rates of friendly fraud. A partner spots a charge on a shared statement, or a renewal posts after someone quietly stopped using the app, and a dispute follows. 

Our guide to managing chargebacks for dating platforms covers how those cases tend to play out.

Processor Risk 

Plenty of mainstream payment facilitators decline dating and dating-adjacent merchants outright, or approve them and then freeze the account once dispute ratios climb. A web subscription strategy only works if the high-risk merchant account underneath it stays open.

Weighing Margin Gains Against Operational Cost

On one side, the commission you avoid. On the other is the cost of running payments yourself:

• Processing rates

• Fraud tooling

• Refund handling

• Extra support tickets

• Engineering hours to keep entitlement syncing across web and app

Sending someone from a native purchase sheet to a browser checkout usually converts at a lower rate at first. Card entry friction is real. So fee savings have to outrun subscriber loss during the transition, and it may take a few tests before that happens.

The practical takeaway: this pays off for apps with a large, stable paying base and the legal plus engineering capacity to keep it compliant. For a smaller app still working out retention and pricing, the overhead usually costs more than the commission it saves.

Choosing a Payment Partner That Understands Dating App Risk

The Stripe, PayPal, and Square tier is built for low-dispute, low-complexity merchants. Dating is neither.

Those platforms screen out the exact profile a dating app fits:

• Elevated chargeback ratios

• Recurring billing edge cases

• Privacy-sensitive statement descriptors

Approval today does not mean a stable account next quarter.

What a dating platform needs instead is online dating payment processing with underwriting built for recurring volume and the category's dispute patterns.

In practice, that looks like:

• Discreet billing descriptors, so a renewal does not create a problem at home

• Chargeback prevention tooling that catches complaints before they turn into disputes

• Membership billing tools that match the in-app experience

Upgrades, downgrades, one-click upsells, and clean cancellations all need to work in the browser. The MobiusPay Gateway handles that side.

Weighing this move? Talk it through with a payments team that already runs dating volume. 

Summing Up

External payment rules will continue to shift as litigation and regulators push both stores in new directions. What works in your US build may not apply in the EU next quarter, so reconfirm the current terms right before you ship, not just while you plan. Build the reporting and dispute infrastructure first, and policy changes become adjustments rather than emergencies.

Ready to figure out what's behind your web checkout needs? Reach out to MobiusPay, and we will walk you through it.