Since these cards actually "store money offline", the symmetric keys involved are really not something the issuers ever want to see leaked, so I assume it's not only a question of money (i.e. licensing fees), but also trust in the security posture of the secure element of the phone (if it even has one; many Android phones don't).
I will write a correction for this section to clear up the confusion.
I rooted my US model Pixel 9 Pro on my Japan trip last year to enable it. :D Literally a boolean in a config file.
https://github.com/kormax/osaifu-keitai-google-pixel
(The author's write up has more theories on why Google blocks it on non-Japan SKUs)
There's a big chance that Apple does not eat the cost for Osaifu-Keitai actually, as they may have a sweet-heart deal, hinted by an article from watch.impress [1], which I found a very long time ago via Twitter.
So the fee is either waived by FeliCa networks, covered by Japanese Carriers, and (as an educated guess) paid only upon enrollment of the first FeliCa-compatible card to device.
I think it would be naive to believe that Apple, of all companies, would be the one willing to pay a couple of cents per device in order to offer a feature that, at best, only a single digit percentage of their users would use.
[1] https://www.watch.impress.co.jp/docs/series/suzukij/1297656....
> Since there's no point in generating keys for a device which will not be used in Japan, non-Japan SKUs don't have Osaifu-Keitai functionality.
AFAIK, all iPhones from all regions since like iPhone 10 (internet says iPhone 7) support Osaifu-Kaitai unless I don't understand what that means. My USA iPhones works everywhere Suika, Pasmo, Icoca, etc work. Every station, bus, vending machine, convenience store, super market, restaurant, and retail store that accept these forms of payment, they all just work.
Given that all of this works, what is it I'm missing?