Edit the Blog Post Header component above this, then place your content here, then fill out the Related Articles section below, if possible. You should have at least one related article and ideally, all three.
Feel free to add supplementary content to the sidebar at right, but please retain the Twitter component (it can live at the bottom of your added content).
This text component can be edited or deleted as necessary.
Related article title here
Related articles only have an image (the squarer version of the banner) and a title. This text can be deleted. Place 1-3 related articles.
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.
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.
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:
- react-native-iap 16.3.1
- expo-iap 5.3.1
- openiap-google-amazon 3.3.1 (Amazon flavor)
➡️ See PR 162 for the implementation.
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.
Supported devices
© 2010-2026, Amazon.com, Inc. or its affiliates. All Rights Reserved.