In short: one validation typically means one in-app purchase.

One validation is deducted from your monthly quota for each successful receipt validation on a new purchase, like a new product/subscription purchase or subscription renewal. Also, for non-consumable purchases a transaction is deemed as new after it expired (see Transaction and User Storage) and the user invoking the restore transactions workflow again. Failed receipt validations (fake purchases) or adding the same transaction to a different user device do not count against your monthly quota.

Transaction Storage ensures that transaction receipts are unique across your app. Different users will not be able to validate a purchase more than once in order to unlock content they do not rightfully own.

The inventory of users (subscriptions and non-consumables) can be stored in the cloud and retrieved by logging into your app. Without interaction, this inventory is available for the duration stated in the plan. The duration is reset when adding new transactions. After expiration, the inventory can be restored by invoking the native restore transactions workflow.

Simple Webhooks do not have a retry mechanism in case the receiving server sends a failed response. When using Reliable Webhooks, failed messages are put into a queue and retried multiple times.

The reset date is determined by your app's monthly billing date. On that date, the validation quota resets at 00:00 UTC.

Yes! If you see a sudden increase in validations for your app, you can upgrade to extend your quota immediately. Whenever changing plans, the billing cycle resets.

Absolutely. If you cancel your paid subscription, you will still be able to use its remaining quota and features until the billing cycle ends. At that date, your app will convert into the free plan.