In-App Billing Version 3
summary
In-App Billing v3 makes API calls synchronous and adds a client-side cache so getPurchases becomes cheap, letting apps check ownership at startup; purchases launch with getBuyIntent and return a purchaseToken that is used to call consumePurchase for consumables. Use getSkuDetails for localized price/title, verify signatures and include a unique developer payload to prevent replay, validate subscriptions server-side via the REST API, and test end-to-end with the sandbox test accounts on the Play publisher console.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:36InApp Billing v2
- 3:23Restoring Purchases
- 3:45ClientSide Cache
- 4:00Users Items
- 4:17Developer Items
- 4:35Supported Devices
- 5:03Get Purchases
- 6:30Manage Items
- 6:45Get by Intent
- 7:31Purchase Result
- 8:43Phone Science
- 9:08Managed Purchases
- 10:48Consume Purchase
- 11:10When to Consume
- 11:50Example
- 14:15Limitation of Method 2
- 16:07SKU Details
- 17:09Subscriptions
- 17:32Check if subscriptions are supported
- 17:47Launch subscription purchase flow
- 18:23Whats a subscription state
- 19:59Local cache
- 20:24UI thread
- 21:45Serverside API
- 23:07Security
- 24:56Developer Payload
- 26:39Signature Verification
- 27:34Serverside Security
- 28:58Security Summary
- 30:26InApp Billing Sandbox
- 33:20Recap
- 33:47Feedback
related talks
44mTaking your users’ money: In-app billing from start to best practices
49mTaking your users’ money: In-app billing from start to best practices
44mThe State off in app purchases on Android
30mWhat's new with Play Billing
34mTesting In App Billing the Easy Way
46mA deep dive into
23mIn-App Subscriptions for all Android devices
19mMigrate to Google Play Billing