Choose a monetization SDK

• Full platform access — A single SDK gives you IAP along with achievements, leaderboards, group presence, user profiles, notifications, DLC/asset file downloads, and more.
• Native Kotlin API — Built with Kotlin coroutines and idiomatic patterns, providing a modern async development experience.
• DLC and asset file support — Download and manage large content files directly through the SDK, which the Billing Compatibility SDK does not support.
• Server-to-server APIs — Dedicated S2S APIs for server-side purchase verification and subscription management.
• No compatibility layer — Direct access to the platform without a translation layer, reducing potential surface area for bugs.

• Higher migration effort — If you have an existing Google Play Billing integration, you will need to rewrite your billing code to use Meta’s API surface.
• Meta-specific API — Code written against the Platform SDK is specific to Horizon OS. You will need to maintain separate billing integrations for Google Play and the Meta Horizon Store.

• You are building a new app for Horizon OS, or your app does not have an existing Google Play Billing integration.
• You need platform features beyond billing, such as achievements, leaderboards, group presence, or DLC downloads.
• You want a single SDK for all platform interactions.
• You prefer native Kotlin APIs with coroutine support.

• Minimal migration effort — In most cases, you only need to replace com.android.billingclient.api imports with com.meta.horizon.billingclient.api. Your existing billing logic, listeners, and purchase flow code remain largely unchanged.
• Familiar API — If your team already knows the Google Play Billing Library, there is no new API to learn.
• Shared billing code — You can maintain a single billing codebase with a build flavor or import swap to target both the Google Play Store and the Meta Horizon Store.

• Billing only — This SDK only handles in-app purchases. If you need achievements, leaderboards, group presence, or other platform features, you must also integrate the Platform SDK separately.
• No DLC/asset file support — Downloadable content management is not available through this SDK.
• Known limitations — Some Google Play Billing features are stubs or not fully supported, including alternative billing, external offers, in-app messaging, and billing configuration. Only single-item checkout flows are supported. See Known Limitations for the full list.
• Compatibility layer overhead — The SDK wraps the Platform SDK internally, which adds an additional dependency and abstraction layer.

• You have an existing Android app with a working Google Play Billing integration and want to port it to the Meta Horizon Store quickly.
• You want to minimize code changes and reuse your existing billing logic.
• Billing is your only platform need — you do not require achievements, leaderboards, group presence, or other platform services.
• You want to maintain a shared billing codebase across Google Play and the Meta Horizon Store.

• Yes — Start with the Horizon Billing Compatibility SDK to get your app on the Meta Horizon Store quickly. If you later need platform features like achievements or leaderboards, you can integrate the Platform SDK alongside it.
• No — Use the Platform SDK directly. It gives you native APIs, full platform access, and avoids the limitations of the compatibility layer.