South Korean developers complain Apple's iOS app refund terms causing financial problems
Developers in South Korea are decrying the iOS App Store's refund policy, saying that they are spending an inordinate amount of time cracking down on customers who have claimed to need a refund for an app's purchase by minors, yet are still consuming resources.
Several developers are pointing to a rash of app refunds that are causing problems economically and with fair game play, under Apple's state-ordered policy on refunding users with multiple instances of charged content, like expensive consumables.
"By analyzing all payment data and logs, we have tracked down about 300 users who are suspected of abusing App Store's refund policy," game developer Flint's CEO Kim Young-mo told the Korea Times. "We pledge to root out the abusers by requesting the judicial authorities for an investigation."
Some of the developers have requested Apple's assistance in cracking down. Apple does not provide information on people who demand refunds, and the company acts on the requests without consulting developers.
Additionally, the Korea Times claims that there are profitable businesses who will file the refund process for customers, and take a percentage of the refund.
"We are regulating those who abuse the payment process and damage other users under our management policy," Korean developer Next Floor said. "Unlike other application stores, Apple does not provide refund information to the game companies and we are having difficulties in promptly counteracting the problem."
In 2014, South Korea's Fair Trade Commission ordered Apple to make changes to the iOS App Store policy to allow for post-purchase refunds.
As a result, Apple now decides on a case-by-case basis if a user who requests a refund on an app or in-app purchase will get it granted. Appeals to Apple are generally processed within a week, with reports suggesting that multiple, expensive in-app purchases being weighed heavier than a simple one-time app purchase.
Several developers are pointing to a rash of app refunds that are causing problems economically and with fair game play, under Apple's state-ordered policy on refunding users with multiple instances of charged content, like expensive consumables.
"By analyzing all payment data and logs, we have tracked down about 300 users who are suspected of abusing App Store's refund policy," game developer Flint's CEO Kim Young-mo told the Korea Times. "We pledge to root out the abusers by requesting the judicial authorities for an investigation."
Some of the developers have requested Apple's assistance in cracking down. Apple does not provide information on people who demand refunds, and the company acts on the requests without consulting developers.
Additionally, the Korea Times claims that there are profitable businesses who will file the refund process for customers, and take a percentage of the refund.
"We are regulating those who abuse the payment process and damage other users under our management policy," Korean developer Next Floor said. "Unlike other application stores, Apple does not provide refund information to the game companies and we are having difficulties in promptly counteracting the problem."
In 2014, South Korea's Fair Trade Commission ordered Apple to make changes to the iOS App Store policy to allow for post-purchase refunds.
As a result, Apple now decides on a case-by-case basis if a user who requests a refund on an app or in-app purchase will get it granted. Appeals to Apple are generally processed within a week, with reports suggesting that multiple, expensive in-app purchases being weighed heavier than a simple one-time app purchase.
Comments
While I agree with that, that's not the problem they are talking about. They are talking about systematic efforts to make an in-app purchase and then get a refund without losing the thing purchased. If it's just a few people doing it for their own use, who cares/it's the cost of doing business. When it because common practice with people facilitating it for the average user, it's a problem. Having said that, it sounds like Apple and the affected developers are in discussions about it, so I'll expect they'll work it out.