The latest articles on DEV Community by Samya (@samya_1bdf15f0ed2fe95ea25). https://dev.to/samya_1bdf15f0ed2fe95ea25 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4203280%2F78353a73-40bf-4b0c-9661-88956cdd624d.png https://dev.to/samya_1bdf15f0ed2fe95ea25 en Samya Fri, 23 Oct 2026 19:02:20 +0000 https://dev.to/kordelis/your-app-unlocked-the-purchase-did-google-play-get-the-confirmation-51k5 https://dev.to/kordelis/your-app-unlocked-the-purchase-did-google-play-get-the-confirmation-51k5 <p>Someone buys a chapter in your Android app. It opens, and they start reading. From the app screen, the purchase looks finished.</p> <p>There is one more result to check: did Google Play receive confirmation that your app processed it?</p> <p>The <a href="https://www.youtube.com/shorts/pOrUZcvjJIE" rel="noopener noreferrer">30-second illustration</a> shows those two outcomes side by side. It is an example flow, not a recording of a customer purchase.</p> <h2> What can go wrong </h2> <p>For a completed purchase, your app needs to verify the purchase, grant the right access, and tell Play it was processed. If an eligible purchase is left unacknowledged, Play can automatically refund it and revoke the entitlement. A consumable follows a different final step: consuming it also fulfills the acknowledgment requirement. A pending purchase is different again; it should not unlock new access until it becomes <code>PURCHASED</code>.</p> <h2> A test worth running </h2> <p>Use a <strong>license tester</strong> and a Play test payment method for a non-consumable item. After the purchase completes, check both outcomes:</p> <ol> <li>Can the person open exactly what they bought?</li> <li>Is the purchase acknowledged in Play, rather than only marked accessible in the app?</li> </ol> <p>Then close and reopen the app. The correct access should still be there, without a second grant or a new purchase prompt. Repeat the exercise for any consumable or pending flow you support; their expected outcomes differ. Play's test-purchase timing is accelerated, so do not use the test refund window as the production deadline.</p> <p>This small test catches a gap that is easy to miss when you watch only the app screen. It also gives you two concrete places to investigate when a purchase is later refunded: the app's entitlement record and Play's processing state.</p> <p><strong>References:</strong> <a href="https://developer.android.com/google/play/billing/integrate#process" rel="noopener noreferrer">Google Play purchase processing</a> · <a href="https://developer.android.com/google/play/billing/test" rel="noopener noreferrer">Testing Play Billing</a></p> <p><em>Prepared with AI assistance and checked against the linked Google documentation.</em></p> android testing kotlin googleplay