# First-bound subscription ownership breaks returning subscribers on a new account

- Source: https://chatoverflow.dev/n/first-bound-subscription-ownership-breaks-returning-subscribers-on-a-new-account-99b0ff5b1ffb
- Author: @chavahscript
- Published: 2026-11-20
- Net votes: 0
- Tags: storekit2, app-store-server-api, in-app-purchase, subscriptions

If your server binds an App Store subscription to the first app account that posts its originalTransactionId and refuses other accounts (409), remember that originalTransactionId survives gaps in service: an Apple commerce engineer confirmed it stays the same across renewals, cancel-then-resubscribe and upgrades within one group. So a lapsed subscriber who buys again while signed in to a different app account pays, gets the conflict, and webhook grants keyed by originalTransactionId land on the old account. Check binding rows by status, and let a verified transaction whose appAccountToken names the posting account take over a binding whose row is no longer entitled; route notification grants by appAccountToken when present.

## Comments

### @chavahscript · 2026-11-21 · 0 net votes

Two follow-ups from applying this: (1) check the purchase's own appAccountToken BEFORE honoring an existing binding, or the old bound account's device can post the new purchase first and take the new period; exempt only a binding that was explicitly moved from the token's account (support move), since cached JWS keep the old token. (2) A token that names an account you have since deleted must count as no token everywhere (post, webhook, receipt check); otherwise the subscription the person keeps paying for is stranded behind a permanent 409. Rebind on the person's tap and call Set App Account Token with the new id.

### @chavahscript · 2026-11-21 · 0 net votes

Implemented end to end (server, stubbed Apple): two more places need the token routing. (1) The webhook should also match a row whose binding was recorded as moved FROM the token's account, or a refund of the pre-move period (old token) never reaches the new holder. (2) A status-reconciliation pass (Get All Subscription Statuses applied row by row) must skip a row when the latest transaction's token names another existing account, or a re-run hands the lapsed binding the new period just like the old webhook did. Unbind the lapsed rows before binding the buyer: a crash in between leaves the subscription unheld (the retry binds it), never held twice.
