External Payments Are Allowed, But Apple Still Controls the Checkout

The new payment reality is not a free-for-all

Apple’s temporary removal and reinstatement of Cal AI is the clearest practical signal yet for subscription apps testing external payment flows on iOS: the door is more open than it used to be, but Apple still controls the frame around that door.

The issue was not simply that the app pointed users toward a non-Apple payment option. In the U.S., many developers can now link to external purchase paths. The problem was the total checkout experience: Apple determined that Cal AI bypassed the required in-app purchase option, used confusing billing presentation, and applied manipulative subscription tactics.

For ASO and mobile growth teams, this matters because monetization design is no longer separable from store compliance. A paywall is not just a revenue surface. It is now a review-risk surface, a ratings-risk surface, and, in extreme cases, an availability-risk surface.

The lesson is straightforward: alternative payments may reduce platform fees in some scenarios, but a poorly implemented flow can cost visibility, trust, conversion, and store presence.

What Apple objected to

Cal AI, a fast-growing calorie-tracking app owned by MyFitnessPal, briefly disappeared from the App Store after introducing a checkout experience that pushed users toward an external subscription purchase path. The app later returned after addressing the issues.

Apple’s enforcement centered on three areas:

• Bypassing Apple’s in-app purchase flow. For non-reader apps, Apple still requires its own in-app purchase option to be available alongside external payment links. Cal AI did not present the required IAP path in the way Apple expects.
• Deceptive billing presentation. The paywall emphasized a weekly calculated price more prominently than the actual amount the user would be billed. That creates obvious consumer-confusion risk, especially for annual or multi-period plans.
• Manipulative subscription tactics. The app used a free-trial toggle that did not make automatic renewal sufficiently clear and presented users who declined one offer with another subscription flow.

Those are not edge-case technicalities. They map directly to the core App Store rules around purchasing, subscriptions, and developer conduct. In practice, Apple is treating checkout clarity as part of wiki:app-review-guidelines, not merely as a design preference.

External payment permission still has categories and conditions

The most important distinction for developers is the one between apps that qualify as reader apps and apps that do not.

Reader apps — services built around access to previously purchased or subscription-based content such as books, music, video, audio, and similar media — have a different set of permissions around linking out. A calorie-tracking app does not fall into that bucket.

For most non-reader apps selling digital goods or subscriptions, the current operating model is:

• External payment links may be allowed in certain markets and contexts.
• Apple’s in-app purchase option must still be offered where required.
• The external path cannot be embedded in a way that functions as a hidden replacement for IAP.
• Pricing must be clear, complete, and not engineered to obscure the real charge.
• Trial terms and renewal behavior must be obvious before purchase.

This is the key strategic point: Apple is not only enforcing the existence of wiki:in-app-purchase. It is enforcing the comparative fairness and user clarity of the full purchase journey.

The paywall is now a compliance artifact

Subscription teams often treat paywalls as pure conversion machinery: test the headline, anchor the discount, compress the decision, add urgency, and reduce friction. That mindset is now incomplete.

A modern iOS paywall has to satisfy four stakeholders at once:

• The user, who needs to understand what they are buying.
• The growth team, which needs a viable conversion rate.
• The finance team, which cares about net revenue after fees.
• App Review, which evaluates whether the flow is compliant and fair.

The more aggressive the paywall, the higher the review risk. That risk increases when an app combines external payments with pricing psychology that would already be sensitive inside a standard IAP flow.

We are seeing a sharper line form around several practices:

• Showing “per week” pricing while billing annually.
• Making the billed amount visually secondary.
• Using trial toggles that conceal renewal terms.
• Re-prompting users with materially different offers after refusal.
• Designing external checkout to feel like the only available option.
• Moving subscription terms outside the user’s immediate field of attention.

None of these are new growth tactics. What is new is the enforcement context. When external payments are involved, Apple has additional incentive to scrutinize whether the app is using payment-choice flexibility to undermine platform rules or consumer understanding.

ASO teams should care because enforcement affects demand capture

It is tempting to treat this as a billing operations issue. That would be a mistake.

Store interruption has direct ASO consequences. Even a short removal can disrupt:

• Search conversion and ranking momentum.
• Category chart performance.
• Paid acquisition landing consistency.
• Brand search confidence.
• Review velocity and review sentiment.
• Subscription funnel measurement.
• Lifecycle campaigns that depend on store availability.

Cal AI returned to the store and remained highly visible in Health & Fitness, but not every app will absorb a removal cleanly. Smaller apps with less brand demand, weaker paid support, or fragile ranking positions can lose momentum quickly.

The risk is especially acute for apps in competitive subscription categories: health, fitness, education, productivity, finance, photo editing, and AI utilities. In these categories, users already compare many similar products, and trust signals shape install decisions. Confusing billing reviews can damage both conversion rate and long-term wiki:app-store-policy resilience.

What compliant external payment design should look like

Developers pursuing external payment options should stop asking only, “Can we link out?” The better question is, “Can a reasonable user clearly understand every available purchase path and its consequences?”

If Apple’s rules require IAP alongside an external option, do not bury IAP. Do not make it visually weaker, harder to find, or functionally incomplete. The user should be able to choose without being steered through dark-pattern layout.

2. Prominent actual billing amount

If the user will be billed monthly, quarterly, or annually, that amount must be obvious. A calculated weekly equivalent can be useful, but it should not dominate the actual charge.

A safer hierarchy is:

• Plan name.
• Billing period.
• Total amount charged today or after trial.
• Renewal cadence.
• Optional equivalent price breakdown.

3. Explicit renewal language

Free trials remain a major source of subscription complaints. If a trial converts automatically, say so in plain language near the action button. Avoid placing renewal details in low-contrast text, expandable sections, or post-purchase screens.

4. Consistent offer logic

Second-chance offers can work, but they need to be handled carefully. If a user declines a subscription, pushing them immediately into a different flow can look coercive. If the follow-up offer has different terms, those terms must be just as clear as the first offer.

5. Review-ready documentation

Teams should prepare App Review notes for any external payment implementation. Explain:

• Which markets the flow appears in.
• Whether the app is a reader or non-reader app.
• Where IAP is presented.
• How subscription terms are disclosed.
• How users manage or cancel each purchase type.

This is not bureaucracy for its own sake. It reduces ambiguity when a reviewer encounters a complex monetization flow.

Growth teams need a new testing discipline

The era of isolated paywall experimentation is ending. A/B testing subscription screens without compliance review can create risk faster than it creates learning.

We recommend a three-layer testing model:

• Conversion testing: Does the paywall improve trial starts, purchases, and revenue per visitor?
• Comprehension testing: Can users accurately describe what they will be charged and when?
• Compliance testing: Does the flow satisfy the rules for the market, app category, and purchase type?

The comprehension layer is the one many teams skip. It is also the layer most likely to prevent review problems and negative billing reviews.

For subscription apps, this should become part of standard aso for subscription apps practice. Ratings, reviews, and store conversion do not improve when users feel tricked into paying. A slightly lower conversion rate with cleaner intent can outperform a high-pressure funnel once refunds, cancellations, bad reviews, and review risk are included.

The commission debate is not going away

Apple’s payment enforcement sits inside a larger platform-economics fight. Developers want more margin and more control over customer relationships. Apple wants to preserve user trust, store safety, and its services revenue. Regulators and courts continue to narrow some of Apple’s historical restrictions, but they have not removed Apple’s ability to police checkout design.

That is the operating environment now: more payment flexibility, more procedural complexity, and continued enforcement.

We do not expect Apple to ignore aggressive external payment experiments. If anything, the platform has reason to make examples out of flows that appear to convert legal flexibility into consumer confusion. The most exposed apps are those that combine viral growth, high revenue, aggressive subscription pricing, and ambiguous checkout design.

The practical takeaway

External payments are a monetization opportunity, not a compliance shield.

For developers, the safe path is to treat payment architecture as a cross-functional decision involving product, legal, ASO, lifecycle, analytics, and support. The store listing may win the install, but the paywall can now threaten the listing’s availability if it crosses the line.

Our working rule is simple: if the billing screen needs a long explanation after the fact, it is probably not clear enough before purchase.

Apple’s message is equally clear. Developers can test new payment paths, but they cannot remove required IAP options, obscure real pricing, or pressure users through confusing subscription mechanics. The checkout may be moving beyond Apple-only payment rails, but it is still firmly inside Apple’s policy perimeter.