South Korea's telecom regulator fined Apple ₩20.81 billion and Google ₩42.9 billion — a combined ₩63.7 billion, or roughly $47.6 million — on October 28, 2026, for violating the country's Telecommunications Business Act. The finding: both companies steered local app developers toward their own in-app payment systems and charged commissions of up to 26% on payments processed through third-party options, when developers were allowed to offer them at all.
Regulators didn't stop at the fine. They also ordered Apple and Google to let Korean developers use external payment links inside their apps and to fix non-transparent delays in the app-review process that developers had flagged as a separate point of friction. Apple told the Associated Press it disagrees with the decision and is weighing its legal options; as of publication, Google had not issued a comparable public response to the ruling.
For most readers this will register as a Big Tech headline and nothing more. But if your business runs an iOS app — or is building one — it's worth a few minutes, because it previews where app-store payment and review rules are heading globally, not just in one market. If a compliance check turns up gaps, it may be worth talking to a team that offers dedicated iOS app development services to handle payment-flow and App Store review changes as they roll out, rather than discovering the gap after a regulator does.
What South Korea's regulators found
The 26% third-party payment commission
The core of the finding is simple: Korean law already requires app marketplaces to allow alternative payment methods, but regulators found that Apple and Google made the alternative worse than the default in practice. A 26% commission on third-party payments, next to the standard in-app rate, left developers with little real incentive to use the option the law was supposed to protect. The effect, according to the regulator's findings, was the same outcome as a flat payment mandate — just reached through pricing instead of a rule.
Blocked external payment links and delayed app reviews
The second piece is about friction, not just price. Developers who wanted to point users to an external payment page — skipping the in-app system and its commission entirely — ran into restrictions on doing so, plus app-review timelines that regulators described as non-transparent. A developer whose update sits in review limbo for unclear reasons has little practical ability to switch payment approaches even where it's technically allowed, which is part of why the corrective order addresses both issues together.
Why this matters beyond South Korea
South Korea isn't acting in isolation. The European Union's Digital Markets Act has already forced changes to how Apple and Google handle alternative payments and app distribution for EU users, and regulators in several other regions have opened similar inquiries into app-store commission structures over the past two years. None of that means a single global standard is imminent — rules differ by region and are likely to keep differing. But the direction is consistent: app-store payment flexibility is turning into a recurring compliance topic that regulators keep returning to, not a single news cycle that resolves and goes away.
What it means for your business's iOS app
None of this requires panic if you don't operate in South Korea today. It does justify treating your app's payment integration as something that needs periodic review, not a decision you made once at launch and can forget about:
- Don't assume your current payment setup is "set" for every market. A flow that's fully compliant in the US or EU today may not automatically clear the bar if you expand into a more actively regulated region.
- Review flow risk before you expand into a regulated market. Adding external payment links or supporting alternative processors is a scoped engineering task if you plan for it — and a rushed one if a regulator or app-store policy change forces your hand.
- Budget for compliance updates as ongoing app maintenance, not a one-time build. Payment and review-process rules are clearly still moving; an app built to be adjustable costs less to update than one that has to be reworked from the payment layer up.
A short technical review is usually enough to tell you whether your current payment integration would hold up if your market expanded tomorrow — and that review is a fraction of the cost of finding out the hard way after a launch.
FAQ
Does this fine affect apps outside South Korea?
Not directly, and not yet. The ruling applies to how Apple and Google operate in South Korea specifically. But regulators in other regions have been pushing in the same direction, so the trend is worth watching even if you don't operate there today.
What should a small business do about it right now?
Nothing urgent unless you already operate in South Korea. For everyone else, it's a reasonable prompt to add a payment-flow compliance check to your next app update cycle rather than an emergency fix.
Who do I ask for help implementing alternative payment options in my iOS app?
A specialized iOS development team that has already handled payment-flow changes and App Store review back-and-forth for other clients — this isn't a feature any general contractor should be learning on your app for the first time.
Sources: Fortune, Euronews. This article is for informational purposes only and does not replace professional advice. Found an error? Let the editors know via the contact page.
