@JackB321 Yeah, this is very frustrating. The local cached transaction record should be rock solid, but it seems like that's not the case now, which has got me rethinking things. I already persist an isPremium flag to UserDefaults on successful purchase, so (assuming we don't get some kind of clarity from Apple soon), I'm planning to rely on my flag rather than the transaction record at launch (at least temporarily). It's not really ideal, but my app does authorization checks on the server side anyway, so for my purposes this is a viable option. Do you have any clarity on whether this bug is still happening today? I can't tell if this was a temporary thing a few weeks ago (and I'm only just seeing the ramifications now) or if it's still an ongoing problem.

@JackB321 Maybe you could try requesting direct code-level support: https://developer.apple.com/support/technical/ This would at least get the issue in front of someone who could figure out the problem or escalate it with the relevant team.

[quote='824230021, Ivan_developer, /thread/824230, /profile/Ivan_developer'] If a customer originally purchased a subscription while their App Store country was France (so we reported France as the tax country), and later updates or renews that same subscription while located in Hungary, which country should we report going forward? [/quote] Can you clarify what you mean by "report"? Report to who/where? I'm not 100% sure, but I believe Apple collects sales taxes based on the user's current registered App Store country, so I guess subscription renewals would be in the new country (assuming the user has actually changed the country/payment details). Apple's commission is fixed, so it would be unaffected.