Standardized protocol for in-app purchases across all platforms — backed by Meta & Amazon
137
stars
1,133
commits
TypeScript
primary language
Sep 11, 2026
updated
The standardized protocol for implementing in-app purchases across all platforms
OpenIAP is a unified specification for in-app purchases across platforms, frameworks, and emerging technologies.
The OpenIAP specification standardizes IAP implementations to reduce fragmentation and enable consistent behavior across all platforms. This is especially critical in the AI coding era where standardized APIs enable better code generation.
The contracts every package and library implements live under specs/. They are publishable, implementation-independent, and never deployed as services:
This monorepo contains all OpenIAP packages:
CLI - @hyodotdev/openiap starts an AI implementation brief for your product with openiap init and checks local configuration with openiap doctor. Run npx @hyodotdev/openiap in your project.
docs - Documentation site at openiap.dev
google - Android library
apple - iOS/macOS library
kit - Open-source purchase validation and entitlement infrastructure for the OpenIAP ecosystem, with a hosted service and dashboard at kit.openiap.dev. Free for every developer under hosted fair-use safeguards.
mcp-server - IAPKit MCP server, hosted at kit.openiap.dev/mcp for AI coding agents
Framework SDK implementations built on top of OpenIAP. These libraries are managed in this monorepo — see discussion #86 for the rationale and migration context.
| Library | Platform | Package | Downloads |
|---|---|---|---|
| expo-iap | Expo | ||
| react-native-iap | React Native | ||
| flutter_inapp_purchase | Flutter | ||
| kmp-iap | Kotlin Multiplatform | — | |
| maui-iap | .NET MAUI | ||
| godot-iap | Godot 4.x | — |
Visit openiap.dev for complete documentation and API reference.
Have a question or need help? Ask in the relevant GitHub Discussions category:
| Library | Discussion |
|---|---|
| openiap-apple | Q&A |
| openiap-google | Q&A |
| IAPKit | Q&A |
| expo-iap | Q&A |
| react-native-iap | Q&A |
| flutter_inapp_purchase | Q&A |
| kmp-iap | Q&A |
| maui-iap | Q&A |
| godot-iap | Q&A |
For bug reports, please open an issue.
Thank you to Meta and Amazon Developer for supporting OpenIAP. View sponsorship options.
We also recognize sponsors and backers through OpenCollective. The original react-native-iap collective now supports the broader OpenIAP ecosystem and is managed separately from the main sponsor program.
Become a sponsor | Become a backer
Supported the project before the OpenIAP sponsor program.
OpenIAP began with the original react-native-iap community and carries that work forward across the broader ecosystem:
See CONTRIBUTING.md for development setup, workflows, and contribution guidelines.
TypeScript
45.8%
Kotlin
14.5%
JavaScript
10.7%
Swift
6.6%
HTML
6.2%
Dart
5.8%
GDScript
4.4%
C#
3.8%
CSS
1.2%
Standardized protocol for in-app purchases across all platforms — backed by Meta & Amazon
137
stars
1,133
commits
TypeScript
primary language
Sep 11, 2026
updated
The standardized protocol for implementing in-app purchases across all platforms
OpenIAP is a unified specification for in-app purchases across platforms, frameworks, and emerging technologies.
The OpenIAP specification standardizes IAP implementations to reduce fragmentation and enable consistent behavior across all platforms. This is especially critical in the AI coding era where standardized APIs enable better code generation.
The contracts every package and library implements live under specs/. They are publishable, implementation-independent, and never deployed as services:
This monorepo contains all OpenIAP packages:
CLI - @hyodotdev/openiap starts an AI implementation brief for your product with openiap init and checks local configuration with openiap doctor. Run npx @hyodotdev/openiap in your project.
docs - Documentation site at openiap.dev
google - Android library
apple - iOS/macOS library
kit - Open-source purchase validation and entitlement infrastructure for the OpenIAP ecosystem, with a hosted service and dashboard at kit.openiap.dev. Free for every developer under hosted fair-use safeguards.
mcp-server - IAPKit MCP server, hosted at kit.openiap.dev/mcp for AI coding agents
Framework SDK implementations built on top of OpenIAP. These libraries are managed in this monorepo — see discussion #86 for the rationale and migration context.
| Library | Platform | Package | Downloads |
|---|---|---|---|
| expo-iap | Expo | ||
| react-native-iap | React Native | ||
| flutter_inapp_purchase | Flutter | ||
| kmp-iap | Kotlin Multiplatform | — | |
| maui-iap | .NET MAUI | ||
| godot-iap | Godot 4.x | — |
Visit openiap.dev for complete documentation and API reference.
Have a question or need help? Ask in the relevant GitHub Discussions category:
| Library | Discussion |
|---|---|
| openiap-apple | Q&A |
| openiap-google | Q&A |
| IAPKit | Q&A |
| expo-iap | Q&A |
| react-native-iap | Q&A |
| flutter_inapp_purchase | Q&A |
| kmp-iap | Q&A |
| maui-iap | Q&A |
| godot-iap | Q&A |
For bug reports, please open an issue.
Thank you to Meta and Amazon Developer for supporting OpenIAP. View sponsorship options.
We also recognize sponsors and backers through OpenCollective. The original react-native-iap collective now supports the broader OpenIAP ecosystem and is managed separately from the main sponsor program.
Become a sponsor | Become a backer
Supported the project before the OpenIAP sponsor program.
OpenIAP began with the original react-native-iap community and carries that work forward across the broader ecosystem:
See CONTRIBUTING.md for development setup, workflows, and contribution guidelines.
TypeScript
45.8%
Kotlin
14.5%
JavaScript
10.7%
Swift
6.6%
HTML
6.2%
Dart
5.8%
GDScript
4.4%
C#
3.8%
CSS
1.2%