Use this page with AI
Copy this into your coding assistant and add your request.
Read https://openiap.dev/docs/foundation/founding-supporters and https://openiap.dev/llms.txt. Follow the reading instructions, detailed reference, and linked guides relevant to my task before making changes.
Inspect my existing project and reuse its framework and conventions. Ask me for missing product decisions. Implement the requested behavior and run the applicable checks.
Show the working result, the commands and actual test results, and any remaining limitations. Keep your explanation brief.
My request: [describe what customers should be able to do]Become a Founding Supporter
We are looking for organizations to join as Founding Supporters and help shape OpenIAP while its governance is being set up.
What We're Building#
OpenIAP is transitioning from a single-maintainer library to an open interoperability standard with neutral governance. We need organizations who understand why this matters:
- A common specification for purchase types, error codes, and verification across iOS, Android, and emerging platforms
- Generated, type-safe bindings for TypeScript, Swift, Kotlin, Dart, C#, and GDScript
- Security-first design with verification profiles and fraud prevention patterns
- Open governance so no single company controls the purchase interoperability layer
Why "Founding" Matters#
Founding Supporters get permanent recognition and early influence that later sponsors won't:
| Benefit | Details |
|---|---|
| Permanent recognition | Listed as a Founding Supporter on the website, README, and all future governance documents — forever |
| Advisory Board seat | When the Advisory Board is formed, Founding Supporters get guaranteed seats with input on roadmap priorities |
| Roadmap influence | Priority input on which platforms, features, and security capabilities are built next |
| Featured case study | A dedicated case study on the OpenIAP website highlighting how your organization uses the standard |
| Direct maintainer access | Monthly sync calls with the project lead |
| Community voice | As OpenIAP grows, Founding Supporters are recognized as the initial supporting organizations that helped shape the standard |
Who Should Join#
We're looking for organizations in these areas — but we're open to anyone who benefits from purchase interoperability:
| Category | Examples |
|---|---|
| App payment SDKs/infrastructure | Companies building payment tooling for mobile apps |
| Cross-platform frameworks | React Native, Expo, Flutter, KMP ecosystem companies |
| Game engines/plugins | Studios or plugin authors building on Unity, Unreal, Godot |
| Verification/fraud prevention | Server-side receipt validation and anti-fraud services |
| App publishers/studios | Large-scale app or game publishers with IAP revenue |
| Developer tooling | Companies building developer tools that integrate with purchase APIs |
What We're Asking#
We're not asking for a big commitment. The first step is simply this:
"We're taking OpenIAP from a personal repo to a neutral, open interoperability standard. We'd like your organization to be listed as an initial supporting organization. This signals to the broader community that the project has multi-stakeholder backing. There's no financial commitment required at this stage."
If you're also interested in financial sponsorship, see our sponsorship tiers.
Timeline#
| When | What Happens |
|---|---|
| Now | Reach out — we'll discuss how OpenIAP fits your organization |
| Week 1–2 | Sign a lightweight letter of support (no legal obligations) |
| Month 1–2 | Your logo appears on the website as a Founding Supporter |
| Month 3–6 | Advisory Board forms with Founding Supporters as initial members |
| Month 6–12 | Foundation hosting exploration with your organization listed as a supporting entity |
Get in Touch#
Ready to join, or just want to learn more? Reach out directly:
Hyo — Project Lead