Apple's EU payment options: compare fees and checkout costs before launch

A lower platform commission can look like an easy win until you count the work around it. If your subscription app sells digital services through the App Store in the EU, Apple’s terms effective October 1, 2026 let apps offer alternative payment methods and out-of-app offers alongside Apple In-App Purchase (IAP). The right question is not simply which rate is lower. It is whether the route fits your app, your customers, and your team’s ability to operate billing.

Apple lists different commission rates for IAP, alternative processing inside the app, and actionable links to out-of-app offers. The terms also add requirements around entitlements, disclosures, reporting, taxes, customer support, and child safety. This guide turns those requirements into a decision process for a small app team. Check the current terms and your account’s eligibility before changing a live payment flow; the overview below is not tax or legal advice.

Start by identifying the routeCopy Anchor Link

Apple describes three ways to sell digital goods and services through an app distributed in the EU:

• Apple IAP: Apple processes the transaction and provides services such as tax support and customer service.
• Alternative processing inside the app: the customer completes payment in the app through another payment processor.
• Out-of-app offer: the app directs or informs the customer about an offer outside the app. Some offers use an actionable link; others do not.

These are different product and operating choices. Do not treat “web checkout” as one uniform route. An in-app alternative processor has a different interface and operational burden from an offer that opens a website. Apple’s rules also distinguish an actionable link from an out-of-app offer without one.

The updated terms took effect on October 1, 2026. Apple says developers must keep their selected combination of payment options for 12 months. Before starting implementation, have the Account Holder review and accept the updated Apple Developer Program License Agreement. Then verify the entitlements, storefronts, device requirements, and current account status for the app. The ability to build a flow is not proof that a specific app or developer qualifies for every option.

Compare the listed commissions carefullyCopy Anchor Link

Apple’s EU overview currently lists these App Store commission rates:

The 15% IAP and 10% alternative-processing rates apply to sales specified by Apple for participants in the App Store Small Business Program, Mini Apps Partner Program, or Video Partner Program, and to qualifying auto-renewable subscriptions after the first year. Apple describes the linked-offer reductions separately. Do not apply one rate to every route or assume a program discount without checking the current terms and the app’s status.

For an actionable link, Apple says the store services commission applies only to sales made within seven days after the link tap. That is not the same thing as saying every website purchase owes that commission, nor does it mean every web purchase avoids Apple fees. The route, the link, the timing, the transaction type, and the applicable agreement matter.

These are Apple’s listed commission rates, not the full cost of collecting a payment. A third-party processor may charge its own fees. Your team may also need to cover tax collection and remittance, subscription management, refunds, disputes, fraud review, customer support, and reconciliation. Ask your accountant or counsel how taxes and the agreement apply to your business. Do not use a generic “Apple versus web” percentage comparison as a forecast.

Model the decision with your own numbersCopy Anchor Link

Use a contribution model for the same customer cohort and the same accounting period. Keep inputs separate so that assumptions are visible:

1. Eligible purchase volume: estimate the EU transactions that could actually use the route you are evaluating. Separate new subscriptions, renewals, one-time purchases, refunds, and transactions that never complete.
2. Conversion change: estimate how many customers would finish checkout on each route. Do not assume web checkout converts equally just because it is available. Use an experiment only if your implementation and Apple’s terms permit it.
3. Platform commission: apply the Apple-listed rate that matches the route and the app’s verified status. For linked offers, include the seven-day attribution window.
4. Processor and operating costs: add the payment processor’s own charges, tax administration, support coverage, fraud handling, and engineering and reporting time. Use actual quotes and observed workload, not a guessed flat percentage.
5. Customer impact: account for the extra step, disclosure, account continuity, and the customer’s ability to manage or restore a subscription. A cheaper route that creates confusion or failed renewals can cost more in lost retention.

A simple comparison is:

route contribution = completed eligible sales − Apple commission − processor charges − refunds and disputes − operating cost

Then compare the result with the IAP baseline using the same cohort and period. Keep the assumptions for conversion, eligible share, refunds, and support workload explicit. If the result changes when one uncertain input moves slightly, treat the choice as unresolved and gather better evidence before shipping.

Count the work that moves to your teamCopy Anchor Link

IAP includes services Apple says are handled for developers, including payment processing, foreign currency exchange, tax support, and customer service. With alternative payments, Apple says the developer becomes responsible for relevant taxes and customer issues. Apple may not be able to help customers with purchase history, subscription management, or refunds for those transactions.

There is also ongoing reporting. Apple requires a monthly report of alternative payment transactions, including refunds, corrections, renewals, one-time purchases, and transactions that did not result in a purchase. The report is due within 15 days after the calendar month ends. Apple invoices applicable commissions, with payment due within 30 days of the invoice. Apple also describes audit rights over transaction records.

That changes the internal owner map. Name who will reconcile processor records against app events, handle subscription cancellation and renewal questions, respond to payment disputes, prepare the monthly report, and review invoices. Decide how support will identify which processor handled a transaction without exposing payment data unnecessarily. If those jobs have no owner, the lower commission rate is not yet an operating plan.

Check interface and safety requirements before codingCopy Anchor Link

When an alternative in-app processor or an actionable link is offered alongside IAP, Apple says IAP must appear at the same time and be at least as prominent in the overall experience. Payment flows cannot discourage or disrupt IAP, and an App Store product page cannot advertise an alternative payment option. Apple also requires the relevant StoreKit entitlement and, for in-app processing or actionable links, StoreKit External Purchase APIs and a disclosure sheet.

Child-safety requirements add more checks. Alternative purchases for users under 13 must be behind a parental gate, and out-of-app offers are not permitted for them. For users aged 13 to 17, both alternative in-app processing and out-of-app offers must be behind a parental gate. Some EU storefronts set a higher age for parental consent, so verify the rule that applies to each storefront and your age-rating setup.

Translate these requirements into test cases before implementation: the same-screen choice, prominence, disclosure, eligibility checks, renewal, refund, cancellation, parental gates, and a user who abandons checkout and returns later. If the product serves children or teens, do not launch an alternative route until the relevant gates and storefront behavior have been reviewed.

Make a reversible launch decisionCopy Anchor Link

A small team can start with a narrow decision record rather than committing to a full payment migration:

• Which EU storefronts and customer segment are in scope?
• Which route is being considered: IAP, in-app alternative processing, or an out-of-app offer?
• Which Apple rate and program status did the estimate use?
• What processor quote, tax workflow, conversion assumption, and support load are included?
• Who owns monthly reports, customer cases, and reconciliation?
• What test and rollback conditions would stop the experiment?
• When does the 12-month selection commitment begin, and what does it constrain?

If the team cannot answer these with evidence, keep the existing route while you verify the unknowns. If a route still looks favorable after conversion loss and operating costs, test it with a defined cohort and a support plan. Review the result against contribution, successful renewals, refund and dispute rates, and support volume—not just checkout completion.

For broader release checks, see the AI-built app App Store submission checklist. For a separate Apple platform-readiness workflow, see the iPhone Duo app readiness guide.

SourcesCopy Anchor Link

• Apple Developer, Payment options on the App Store in the EU, checked October 11, 2026.

This is a product and operating-cost decision, not tax or legal advice.