In-App Payment Restrictions and Competition Concerns

Introduction

In-app payment restrictions arise when a digital platform requires, strongly encourages, or technically constrains developers and merchants to use the platform operator's own payment system for transactions involving digital goods, subscriptions, virtual items, content, or services. The platform may prohibit alternative payment systems, prevent developers from directing users to external payment options, impose commissions on transactions, restrict payment-related APIs, or condition app distribution on compliance with its payment rules.

From a competition-law perspective, these practices can create concerns where a platform possesses substantial market power in app distribution, mobile operating systems, digital content distribution, payment processing, or user access. The central concern is that the platform can use control over one layer of the digital ecosystem to protect or extend its position into another market.

The principal competition issues include:

1. Tying and bundling of app distribution with payment processing.
2. Exclusion of competing payment providers.
3. Self-preferencing of the platform's payment service.
4. Anti-steering restrictions preventing developers from informing users about alternatives.
5. Excessive or discriminatory commissions.
6. Raising rivals' costs.
7. Foreclosure of innovative payment technologies.
8. Control over commercially valuable transaction data.
9. Network effects and ecosystem lock-in.
10. Restrictions on interoperability and external payment links.

1. Meaning and Structure of In-App Payment Restrictions

A typical digital ecosystem may contain:

Operating System → App Store → App Developer → Payment System → Consumer

A platform controlling the first two layers may impose rules affecting the fourth layer.

For example, an app-store operator might require:

"All purchases of digital content made inside the app must use the platform's payment system."

The platform may additionally prohibit the developer from:

• embedding another payment processor;
• providing an external payment link;
• informing consumers that cheaper alternatives exist;
• displaying alternative prices;
• using alternative billing APIs;
• offering subscriptions outside the platform;
• avoiding the platform's commission.

The restriction therefore can operate at several levels:

A. Technical restriction

The platform prevents alternative payment APIs from functioning effectively.

B. Contractual restriction

The developer agrees not to use competing payment systems.

C. Steering restriction

The developer cannot tell consumers that payment can be made elsewhere.

D. Economic restriction

The platform imposes a commission sufficiently high to make alternative payment arrangements commercially unattractive.

E. Access restriction

Failure to comply may result in app rejection, suspension, or removal from the app store.

2. Why In-App Payments Raise Competition Concerns

The competition problem is not simply that a platform charges a fee.

A payment commission can be legitimate compensation for:

• payment infrastructure;
• fraud prevention;
• security;
• billing;
• refunds;
• customer support;
• app distribution.

The competition concern arises where the platform uses control over app distribution or operating-system access to eliminate competing payment mechanisms.

The basic theory can be represented as:

Market power in app distribution

↓

Control over developer access to consumers

↓

Mandatory platform billing

↓

Exclusion of competing payment providers

↓

Reduced payment competition

↓

Higher commissions / reduced innovation / reduced consumer choice

Thus, the relevant competition question is:

Is the platform legitimately providing an integrated payment service, or is it using power in one market to foreclose competition in another?

3. Relevant Markets

Several relevant markets may need to be considered.

A. Mobile operating-system market

The platform may possess substantial power because developers cannot easily substitute one operating system for another.

B. App distribution market

An app store can constitute a separate economic environment because developers may require access to the store to reach users.

C. In-app payment-processing market

The platform's billing system may compete with:

• card networks;
• payment gateways;
• digital wallets;
• bank-transfer systems;
• alternative billing providers;
• cryptocurrency or blockchain payment systems where legally permissible.

D. Digital-content distribution

The platform may also control distribution of:

• games;
• music;
• video;
• subscriptions;
• e-books;
• virtual goods.

Market definition becomes especially important because competition authorities may examine the platform at multiple ecosystem layers simultaneously.

4. Tying and Bundling

One of the strongest competition theories is tying.

Suppose:

• Product A = app-store distribution;
• Product B = payment processing.

If a platform has substantial power over A and requires developers to purchase B from it, competitors in payment processing may be excluded.

The structure is:

App distribution power

→ Mandatory use of platform billing

→ Reduced access to payment market

→ Foreclosure of payment competitors

This may resemble traditional tying doctrine, although digital platforms create additional complications because the products are technologically integrated.

5. Anti-Steering Restrictions

Anti-steering provisions can be particularly significant.

An app developer may technically be free to use an alternative payment system outside the app, but if the developer is prohibited from telling users about that alternative, effective competition may still be substantially weakened.

For example:

"You cannot tell users that a subscription is cheaper on your website."

This prevents consumers from comparing alternatives.

Anti-steering restrictions therefore affect consumer information, not merely payment infrastructure.

They can:

• suppress price comparison;
• preserve platform commissions;
• reduce switching;
• prevent direct customer relationships;
• reinforce platform dependence.

6. Self-Preferencing

A platform may give its own payment service advantages unavailable to rivals.

Examples include:

• privileged API access;
• default integration;
• superior authentication;
• automatic billing;
• preferential placement;
• easier refunds;
• reduced technical friction;
• access to transaction data.

Even where third-party payment systems are formally permitted, such advantages may make genuine competition difficult.

The competition issue is therefore not only:

"Are competitors prohibited?"

but also:

"Are competitors placed at a systematic disadvantage by the platform's architecture?"

7. Excessive Commission Concerns

A platform may charge a percentage of every transaction.

Competition concerns may arise if:

• the platform possesses durable market power;
• developers cannot realistically avoid the payment system;
• the commission is substantially above competitive levels;
• the fee is unrelated to the value of the payment service;
• the platform prevents developers from negotiating alternatives.

However, high prices alone do not automatically establish an antitrust violation.

Authorities must normally examine market power, competitive conditions, costs, alternatives, entry barriers and the overall economic effects.

8. Network Effects and Lock-In

In-app payment markets have strong network effects.

More users → more developers → more applications → more users.

This creates a reinforcing ecosystem.

Once developers invest in:

• app-store compliance;
• platform APIs;
• subscriptions;
• customer accounts;
• payment integration;
• platform-specific software;

switching may become expensive.

Consequently, a payment restriction can become more powerful over time.

The platform may effectively transform:

technical dependence → contractual dependence → economic dependence.

9. Data Advantages

Payment systems generate commercially important information.

The platform may obtain information concerning:

• transaction frequency;
• consumer spending;
• subscription behaviour;
• product popularity;
• pricing;
• cancellation rates;
• consumer preferences.

If the platform's own downstream services benefit from this information while competing payment providers do not receive equivalent access, the platform may obtain an additional competitive advantage.

This can create a data-based foreclosure theory.

10. Key Case Laws

1. United States v. Apple Inc. (2024)

The U.S. government's antitrust litigation against Apple is highly relevant to the broader question of ecosystem restrictions.

The government alleged that Apple used contractual and technological restrictions to maintain monopoly power in smartphone markets, including restrictions affecting payment functionality, app distribution and alternative avenues for developers.

The case is important because it illustrates how competition law can examine interlocking restrictions across a digital ecosystem, rather than treating every contractual provision independently.

Principle

Where a platform possesses substantial ecosystem power, restrictions that suppress alternative distribution, payment or functionality channels may be assessed collectively for their exclusionary effects.

2. Epic Games, Inc. v. Apple Inc. (2021)

This is one of the most important cases concerning app-store payment restrictions.

Epic challenged Apple's requirement that digital transactions in apps use Apple's in-app purchasing system and Apple's restrictions against alternative payment mechanisms and steering.

The court rejected several of Epic's claims under federal antitrust law but found Apple's anti-steering provisions problematic under California's Unfair Competition Law and issued an injunction concerning them.

Competition significance

The case demonstrates that:

• app-store payment rules can have antitrust significance;
• anti-steering restrictions can independently affect competition;
• the distinction between payment processing and app distribution matters;
• market definition can determine the outcome of platform litigation.

Key lesson

A platform does not necessarily violate antitrust law merely because it requires its own billing system, but restrictions preventing consumers from learning about alternative purchasing channels can create a distinct competition concern.

3. European Commission — Apple App Store Practices

The European Commission's investigations into Apple's App Store practices provide an important European competition-law example.

The Commission examined Apple's rules affecting developers' ability to inform users about alternative purchasing possibilities and the terms imposed on developers using Apple's payment environment.

Competition significance

The case illustrates the application of Article 102 TFEU to digital gatekeepers where platform rules can restrict:

• alternative payment channels;
• developer steering;
• consumer choice;
• competing payment services.

The EU approach also demonstrates the increasing interaction between traditional abuse-of-dominance law and specialized digital-platform regulation.

4. Epic Games v. Google

Epic Games also brought competition litigation against Google concerning the Google Play ecosystem.

The dispute concerned Google's alleged restrictions relating to app distribution, billing systems and payments, including the economic relationship between Google Play's billing system and competing payment mechanisms.

A U.S. jury found Google liable on important antitrust claims concerning its app-distribution ecosystem.

Competition significance

The litigation demonstrates that:

• app stores may constitute economically significant gatekeeping infrastructure;
• payment rules can be examined together with distribution restrictions;
• alternative billing systems may be relevant to competitive analysis;
• contractual and technical restrictions can reinforce each other.

Key principle

Competition analysis should consider the combined effect of distribution and payment restrictions, rather than viewing them as isolated commercial terms.

5. Competition Commission of India — Google Android / Google Play Billing

The Competition Commission of India has examined Google's conduct concerning the Android ecosystem and Google Play's billing system.

The CCI considered Google's position in relevant markets involving Android mobile devices and app distribution and addressed concerns surrounding Google's billing policies and mandatory use of its billing system.

Competition significance

The Indian approach highlights several important issues:

• dominance in digital ecosystems;
• mandatory use of proprietary billing;
• exclusion of alternative payment processors;
• differential treatment of payment methods;
• leveraging of platform power;
• foreclosure of competing billing systems.

The matter is particularly important for Indian competition law because it demonstrates how Section 4 of the Competition Act, 2002 can address ecosystem-based exclusion.

6. European Commission v. Google Android (2018)

The Google Android decision is broader than in-app payments, but it provides an important legal framework for understanding ecosystem leveraging.

The European Commission found several contractual restrictions involving Android that were capable of reinforcing Google's position in related markets.

Competition significance

The case demonstrates the concept of leveraging dominance across interconnected digital markets.

The underlying lesson is applicable to payment restrictions:

A dominant platform cannot necessarily use contractual conditions surrounding one digital product to protect or strengthen its position in another competitive market.

7. Microsoft Corp. v. Commission (2007)

The Microsoft case concerned interoperability and the use of control over one technological layer to disadvantage competitors in adjacent markets.

Although it did not concern mobile in-app payments, it is highly relevant doctrinally.

The European courts accepted that technological restrictions can constitute abusive conduct where a dominant undertaking's control over an important technological input prevents effective competition downstream.

Relevance to payment systems

A platform-controlled payment API can function as an important technological gateway.

If access is restricted or competing systems are technically disadvantaged, the conduct may resemble other forms of technological foreclosure.

8. Bronner v. Mediaprint (1998)

The Court of Justice developed important principles concerning refusal to provide access to an essential facility.

Bronner established a demanding framework for when refusal by a dominant undertaking to provide access to an infrastructure can constitute abuse.

Relevance

Where an app-store platform controls indispensable technical infrastructure, developers may argue that access to certain APIs or payment functionality is indispensable.

However, the Bronner threshold is demanding. Mere commercial inconvenience is generally insufficient.

11. Comparative Case-Law Principles

12. Legal Theories That Can Apply

A. Abuse of Dominance

Where the platform is dominant, payment restrictions may constitute abusive conduct if they:

• exclude competitors;
• impose unfair conditions;
• restrict technical development;
• limit consumer choice;
• leverage dominance into adjacent markets.

B. Tying

The platform may effectively say:

"If you want access to our app-store customers, you must use our payment system."

This creates a potential tying theory.

C. Exclusive Dealing

A requirement that developers exclusively use the platform's payment service may resemble exclusive dealing.

The central question becomes whether the arrangement substantially forecloses competing payment providers.

D. Refusal to Deal

A platform may refuse to permit competing payment providers to access:

• payment APIs;
• authentication systems;
• subscription APIs;
• payment tokens;
• transaction interfaces.

The essential-facilities doctrine may become relevant, although its legal threshold varies by jurisdiction.

E. Self-Preferencing

The platform may prefer its own payment service through:

• default status;
• better technical integration;
• lower friction;
• preferential placement;
• superior data access.

F. Unfair Trading Conditions

A dominant platform may face scrutiny where payment conditions are:

• unreasonable;
• discriminatory;
• disproportionate;
• commercially coercive.

13. Consumer-Welfare Effects

In-app payment restrictions can affect consumers through several channels.

Higher prices

Developers may transfer platform commissions to consumers.

Reduced choice

Consumers may have only one payment option.

Reduced innovation

Payment startups may be unable to access app users.

Reduced privacy competition

Consumers may lose the ability to select payment providers based on privacy practices.

Reduced promotional competition

Alternative payment systems may offer:

• discounts;
• loyalty programs;
• cashback;
• alternative subscription arrangements.

A platform restriction can eliminate these competitive dimensions.

14. Effects on Developers

Developers can experience:

Increased costs

A commission may reduce developer margins.

Reduced flexibility

Developers cannot select the payment provider best suited to their business.

Reduced customer relationships

The platform may control billing and customer interactions.

Switching barriers

Developers may be unable to move payment infrastructure without restructuring their applications.

Reduced innovation

Alternative payment companies may have little incentive to develop new solutions for the ecosystem.

15. Small Businesses and Start-Ups

Payment restrictions can disproportionately affect smaller developers.

A large developer may have sufficient resources to:

• maintain multiple distribution channels;
• negotiate commercial arrangements;
• operate an independent website;
• absorb commissions.

A small developer may not.

Thus, mandatory billing can produce:

Platform dependency → higher marginal costs → reduced entry → weaker competitive pressure.

This makes payment restrictions particularly relevant to barriers-to-entry analysis.

16. Interoperability Concerns

Competition may improve when platforms allow interoperability with competing payment systems.

Possible forms include:

• standardized payment APIs;
• external payment links;
• alternative billing;
• payment-token portability;
• interoperable authentication;
• standardized subscription management.

However, interoperability can create legitimate concerns involving:

• fraud;
• cybersecurity;
• privacy;
• consumer protection;
• refunds;
• chargebacks.

Competition law therefore should not automatically require unrestricted interoperability.

The proper question is whether the restriction is objectively justified and proportionate.

17. Legitimate Business Justifications

Platforms may defend payment restrictions on grounds such as:

Security

Centralized billing can reduce fraud.

Privacy

The platform may argue that third-party processors increase data exposure.

Consumer protection

Centralized payment may simplify refunds and dispute resolution.

Quality control

The platform may claim that payment providers must meet technical standards.

Transaction integrity

A single billing system can simplify subscription management.

These arguments should be tested rather than automatically accepted.

The key competition question is:

Could the legitimate objective be achieved through a less restrictive method?

For example, instead of banning all third-party payment systems, the platform could establish:

• security certification;
• technical standards;
• audit requirements;
• fraud controls;
• disclosure requirements.

18. Proportionality Analysis

A competition authority can examine:

Step 1 — Legitimate objective

What does the restriction accomplish?

Step 2 — Necessity

Is the restriction actually necessary?

Step 3 — Less restrictive alternatives

Could security or consumer protection be achieved through certification?

Step 4 — Competitive effects

How many competing payment providers are excluded?

Step 5 — Consumer effects

Does the restriction increase prices or reduce choice?

Step 6 — Dynamic effects

Does it prevent future payment innovation?

19. Digital-Ecosystem Theory

In-app payment restrictions illustrate a broader phenomenon of ecosystem leveraging.

The platform does not necessarily need to monopolize payment processing directly.

Instead, it can control:

Operating system

↓

App store

↓

Developer access

↓

Payment rules

↓

Consumer transaction

This allows the platform to exercise architectural control over competition.

The competitive advantage therefore comes not merely from ownership of a payment company, but from ownership of the gateway through which competitors must reach consumers.

20. Algorithmic and AI-Enabled Payment Restrictions

Modern platforms may increasingly use algorithms to determine:

• transaction approval;
• payment routing;
• commission structures;
• fraud scores;
• merchant eligibility;
• app-store compliance.

AI can make exclusion less visible.

For example, a platform might technically permit competing payment systems but algorithmically:

• reduce app visibility;
• delay approvals;
• impose additional compliance requirements;
• flag alternative payment flows;
• downgrade apps using external billing.

This raises a new competition issue:

Can algorithmic implementation of payment restrictions constitute exclusionary conduct even when the written platform rules appear neutral?

The answer may depend on evidence of discriminatory effects, intent, market power and objective justification.

21. Remedies

Competition authorities may consider several remedies.

Structural remedies

In exceptional circumstances:

• separation of app distribution and payment functions;
• divestiture;
• organizational separation.

Behavioral remedies

More commonly:

• permit third-party payment systems;
• prohibit anti-steering clauses;
• permit external payment links;
• prohibit discriminatory API treatment;
• require transparent payment rules.

Interoperability remedies

Platforms may be required to provide:

• payment APIs;
• authentication interfaces;
• standardized billing interfaces.

Data remedies

Authorities may require restrictions on the use of payment data to prevent the platform from gaining an unfair downstream advantage.

22. Compliance Framework for Platforms

A platform seeking to minimize competition risk should consider:

1. Clearly define the relevant payment markets.
2. Permit technically viable alternatives where feasible.
3. Avoid unnecessary anti-steering restrictions.
4. Apply payment rules uniformly.
5. Separate security requirements from exclusionary requirements.
6. Document objective justifications.
7. Provide transparent API-access criteria.
8. Avoid discriminatory treatment of rival payment providers.
9. Monitor foreclosure effects.
10. Conduct periodic competition assessments.

Conclusion

In-app payment restrictions represent a major modern competition-law issue because app-store operators can combine control over distribution, operating systems, technical infrastructure and consumer access with control over payment transactions.

The central legal concern is not simply the existence of a proprietary payment system or the charging of a commission. The more serious concern arises when the platform uses gatekeeper power to suppress competing payment providers, prevent developers from steering consumers toward alternatives, discriminate against rival payment systems, or leverage dominance from app distribution into payment processing.

The cases involving Epic Games v. Apple, Epic Games v. Google, Google Play Billing, the EU's Apple App Store proceedings, Google Android, Microsoft v. Commission, and Bronner demonstrate the principal doctrinal tools available to competition authorities and courts.

The emerging principle is increasingly clear:

Control over a digital gateway should not automatically become control over every competitive service accessible through that gateway.

Accordingly, competition analysis should examine the entire ecosystem, including technical architecture, contractual restrictions, payment economics, data advantages, network effects, switching costs, interoperability and consumer choice, while also recognizing legitimate concerns relating to security, privacy and consumer protection.