Use this page with AI
Copy this into your coding assistant and add your request.
Read https://openiap.dev/docs/types/verify-purchase 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]VerifyPurchase Types
Purchase Verification Types#
Types used with verifyPurchase() for server-side purchase verification.
Input/output shape for verifyPurchase. iOS: validates the JWS from Transaction.jsonRepresentation (Apple docs). Android: validates the purchaseToken against Google Play Developer API (Google docs).
Native references: Apple · App Store Server API · Google Play Developer API · purchases.subscriptionsv2 · Meta Horizon · IAP Overview
VerifyPurchaseProps#
| Name | Summary |
|---|---|
apple | Apple App Store verification options. Contains: sku |
google | Google Play verification options. Contains: sku, packageName, purchaseToken, accessToken, isSub |
horizon | Meta Horizon (Quest) verification options. Contains: sku, userId, accessToken |
VerifyPurchaseResult#
Union of VerifyPurchaseResultIOS, VerifyPurchaseResultAndroid, and VerifyPurchaseResultHorizon.
VerifyPurchaseResultIOS#
| Name | Summary |
|---|---|
isValid | Whether verification succeeded |
receiptData | Raw App Store receipt data |
jwsRepresentation | JWS-encoded transaction |
latestTransaction | Most recent transaction for this product |