All packsPlay Billing MachinerySolve
purchases.subscriptionsv2 no acknowledge method deprecated v1
The API you're told to use has no way to do the one thing you must do
purchases.subscriptionsv2 -- the current, correct resource for reading subscription state -- has no acknowledge method at all; it lives on the deprecated v1 purchases.subscriptions (decision 7).
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?
An agent building a clean v2-only backend reads subscription state from purchases.subscriptionsv2.get and looks for an acknowledge method on the same resource -- and there isn't one. Acknowledgement only exists on the otherwise-deprecated v1 purchases.subscriptions resource, so a backend that avoids "deprecated" APIs on principle silently ships without ever acknowledging a purchase, triggering the three-day auto-refund on every one.
Why this one is easy to get wrong
Reading v2's own API reference for subscriptionsv2 turns up no acknowledge call, and the deprecated label on v1 reads as a clear signal to avoid it entirely -- there's no cross-reference in the v2 docs pointing back to the one v1 method that's still required. The most defensible-looking choice (avoid deprecated APIs) is the one that produces the bug.
What you get instead
The pack reads subscription state from purchases.subscriptionsv2.get and explicitly still calls purchases.subscriptions.acknowledge -- the v1 method -- to satisfy the acknowledgement window, treating acknowledgement as idempotent by checking acknowledgementState first. One-time products use the parallel purchases.products.acknowledge call instead.
Source: ARCHITECTURE.md decision 7 — 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 →