StoreKit introductoryOfferEligibility: safe retry after JWS expiration

How should a server safely retire or renew an unused JWS for Product.PurchaseOption.introductoryOfferEligibility(compactJWS:) after cancellation or interruption?

Our application allows a first-purchase discount once per application account across payment platforms. We bind the signed eligibility request to a verified Apple app transaction, product, and purchase attempt, persist the exact JWS, and reuse it for the same attempt. Once a paid purchase is verified, we consume the application's eligibility. We do not automatically issue another nonce after cancellation, a signature error, or an empty transaction history.

Apple's JWS documentation describes a one-time nonce and expiration calculated from iat, and says not to include exp:

https://developer.apple.com/documentation/storekit/generating-jws-to-sign-app-store-requests

I could not find the lifetime or a supported retirement/renewal procedure for the introductory-offer-eligibility audience. Keeping an unusable authorization forever would prevent the customer from trying another checkout; replacing it without retiring the original might leave two redeemable authorizations.

What we observed

Environment: Xcode 27.2 (27B52), macOS 26.6.2, physical iPhone 16 with iOS 27.0, Apple Sandbox.

  1. Verify the Apple-signed AppTransaction and issue one eligibility JWS.
  2. Start the purchase using that JWS, then cancel the payment sheet (userCancelled).
  3. Terminate and relaunch the app without resetting purchase history or replacing the authorization.
  4. Retry the same product and Apple account using the byte-for-byte identical JWS.
  5. Complete the Sandbox purchase and verify the Apple-signed transaction on an isolated server.

The successful verification happened about 164 seconds after issuance. This is one successful cancellation/retry observation, not a reproduced expiration failure or proof of a general validity/nonce-consumption rule. It also did not verify our intended introductory price.

The purchase call uses the persisted value:

let result = try await product.purchase(options: [
    .introductoryOfferEligibility(compactJWS: existingJWS)
])
Supported lifecycle questions
  1. What is the validity period derived from iat, including clock-skew allowances and any Sandbox/production differences? Which API or documented error can establish that a previously issued authorization is definitively unusable, rather than merely absent from transaction history?
  2. When is the nonce consumed, and what happens after userCancelled, interruption, pending approval, expiration, or an uncertain result? Is invalidOfferSignature specific enough to distinguish expiration from consumption, account mismatch, or a bad signature?
  3. Is it supported to keep the same nonce and all bindings, update only iat, and re-sign? If so, is one-time use enforced across every version and for what retention period? If renewal requires a new nonce, how can the prior authorization be invalidated first? Is there another recommended recovery flow that prevents duplicate redemption without indefinitely blocking checkout?

DTS directed us to ask this lifecycle question on the forums. A sanitized minimal Xcode project was already supplied privately to DTS; it demonstrates the observed cancel/relaunch/same-JWS retry, not an expiration failure. We would appreciate a supported procedure or documentation reference.

Please file a Feeback report in Feedback Assistant to have these behaviors documented.