Skip to content
AppDues
Log in
Contact salesSign up

App Store Receipt Validation

Paste a receipt to have it checked against the App Store.

If the receipt includes subscriptions, add the app-specific shared secret so the check can read them. The tool uses verifyReceipt under the hood to help you quickly decode and debug.

What each field does

Use this map to decide what to paste before you submit.

Receipt validation error codes

When a check fails, the response carries a numeric code. The table below lists the receipt validation error codes and what each one means. Use it to tell a malformed receipt apart from an environment mismatch or an expired subscription.

Diagnose a failed check

Start with the code, then act on it. A 21002 means the receipt-data property was malformed or missing, so re-copy the receipt before retrying. A 21007 means a test-environment receipt was sent to production for verification, so resend it to the test environment. A 21008 is the reverse: a production receipt sent to the test environment, which should go to production instead. A 21006 means the receipt is valid but the subscription has expired; the receipt data is still decoded and returned alongside the code, and this code is only returned for iOS 6 style transaction receipts for auto-renewable subscriptions. A 21010 means the receipt could not be authorized and should be treated the same as if a purchase was never made.

Privacy and data handling

The page states that submitted data is sent securely and remains private. {{OWNER_ACCOUNT_REQUIREMENT}}

ConfigureTargetTest
Receipt validation error codes
CodeDescription
21000The App Store could not read the JSON object you provided.
21002The data in the receipt-data property was malformed or missing.
21003The receipt could not be authenticated.
21004The shared secret you provided does not match the shared secret on file for your account.
21005The receipt server is not currently available.
21006This receipt is valid but the subscription has expired. When this status code is returned to your server, the receipt data is also decoded and returned as part of the response. Only returned for iOS 6 style transaction receipts for auto-renewable subscriptions.
21007This receipt is from the test environment, but it was sent to the production environment for verification. Send it to the test environment instead.
21008This receipt is from the production environment, but it was sent to the test environment for verification. Send it to the production environment instead.
21010This receipt could not be authorized. Treat this the same as if a purchase was never made.
21100 - 21199Internal data access error.

Codes and descriptions are reproduced as supplied. Availability of the verifyReceipt endpoint may change over time; check current App Store documentation before relying on it.

Frequently asked questions

Why should I use this?

To decode a receipt and see what the App Store returns, or to identify why a purchase or subscription check failed. It saves you from writing a throwaway script just to read one receipt.

How does it work?

Paste the receipt, add the app-specific shared secret if the receipt contains subscriptions, and submit. The tool uses verifyReceipt under the hood to decode and debug the receipt.

Is it safe?

The page states that data is sent securely and remains private. {{OWNER_SECURITY_GUIDANCE}}

Are you storing any information?

The page states that submitted data remains private. {{OWNER_DATA_RETENTION_POLICY}}

Where can I learn more about App Store receipts?

The error-code table on this page lists the receipt validation error codes. For the receipt format and server-side verification details, consult Apple's official App Store receipt documentation.