All packsPlay Billing MachinerySolve
google play purchase not acknowledged 3 days auto refund
Three days to acknowledge, or Google refunds the purchase for you
A purchase not acknowledged within three days is automatically refunded and its entitlement revoked -- and the clock starts at PENDING to PURCHASED, not at purchase initiation (decision 6).
This is one of the things Play Billing Machinery already handles. Sell subscriptions in your Android app on the Billing Library version Google requires from 31 August 2026.
Is this you?
Google's docs say acknowledgement "must be done within three days so that the purchase isn't automatically refunded and entitlement revoked" -- in one easy-to-read-past sentence. Miss the window on any initial purchase and Google reverses it unprompted: the customer paid, and days later the money is back and the feature is gone, with no error anywhere in the app's own logs.
Why this one is easy to get wrong
A purchase flow that completes, unlocks the feature, and never throws looks entirely done -- acknowledgement reads as a formality rather than a hard deadline with an automatic penalty. The bug surfaces as unexplained churn in the first week of purchases, which looks like a business problem long before anyone suspects a missing API call.
What you get instead
The pack acknowledges every initial subscription and non-consumable purchase server-side, tracks acknowledgementState from fetched state before ever retrying, and specifically handles the prepaid-plan variant (half the plan duration for plans under a week -- 36 hours on a 3-day plan). A license tester compresses the window to three minutes, which is what turns this failure mode into a same-afternoon test rather than a three-day wait.
Source: ARCHITECTURE.md decision 6 — checkable in the pack you receive
How you actually use this
You don’t install a library or wire up an SDK. Your own coding agent builds the code in your project, and you keep it — no runtime dependency on us.
Step 1
Download and unzip
You get a folder: the docs that tell an agent what to build, a starting skeleton, and the test suite that decides when it's done.
Step 2
Open it in Claude Code or Cursor
Point your coding agent at the folder. Nothing to install, no account with us, no API key.
Step 3
Paste one prompt
The pack contains the exact prompt. Paste it as your first message and leave it alone — it works through the build itself, choosing a cheaper or stronger model per task.
Step 4
Run ./verify.sh
One command. It prints a pass or fail for every check. Green means the build is done — the same script we ran to produce the receipt on this page.
Typical build: about 33 minutes of your agent working, mostly unattended. Then you integrate the working module into your app the way you would any code you’d written yourself.
Why you can believe this
3 of 3 runs passedWe ran this pack from an empty folder 3 times and published exactly what happened — every check, the model, the token cost, the wall time. Not a testimonial, and not our opinion: the same verify.sh you run yourself. Read the full receipt →