South Korea Orders Apple to Open App Store Payments and Revises $15.5 Million Fine

| 2 Min Read
South Korea fined Apple 20.81 billion won and ordered changes to payment options, app reviews and commission calculations for local developers.

South Korea’s order targets the rules behind app payments

South Korea’s latest App Store enforcement reaches beyond a fine: Apple must change how developers can accept payments, how it handles app reviews and how it calculates commissions for local businesses. The Korea Media and Communications Commission (KMCC) fined Apple 20.81 billion won, about $15.5 million, and issued corrective orders to Apple and Google under the Telecommunications Business Act.

That combination matters. A fine assigns a cost to past conduct; corrective orders reach into the systems companies use to operate their app marketplaces. The KMCC’s action therefore puts day-to-day policies—payment routes, review handling and commission calculations—at the center of the dispute. Whether the changes alter developers’ practical choices will depend on how the companies implement them.

Payment choice and review delays under scrutiny

The KMCC said Apple and Google effectively steered developers toward their own in-app payment systems through a 26% commission and restrictions on third-party payment options. The commission characterized that conduct as using their position in app distribution to compel mobile content providers to adopt a specific payment method.

A commission can shape behavior even when an alternative payment route exists on paper. Developers have to weigh the cost of using the platform’s system against the restrictions attached to outside options, including the effort of supporting a separate payment process. The KMCC’s finding is that the combined terms left developers with a forced choice in practice. That distinction—formal permission versus a workable alternative—is where the order’s effect will be tested.

Both companies must revise their policies to permit external payment methods and address the limits placed on developers who use them. They’re also required to update app review procedures. The commission found that reviews were delayed without specific explanations, and that developers didn’t receive clear answers about the reasons for delays or expected timelines.

Review transparency is a separate but related pressure point. App marketplaces decide when software can reach users and whether updates are accepted, so unexplained delays can leave developers unable to plan releases or respond to problems. Clear reasons and timelines won’t guarantee a favorable review, but they can make the process more predictable and give developers information they can act on. The order makes that process part of the enforcement issue, not just a customer service concern.

The case is the first enforcement action under South Korea’s 2021 amendment to the Telecommunications Business Act. That amendment introduced prohibited conduct for app market operators, including forcing developers to use designated payment systems and unfairly delaying app reviews.

As the first action under the amendment, the case shows how the law is being applied to the mechanics of marketplace operation. The KMCC has addressed both the commercial terms developers face and the procedures governing access to users. This is more significant than it looks: a rule against steering has limited practical value if review decisions remain opaque, while clearer reviews alone wouldn’t resolve the payment dispute.

Apple’s commission calculations for Korean developers

Apple faces an additional finding that Google does not. From July 2015 through January 2023, Apple calculated its 30% commission differently for South Korean developers and developers abroad. For overseas developers, it applied the commission to prices before value-added tax (VAT); for South Korean developers, it used prices that included VAT.

The difference concerns the base on which the commission was calculated, rather than the stated commission rate alone. Applying the same percentage to a VAT-inclusive price can produce a different charge than applying it to a pre-tax price. The KMCC’s finding focuses on the unequal treatment of local and overseas developers over the period it identified. And this is the part most people overlook: a published commission rate doesn’t tell developers everything about the amount they’ll ultimately pay.

The KMCC said this amounted to discriminatory treatment in the economic benefits provided through telecommunications services. Apple must take steps to prevent the commission practice from recurring.

That requirement turns the finding into an ongoing compliance question. Apple will need to address the calculation method in a way that avoids a return to the disparity described by the commission. The announcement, as presented here, doesn’t spell out the specific mechanics of that remedy, so the details of implementation remain the point to watch.

Apple told Reuters it “disagreed ⁠with the decision and was evaluating options in accordance with South Korean ​laws.” The company also said it “⁠has worked with outside developers ​to enable innovation ​through ⁠its App Store.”

Those statements frame the dispute from Apple’s side, but they don’t resolve the commission’s specific findings. The company says it disagrees and is evaluating its options; the KMCC has issued corrective orders. The practical response will matter more than either statement: developers will be looking for changes they can see in payment terms, review communications and the treatment of VAT.

A wider shift in App Store policies

South Korea’s order adds to pressure on Apple to adapt its App Store model market by market. The company has introduced alternative app distribution and payment options in Brazil and Japan, while changes to its fees and business terms in the European Union have followed scrutiny from the European Commission.

The examples point to a company adapting its policies in response to scrutiny across several markets, while the exact terms vary by place. That makes the Korean case useful to watch on its own terms: the KMCC’s findings address payment restrictions, review delays and Apple’s VAT-related commission calculations. Developers operating across markets may face a patchwork of processes, and the details of each local policy can matter as much as the broad promise of an alternative.

What developers should watch next

The practical test in South Korea will be how Apple and Google implement payment alternatives and review transparency—and whether Apple changes its commission calculations in a way that prevents the same disparity from returning. The KMCC’s full announcement outlines the orders.

If you’re working in this space, the useful signals will be concrete: whether developers can explain their payment options to users under the revised rules, whether review delays come with reasons and expected timelines, and whether the commission base is clear. Those are operational questions, not abstract policy language. The fine is the headline; implementation is the test.

For now, the order establishes what the KMCC says must change and identifies the conduct it found problematic. It doesn’t, by itself, show how much developers’ costs or release schedules will shift once the policies are revised. That said, South Korea’s enforcement gives developers a defined set of issues to track as the changes take shape.

Source: Marcus Mendes · 9to5mac.com

Comments

Please sign in to comment.