In-app purchase rules are one of the most consequential and most fast-moving parts of dating app monetisation. This guide explains how they work and why they matter, with the clear caveat that the detail is changing.

A note on a changing area

Before anything else, a caveat that matters more here than in almost any other guide: this is a fast-changing area, and the specific rules should always be checked against the current position.

The rules governing in-app purchases, the app stores' commissions, and what app makers may and may not do around payments have been the subject of sustained legal action, regulatory intervention and policy change for years, and that process is ongoing. Courts in various jurisdictions have ruled on aspects of it. Regulators, including under major competition and digital-markets regimes, have intervened. The app stores themselves have changed their policies in response, sometimes more than once. The picture in one country can differ from the picture in another.

This means a guide written at one moment cannot be a reliable statement of the exact current rules, and this one does not try to be. What it can do, and what it does, is explain the concepts, the structure of how in-app purchases and commissions work, why they matter for a dating app's economics, and the direction the rules have been moving, so that an operator understands the topic well enough to grasp its effect on their business and to ask the right questions.

For the specifics, what the current commission rates are, what the current rules permit around alternative payment and steering, what differs by jurisdiction, an operator should rely on current sources: the app stores' current policies, current reporting, and, on a platform, the provider, whose job it is to track and comply with the current rules.

With that caveat firmly in place, the rest of the guide explains the concepts an operator should understand.

What in-app purchases are

An in-app purchase is, simply, a payment made by a member from inside a mobile app.

When a dating app is distributed through Apple's App Store or Google Play, and a member uses that app on their phone, the app can offer the member things to buy: a subscription, a premium tier, credits, boosts, the various monetised elements the rest of the monetisation guidance describes. A purchase the member makes from inside that app is an in-app purchase.

The key fact about in-app purchases is that the app stores have historically required a particular thing: that purchases of digital goods and subscriptions made inside an app go through the app store's own in-app purchase system. That is, the payment is not processed by the app maker's own payment system; it is processed by Apple's or Google's in-app purchase mechanism. The member pays through the app store, and the app store passes the money on to the app maker, minus a commission.

This is the heart of the topic. "In-app purchase," in the sense that matters for this guide, is not just "a purchase made in an app"; it is "a purchase made through the app store's own payment system, on which the app store takes a commission." That mechanism, and the commission attached to it, is what makes in-app purchase rules a genuine monetisation issue for a dating app rather than a technical detail.

For an operator, the starting point is to understand that a dating app distributed through the mobile app stores has historically had to route the purchases members make inside it through the app stores' own systems, and that this routing comes with a commission, which the next sections explain.

The app store commission

The commission is the core of why in-app purchase rules matter, and an operator should understand what it is.

When a purchase goes through an app store's in-app purchase system, the app store takes a percentage of that purchase as a commission, and passes the remainder to the app maker. This commission has historically been a significant percentage, large enough to be a major factor in the economics of any app that sells digital subscriptions, and dating apps, being largely subscription businesses, are squarely affected.

The exact commission rate is one of the specifics that the changing-area caveat applies to. The headline rate has historically been substantial; there have been reduced rates for smaller developers and for certain situations, such as subscriptions that have continued for a longer period; and the rates and the structure have been among the things subject to change under the legal and regulatory pressure described later. An operator should treat the precise current numbers as something to check against current sources, not as something a guide can fix in place.

What does not change, and what an operator should hold onto, is the principle: when a purchase goes through the app store's in-app purchase system, a meaningful slice of that revenue is taken by the app store before the app maker sees it. For a subscription dating app, that slice comes off subscriptions, the core revenue, and it comes off them for as long as the rules require those subscriptions to be sold through in-app purchase.

For an operator, the commission is the thing to understand: app store in-app purchase carries a significant commission, it applies to the subscription revenue that is a dating app's lifeblood, and its exact size is a current-rules question, but its existence and its materiality are not in doubt.

Why the commission matters for dating

The commission matters for a dating app specifically, and an operator should understand why it is not just a generic app cost but a genuine factor in dating economics.

A dating app, as the pricing and monetisation guidance establish, is largely a subscription business. Its revenue comes from members paying recurring subscriptions, and the whole compounding model the analytics guidance describes runs on that subscription revenue. The commission applies to exactly that revenue. Every subscription sold through app store in-app purchase has the commission taken off it.

This interacts with the white label revenue share. A white label operator, as the white label guidance describes, already shares revenue with the provider, typically keeping the majority. If a subscription is also sold through app store in-app purchase, the app store commission is taken as well. The operator's economics, then, can be shaped by more than one layer: the app store's commission, and the operator-provider revenue share. An operator should understand their economics with a clear view of which layers apply to which sales.

The commission also interacts with pricing. The pricing guidance describes setting a price that reflects value, audience and positioning. The commission affects what the operator and provider actually net from that price when a sale goes through in-app purchase, which is part of the economic picture an operator should understand when thinking about pricing.

And the commission is what gives the web-versus-app distinction, covered next, its significance. Because purchases made through the web typically have not carried the app store commission, while purchases made through in-app purchase have, where a member pays becomes an economically meaningful question.

For an operator, the lesson is that the in-app purchase commission is not a trivial platform fee; it is a genuine factor in the economics of a subscription dating business, interacting with the revenue share and with pricing, and worth understanding clearly rather than ignoring.

What has had to go through in-app purchase

A natural question is exactly which purchases have had to go through app store in-app purchase, and the broad answer, with the changing-area caveat applied, is digital goods and subscriptions consumed within the app.

The app stores' in-app purchase requirement has applied to digital content and services, the digital subscriptions, premium tiers, credits, boosts and similar digital items that a dating app sells, when those are sold to a member using the app. A dating subscription that unlocks the app's paid features is exactly the kind of digital subscription the requirement has covered.

What has generally fallen outside the in-app purchase requirement is physical goods and services consumed in the real world, which is not relevant to most dating apps, and, importantly, purchases not made through the app, which the web-versus-app section addresses.

The dividing lines here, what counts, what does not, what an app may and may not do around the boundary, are among the things that have been contested and that have shifted. An operator should not treat any precise account of the boundary as fixed.

The practical point for a dating operator is that the core of what they sell, the digital subscription and the digital monetised elements, is squarely the kind of thing the in-app purchase requirement has applied to when sold inside the app. There is no realistic argument that a dating subscription is outside the category of digital goods the app stores' rules address. So a dating app distributed through the app stores has had to engage with the in-app purchase requirement for its core revenue, and that is the situation an operator should understand.

For an operator, the takeaway is that the digital subscriptions and digital items a dating app sells are exactly what the in-app purchase rules cover when sold within the app, so this is not a topic a dating operator can sidestep on the grounds that it does not apply to them.

The web versus app distinction

The most strategically important concept in this whole area is the distinction between a purchase made inside the app and a purchase made through the web, and an operator should understand it clearly.

The in-app purchase requirement, and its commission, has applied to purchases made inside the mobile app. A purchase a member makes through a website, in a normal web browser, is a different thing. A web purchase is processed through the operator's or provider's own payment system, the kind of payment processing the payment-systems guidance describes, and it has typically not carried the app store commission, because it did not go through the app store.

This creates a genuine and significant distinction. The same member, buying the same dating subscription, can do so in two ways with different economics. If they buy it inside the iOS or Android app, the purchase goes through app store in-app purchase and carries the commission. If they buy it through the dating service's website, in a browser, it goes through the ordinary payment system and typically does not.

This is why so much strategic attention in app monetisation has gone to where members pay. An app maker that can have members subscribe through the web rather than through in-app purchase keeps the commission. This is the background to a great deal of the legal and regulatory contest described in the next section, much of which has been about whether, and how far, an app may tell members inside the app that they can pay elsewhere, the question often called steering.

The historical position, broadly, has been that members could buy through the web, and that web purchases avoided the commission, but that the app stores placed significant restrictions on what an app could do inside itself to point members toward web payment. Exactly what those restrictions are, and how much they have been loosened by courts and regulators, is precisely the moving part the next section and the changing-area caveat address.

For an operator, the essential concept is the web-versus-app distinction: where a member pays has historically determined whether the app store commission applies, and that distinction is the hinge of the whole strategic picture.

The shifting rules

The rules around in-app purchase, commissions and steering have been shifting for years under legal and regulatory pressure, and an operator should understand the direction even though the specifics are a current-sources question.

The pressure has come from several directions at once. There has been major litigation, with app makers, including prominent ones in adjacent and overlapping spaces, challenging the app stores' in-app purchase requirements and commissions in court, and courts in various jurisdictions reaching findings that have affected what the app stores may do. There has been regulatory intervention, with competition and digital-markets regulators in major jurisdictions scrutinising and acting on the app stores' practices; large digital-markets regimes have specifically addressed app store rules. And there has been resulting policy change, with the app stores adjusting their rules, commissions and steering policies in response, sometimes differently in different regions.

The broad direction of all this pressure has been toward loosening the app stores' historically tight control: toward more ability for app makers to tell members about alternative ways to pay, more room for alternative payment options in some contexts and jurisdictions, and in some places changes to commission structures. But the picture is genuinely uneven, it differs by jurisdiction, it has moved in steps rather than smoothly, and it is not finished.

The honest position for this guide is the one the changing-area caveat set out: an operator should understand that the rules have been moving in the direction of loosening the app stores' grip, but should not rely on any guide for the precise current state. What an app may currently do around steering and alternative payment, what the current commission position is, and how it differs by region, are questions for current sources and, on white label, for the provider.

For an operator, the takeaway is to understand the area as genuinely dynamic: the rules have been contested and are loosening, the direction matters strategically, but the specifics must be checked current, and an operator who learned the rules a year ago should assume they may have changed.

Strategic implications for an operator

What does all of this mean, strategically, for a dating operator. There are a few genuine implications an operator should carry, holding the changing-area caveat throughout.

The first is that where members pay has economic consequences. Because of the web-versus-app distinction, an operator's economics are affected by whether members subscribe through the app or through the web. An operator should understand their own economics with that distinction in view, rather than treating all subscriptions as economically identical.

The second is that the web channel matters. The operator-owned marketing the operator already controls, the landing pages, the marketing site, the about page, the advertising, is also a web channel through which members can be brought to subscribe via the web. An operator who is building a strong web acquisition and conversion presence, as the landing-page and conversion guidance encourage, is, among other things, building a channel whose payment economics differ from the in-app channel. This is one more reason the operator's web marketing footprint matters.

The third is that pricing and economics should be understood with the commission in view. As the why-it-matters section noted, the commission interacts with the revenue share and with pricing. An operator should understand their net economics across the channels, rather than being surprised by the effect of the commission on in-app sales.

The fourth is that this is a topic to keep watching. Because the rules are shifting, the strategic picture can change. An operator does not need to track every development personally, on white label the provider does that, but an operator should be aware that the in-app purchase landscape is one that genuinely moves, and should expect their provider to be on top of it.

The fifth, and steadying, implication is that an operator should not let this topic dominate. It is a genuine factor in economics, but it is one factor. The fundamentals the rest of this guidance describes, a good niche, genuine value, honest monetisation, real conversion and retention, matter more to whether a dating business succeeds than the precise handling of app store commission.

For an operator, the strategic guidance is: understand the web-versus-app distinction and its effect on economics, value the web channel partly for that reason, know your net economics with the commission in view, expect the rules to keep moving, and keep the topic in proportion against the fundamentals.

What white label handles for you

On a white label platform, the handling of app store rules and in-app purchase compliance is the provider's responsibility, which is a genuine and substantial benefit, given how complex and fast-moving the area is.

The provider builds and distributes the apps. On a typical white label arrangement the apps are published and maintained by the provider, as the development guidance notes. That means the provider is the party that deals with the app stores: that complies with their rules, that implements in-app purchase where it is required, that handles the steering and alternative-payment rules within whatever the current position permits, and that tracks the shifting landscape and keeps the platform compliant as the rules change.

This is a real benefit. The in-app purchase area is, as this whole guide has stressed, complex, consequential and genuinely fast-moving. An independent operator distributing their own dating app would have to understand and comply with all of it themselves, and keep up as it changes. On white label, that specialist, moving compliance burden sits with the provider.

What the operator should do is understand and confirm. The operator should understand, as this guide has explained, how the commission and the web-versus-app distinction affect their economics, so they are not surprised by their own numbers. And the operator should, when assessing a provider, confirm that the provider genuinely handles app store compliance competently and stays current with the changing rules, and should understand how the in-app purchase commission interacts with the revenue share in the provider's arrangement, so the operator has a clear view of their net economics across channels.

For an operator, the guidance is: the provider handles the app store rules and in-app purchase compliance, which spares the operator a complex and shifting burden; the operator's job is to understand the economic effect of the commission and the web-versus-app distinction on their own business, and to confirm the provider handles this area competently and keeps it current.

Common mistakes

The defining mistake is treating in-app purchase rules as an irrelevant technical detail, when the app store commission is a genuine factor in the economics of a subscription dating business.

The second is relying on a fixed account of the rules, when this is one of the fastest-moving areas in app monetisation and the specifics, commission rates, steering rules, what differs by jurisdiction, must be checked against current sources.

The third is ignoring the web-versus-app distinction, and so not understanding why where members pay affects the operator's economics.

The fourth is failing to understand how the app store commission interacts with the white label revenue share, leaving the operator without a clear view of their net economics across channels. The fifth is the opposite, letting this topic dominate strategic thinking, when it is one factor and the fundamentals of niche, value, honest monetisation, conversion and retention matter more. Understand it, keep it current, keep it in proportion.

For the payment system behind web purchases, read dating site payment systems and PSPs. For pricing in light of the economics, see how to price a new dating site. For the web channel, read how to write a dating site landing page that converts. And to understand how a provider handles app store compliance and revenue share, DatingPartners.com can walk through it.

Recommended next step

DatingPartners handles IAP, DMA rails and refund tooling. Stay compliant without rebuild.

Visit DatingPartners.com →