Taking your users’ money: In-app billing from start to best practices
summary
Covers Google Play Billing Library (v2/v3) and the Play Developer REST API, warns that the library requires you to supply SKU lists because there is no API to list all products, and shows that subscriptions require server-side checks and real-time notifications; practical tips: must verify tokens server-side and acknowledge purchases within 3 days or Google auto-refunds. Testing needs a closed Play track (subscriptions renew every few minutes for tests), Register and BillingX ease local testing, and Google fee drops from 70% to 15% after 12 months retention.
AI-written summary · about
chapters (16)
- 0:00Introduction and speaker
- 1:29Why in-app billing matters
- 5:02Products and subscriptions basics
- 11:23App setup and billing client
- 13:53Product setup in Play Console
- 21:25Retrieving products in code
- 25:19Purchase flow and acknowledgment
- 28:29Acknowledging purchases
- 31:43Backend integration challenges
- 33:32Verification and consumption
- 35:39Handling cancellations and edge cases
- 36:44Real-time notifications and pricing changes
- 37:48Testing in-app billing
- 40:58Third-party testing libraries
- 41:59Transaction fees and retention
- 43:04Key takeaways and back end advice
related talks
49mTaking your users’ money: In-app billing from start to best practices
34mTesting In App Billing the Easy Way
46mA deep dive into
44mThe State off in app purchases on Android
36mGrow and optimize your subscriptions with new Google Play features
30mWhat's new with Play Billing
35mIn-App Billing Version 3
23mIn-App Subscriptions for all Android devices