Troubleshooting Apple App Store Subscriptions: Missing appAccountToken

Symptoms

• An App Store subscription purchase succeeds, but the expected subscription/account association does not occur.
• You see Apple transaction data, but the appAccountToken value is missing or blank.
• Renewals or upgrades appear disconnected from the original customer/account mapping.

Common Causes

• appAccountToken not set in the purchase request (most common).
• Incorrect field used (e.g., using a deprecated or unrelated identifier rather than appAccountToken).
• Token inconsistency: a new token is generated per purchase/renewal rather than reusing the same UUID for the same customer.

How to Confirm

1. Inspect your App Store transaction data (signed transaction payload / decoded transaction info).
2. Confirm whether appAccountToken is present and non-empty.
3. Validate it is a UUID format (example: 6de8ef5f-ac46-4b9f-9347-f5f6681349a0).

TransactionInfo={
  appAccountToken=,
  bundleId=...,
  environment=Production,
  productId=...,
  transactionId=...
}

How to Fix

1. Update your iOS implementation to set appAccountToken during the purchase flow (use a UUID you generate and store for the customer).
2. Ensure the same customer always uses the same token (do not regenerate for renewals/upgrades).
3. Test in Sandbox and confirm the token is returned in the transaction payload.
4. Deploy to Production and confirm the Production payload includes appAccountToken.

What to Send Support

If you still need help, include:

• Environment: Sandbox or Production
• Transaction UUID(s) and timestamp(s)
• The appAccountToken value you expected (if any)
• The TransactionInfo object payload containing appAccountToken