We're excited to announce that Amazon is sponsoring OpenIAP, which now supports in-app purchasing (IAP) flows for Amazon devices across both Fire OS and Vega OS.
OpenIAP gives you one standard way to build in-app purchase flows and verify receipts, whatever framework you use. It's open source, with backers including Meta, and now Amazon.
That standard supports Expo, React Native, Flutter, Kotlin Multiplatform (KMP), .NET MAUI, and Godot. So, if you're already using react-native-iap or expo-iap, you can ship IAP flows on Amazon devices with the same APIs you know, with no separate integration path to maintain.
Why it matters?
More than 300 million Fire TV devices have been sold worldwide, and last year alone customers spent over 100 billion hours streaming, gaming, and watching live events on them. Behind a lot of those hours are IAP payment flows - renting a movie, unlocking a game level or subscribing to a channel.
We know that adding Amazon Appstore IAPto a cross-platform app has meant a separate SDK, separate types, and separate purchase update handling from the Google Play or Apple App Store path. For developers targeting Amazon devices in addition to iOS and Android, we’ve seen that friction add up fast.
OpenIAP mitigates that friction, so you can reach the millions of Fire TV customers with the same code you’re already shipping on other store's. This community project maps Amazon Appstore’s purchase model (consumables, entitlements, subscriptions, purchase updates, and fulfillment) into the same OpenIAP API model used for Google Play and the App Store.
One API across both Operating Systems
Fire TV devices run on two operating systems: Fire OS and Vega OS. OpenIAP supports both, so you can use the same APIs to target them while OpenIAP handles the OS-specific work, so you don't need to.
Fire OS is implemented as the Android amazon flavor, backed by the Amazon Appstore SDK. If you already ship an Android build, this is a Gradle-level switch for most frameworks. Select Amazon Appstore SDK as your IAP backend on any Android target:
Native Android: depend on openiap-google-amazon and use the amazon platform flavor
Bare React Native: set fireOsEnabled=true in gradle.properties
Expo: use the expo-iap config plugin with modules.amazon.fireOS:true
Flutter, KMP, MAUI: use the equivalent flavor selection in your build config
➡️ See the Fire OS setup guide for full steps.
Vega OS is a separate Kepler runtime target, not an Android flavor. Vega apps use manifest.toml, Kepler dependencies, and the Amazon Kepler IAP module. React Native for Vega and compatible Expo Vega apps get an OpenIAP adapter that talks to the Kepler IAP service.
Expo: set modules.amazon.vegaOS:true, with optional Vega metadata overrides
React Native for Vega: install @amazon-devices/keplerscript-appstore-iap-lib alongside react-native-iap, and declare the IAP module in manifest.toml
➡️ See the Vega OS setup guide for full steps
It's important to keep in mind that Verification and catalog identity stay consistent across both. Verification uses the same IAPKit Amazon receipt payload, so your server-side validation code doesn’t fork. And product IDs stay aligned across the Amazon Developer Console, Amazon App Tester, your app code, and entitlement checks meaning the same SKU strings all the way through.
Release Notes
Fire OS and Vega OS support first shipped in the OpenIAP RC.1 wave (openiap-google 2.3.0-rc.1, react-native-iap 15.4.0-rc.1, expo-iap 4.4.0-rc.5, plus matching RCs for KMP, MAUI, Flutter, and Godot) and is now available in the current stable releases:
openiap-google-amazon 3.3.1 (Amazon flavour)
➡️ See PR 162 for the implementation.
Get started today
Start with the **Amazon Store Setup guide** in the OpenIAP docs for the guidance on Fire OS and Vega OS implementations.
If you already use react-native-iap or expo-iap, add the Amazon flavor selection to your existing build targets.
Test purchases before publishing with Amazon App Tester for local IAP validation.
Where to go for help:
OpenIAP docs: openiap.dev/docs
OpenIAP GitHub: github.com/hyodotdev/openiap
Amazon Appstore IAP docs: developer.amazon.com/docs/in-app-purchasing
Amazon developer community: community.amazondeveloper.com
OpenIAP continues to operate independently with the same commitment to developer experience and cross-platform compatibility. The core libraries remain MIT licensed and free to use, and our role is to support these efforts and contribute to the project.
Special thanks to the lead maintainer Hyo Dev and the years of work he and many other contributors have put into this project.
Finally, tell us what you think! If you’re building for Amazon devices and using OpenIAP (or thinking about it), we’d love to hear from you.
Top comments (0)