Is dynamic fallback to Sandbox API correct when receiving error 4040010 (TransactionIdNotFoundError) during App Review?

App & System Services StoreKit
kamesenin OP
Created
Replies 1
Boosts 0
Views 106
Participants 2

Hi, During the App Review process, a test purchase was made using what appeared to be a production Apple account. When our app server sent this transactionId to the Production App Store Server API, it returned the error code 4040010 (TransactionIdNotFoundError). To handle this gracefully and prevent review rejections, we are considering implementing a dynamic fallback mechanism on our app server. Specifically, when the Production API returns 4040010, the server will automatically retry the request using the Sandbox App Store Server API URL. Could you please clarify the following points regarding this design? Is it expected behavior for an App Review purchase to return 4040010 on the Production API, and can it be successfully verified by routing it to the Sandbox API? Is this dynamic fallback logic (Production API ➔ if 4040010 ➔ Sandbox API) a recommended and officially supported best practice for handling App Review and TestFlight transactions?

Any confirmation or advice from Apple engineers or the community would be greatly appreciated.Thank you.

Replies  1
Boosts 0
Views  106
Participants  2
DTS Engineer OP
Apple

From TransactionIdNotFoundError:
Don’t unlock the service or content associated with the transaction ID for the app bundle ID and environment that you indicate in the request unless you successfully resolve this error. To resolve this error, check your request to ensure that:

  • The JSON Web Token (JWT) payload contains the bundle ID (bid) of your app that’s associated with the transaction ID. For more information, see Generating JSON Web Tokens for API requests.
  • You’re making the request in the same environment, production or sandbox, that generated the transaction ID.
    In rare cases, you might get this error for transaction IDs that previously returned data successfully. Don’t unlock the service or content for the app bundle ID and environment in the request if you’re unable to resolve this error using the steps above.