Unity IAP 4: End of Support Announcement

Unity Services
,
1

Hi everyone,

As of June 8, 2026, Unity IAP 4 is being deprecated. IAP 5 is the path forward.

Why migrate now

IAP 5 will support updates IAP 4 simply can’t:

  • Modern store support: Google Play Billing Library 7+ and Apple’s modern StoreKit (including the StoreKit 1 backward compatibility we added back in IAP 5.1 for iOS 14 and below).
  • Better debugging: Platform-specific store logs surface directly, so failed purchases tell you why instead of leaving you to guess.
  • All future investment: New features, store integrations, and improvements land in IAP 5.
    • D2C commerce, GA at the end of June 2026: IAP 5 is the SDK foundation for selling directly to your players to benefit from higher margins, more pricing control, and one catalogue for D2C transactions. If D2C is on your roadmap, migrating to IAP 5 means the capability is there when you want to turn it on.

What changes June 8

From June 8, 2026:

  • No new features for IAP 4
  • No more bug fixes in IAP 4
  • No more customer support for IAP 4
  • All IAP 4 versions will start to be marked as deprecated in Package Manager

What doesn’t change

  • Your existing IAP 4 projects keep running
  • The package isn’t being removed
  • No forced upgrades until December (see below)

Hard bump: Next LTS after U6.3 (targeting December 2026)

When the next LTS ships, the bundled editor manifest will point to IAP 5 instead of IAP 4. This means projects on that LTS that resolve packages will get IAP 5 by default.

Your code is mostly backwards compatible, but there are two operational changes:

  1. Amazon App Store requires migration to the custom store path
  2. iOS 15+ becomes the minimum. If you support iOS 14 or earlier, you’ll need to update your minimum deployment target.

How to prepare: Run the IAP migration AI skill (works in Unity AI Assistant or Claude Code). It scans your project, writes a plan, and applies changes with your approval. Most projects take a few hours. For detailed migration steps, see our upgrade guide.

How to get started

Starting a new project: Install IAP 5.3 - it’s already the default in Package Manager.

Existing projects on IAP 4: Use the migration AI skill in your next dev cycle. You have 6 months before U6.7.

Amazon App Store: Supported in IAP 5 via custom store path. Full tutorial here with PDF, video, and asset package.

Blocked on something specific: Tell us in this thread. Real blockers matter — we’d rather hear about them now.

What’s next on IAP 5

  • Google Play Billing Library v9 support
  • D2C capabilities (webshop, in-game purchase UI)
  • Remote catalog management from the Dashboard
  • IAP transaction reporting across native stores and D2C

We know deprecation announcements aren’t fun to read, but the move to IAP 5 has real benefits and we’re here to help. Reply with questions.

— The Unity IAP team

1 Like
3

Forcing us to IAP 5 also means dropping Window Store support but there is no mention of that platform in this announcement. Do you have any suggestions on how to handle that?

4

We already have a released game using Unity IAP 4, and we’re planning to migrate to IAP 5 to keep up with future store requirements.
We don’t really need new IAP features right now — our main concern is support for the latest store requirements. So we’re wondering if it makes sense to wait until Google Play Billing Library v9 support is available before migrating.
Do you have any rough timeline for Google Play Billing Library v9 support? Will it be available before the December 2026 deadline?

5

Hi, can you explain please what means “force upgrade”? If we are ok on our porject with Unity IAP v4 can we stay on it after December?

7

Thanks for raising this. The standard IAP 5 migration guidance does not fully address projects that still depend on Windows Store support, so this should be reviewed as a specific migration scenario.

For IAP 5, we do not plan to support the legacy UWP / Windows Store integration. For Microsoft platforms, our current plan is to support Xbox Store natively in IAP 5.3.0 through the Microsoft GDK. That means projects that still rely on the legacy Windows Store / UWP path should treat this as a platform-specific migration consideration rather than a standard IAP 5 upgrade.

If your project still needs Windows Store / UWP purchasing support, the main options are:

  • implement a Custom Store integration for unsupported store flows, noting that Unity does not currently provide a built-in Custom Store implementation for legacy Windows Store / UWP as part of the IAP 5 migration path.
  • or evaluate whether moving to the Microsoft GDK / Xbox Store path is viable for your title
1 Like
8

Google Play Billing Library v9 support is planned for Unity IAP 5.4.0, and will be available when the package is made generally available shortly (end of June 2026).

1 Like
9

By “forced upgrade,” we do not mean that existing projects using Unity IAP v4 will automatically stop working in December.

The December timing refers to the expected Unity Editor and LTS package default change. In the next LTS after Unity 6.3, currently targeted for December 2026, the bundled package manifest is expected to resolve Unity IAP to IAP v5 by default instead of IAP v4. This means projects that move to that Unity version, or otherwise resolve packages against the updated defaults, will receive IAP v5 unless their package configuration is managed accordingly.

That said, Unity IAP v4 has been deprecated as of June 8, 2026. After that date, IAP v4 will not receive new features, bug fixes, or customer support. We recommend planning a migration to IAP v5 during your next development cycle so you can stay aligned with current store requirements and future IAP capabilities.

In short:

  • No, IAP v4 does not automatically stop working in December.
  • Yes, you can remain on IAP v4 after December if you actively manage your project manifest to restore references to IAP v4 when it is updated to v5 following editor upgrades
  • The December change is about the default IAP version in future Unity LTS package resolution.
  • IAP v4 will be deprecated and unsupported, so migration to IAP v5 is recommended.
1 Like
10

Unity does not charge additional fees for using the Unity IAP D2C capabilities. Developers pay the fee agreed with their selected third-party payment provider or merchant of record, such as Stripe or Coda. The exact fee depends on the provider and the developer’s agreement with that provider.