All packsPlay Billing MachinerySolve
google play subscription grace period cancelled still entitled
Grace period and cancelled both still mean entitled -- agents get both backwards
SUBSCRIPTION_STATE_IN_GRACE_PERIOD is still entitled during a failed payment retry, and CANCELED remains entitled until expiryTime -- the two rows the entitlement truth table names as commonly reversed (decision 11).
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?
Mapping subscriptionState to an entitlement boolean by intuition gets two states backwards in opposite, expensive directions: treating a grace-period subscriber (payment failed, Google is still retrying) as not entitled locks out a paying customer mid-recovery, while treating a cancelled subscriber as immediately not entitled cuts off someone who already paid through the end of their period.
Why this one is easy to get wrong
Both state names read like they should mean "not entitled" in plain English -- "grace period" sounds provisional, and "cancelled" sounds over. The actual Play semantics (both still active) require reading Google's own subscriptionState reference table rather than inferring behavior from the enum name.
What you get instead
Decision 11 ships the entitlement truth table directly: IN_GRACE_PERIOD is yes, CANCELED is yes until expiryTime, and everything else (ON_HOLD, PAUSED, EXPIRED, PENDING) is no, fail-closed on UNSPECIFIED. A voidedPurchaseNotification overrides every row in the table and revokes immediately, regardless of what the current subscriptionState says.
Source: ARCHITECTURE.md decision 11 — 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 →