Recover purchases your app started but never finished.

Zoruko finds the gaps where checkout, app lifecycle, network timing, or store callbacks interrupt the purchase path, then ships replay-safe recovery logic as a pull request.

Find lost purchases Open sample audit

01initiated

02interrupted

03queued

04confirmed

Replay-safe dispatch

Replay-safestalled attempts are retried without double-granting entitlement

State-awarepending, purchased, cancelled, and failed states stay separate

Backend-firstpurchase tokens are verified before the user receives benefits

01initiated

02interrupted

03queued

04confirmed

Replay-safe dispatch

Find the exact interruption point.

Lost purchases usually happen between intent and proof: the store sheet opens, the app backgrounds, the callback fails, or the server never records the final state.

Trace purchase initiation, callback handling, token verification, and entitlement writes.
Detect stale initiated purchases that never reached a final state.
Keep ambiguous cases out of ad-platform learning until they are resolved.

StoreKit / Playsettled purchase

Server truthvalidated receipt

Ad platformsdeduped event

purchase.signal.ts

if (receipt.acknowledged) {
  send("Purchase", {
    value,
    event_id,
    source: "server"
  })
}

Replay signals without creating duplicate purchases.

Recovery should not mean firing the same event twice. Zoruko adds durable keys, server checks, and dispatch guards around every replay path.

Use stable recovery keys for app reopen, network retry, and backend reconciliation.
Verify token state before granting entitlement or sending ad events.
Keep recovery evidence attached to the purchase event ledger.

scan app/
trace billingClient
trace StoreKit.Transaction
match server event_id
plan 3 safe fixes

purchase.tsbilling.ktcapi.tsrefund.ts

Turn recovery into a reviewed PR.

The output is not a vague recommendation. It is a scoped change that fixes the broken purchase path and documents how the state machine should behave.

Patch handlers for foreground, background, and server notification paths.
Add tests around duplicate callbacks and delayed purchase completion.
Document what Meta, TikTok, and your backend should receive after recovery.

Aligned with official purchase lifecycle guidance.

The recovery flow is built around the store lifecycle patterns documented by Apple and Google, not hidden billing behavior.

Google Play purchase lifecycleBackend systems should track purchase lifecycle events and entitlement changes promptly.Google Play Billing integrationPurchase processing includes verification, entitlement delivery, and acknowledgement.

Recover real buyers without teaching ads bad data.

Run a repo scan and see where your purchase path drops confirmed customers.

Run recovery audit

Recover purchases your app started but never finished.

Zoruko finds the gaps where checkout, app lifecycle, network timing, or store callbacks interrupt the purchase path, then ships replay-safe recovery logic as a pull request.

Find lost purchases Open sample audit

01initiated

02interrupted

03queued

04confirmed

Replay-safe dispatch

Replay-safestalled attempts are retried without double-granting entitlement

State-awarepending, purchased, cancelled, and failed states stay separate

Backend-firstpurchase tokens are verified before the user receives benefits

01initiated

02interrupted

03queued

04confirmed

Replay-safe dispatch

Find the exact interruption point.

Lost purchases usually happen between intent and proof: the store sheet opens, the app backgrounds, the callback fails, or the server never records the final state.

Trace purchase initiation, callback handling, token verification, and entitlement writes.
Detect stale initiated purchases that never reached a final state.
Keep ambiguous cases out of ad-platform learning until they are resolved.

StoreKit / Playsettled purchase

Server truthvalidated receipt

Ad platformsdeduped event

purchase.signal.ts

if (receipt.acknowledged) {
  send("Purchase", {
    value,
    event_id,
    source: "server"
  })
}

Replay signals without creating duplicate purchases.

Recovery should not mean firing the same event twice. Zoruko adds durable keys, server checks, and dispatch guards around every replay path.

Use stable recovery keys for app reopen, network retry, and backend reconciliation.
Verify token state before granting entitlement or sending ad events.
Keep recovery evidence attached to the purchase event ledger.

scan app/
trace billingClient
trace StoreKit.Transaction
match server event_id
plan 3 safe fixes

purchase.tsbilling.ktcapi.tsrefund.ts

Turn recovery into a reviewed PR.

The output is not a vague recommendation. It is a scoped change that fixes the broken purchase path and documents how the state machine should behave.

Patch handlers for foreground, background, and server notification paths.
Add tests around duplicate callbacks and delayed purchase completion.
Document what Meta, TikTok, and your backend should receive after recovery.

Aligned with official purchase lifecycle guidance.

The recovery flow is built around the store lifecycle patterns documented by Apple and Google, not hidden billing behavior.

Recover real buyers without teaching ads bad data.

Run a repo scan and see where your purchase path drops confirmed customers.

Run recovery audit