Are there plans to support Storekit 2 receipt verification?

[william]

Currently it appears that VerifyPurchase is only compatible with the StoreKit 1's PKCS#7 receipts. With StoreKit 2 becoming more common, the receipt format is apparently shifting to using the JWS representation for verification, and is recommended by libraries like Unity Purchasing v5. So I was curious if there are plans to update VerifyPurchase via either a secondary itunes store ID or a full migration?

[Paul Winterhalder]

Hi @william ,

We do have plans to support the new receipts. The work has been assessed - but not scheduled yet. I would expect it to be early next year.

Thanks for asking!

Paul.

[LEE JONG GUN]

Hi @Paul-Winterhalder

I wanted to follow up regarding StoreKit 2 JWS receipt support.
At the moment, Unity IAP v5 relies on StoreKit 2 by default, but there are two major issues we’re facing in production:

VerifyPurchase currently only supports StoreKit 1’s PKCS#7 receipt format.
When StoreKit 2 is used (as in Unity IAP v5), the App Store often returns empty receipts in certain environments — especially on Apple Silicon (M-series) Macs running iPadOS compatibility mode — causing verification to fail and users to lose their purchases.

In addition, Unity IAP v5 has a known issue where after the first successful purchase, all subsequent purchases return the same receipt as the first transaction.
This makes it impossible for the server to distinguish or validate new purchases, since every transaction reuses the initial receipt data.

Both of these problems make proper validation impossible under StoreKit 2, and they directly affect live monetization and user trust.

If StoreKit 2 JWS receipt support could be prioritized or exposed as a secondary endpoint (for example, itunes2), it would help developers transition more safely.
Given the impact, we would really appreciate if this work could be accelerated.