Yes. Apple requires a 'Restore Purchases' mechanism for any app with in-app purchases. Failure to include one is a common App Review rejection reason. Place it visibly on your paywall and in settings.
When the user taps restore, the app requests the user's transaction history from Apple or Google. The receipts are validated (server-side via Botsi recommended), and entitlements are granted based on active subscriptions. This works across device upgrades, reinstalls, and family sharing.
Common issues: using a different Apple ID than the original purchase, network connectivity problems during verification, server-side validation failures, and expired subscriptions the user thought were active. Provide clear error messages and fallback to support contact for edge cases.
A backend mechanism that limits how often users can trigger certain subscription-related actions (e.g., restore, trial start, promo redemptions) within a set time frame. This helps prevent abuse, fraud, and system overload.
When a previously churned or lapsed subscriber returns and resumes their subscription. Reactivations are a part of lifecycle marketing and often driven by email/push campaigns, pricing incentives, or product improvements.
Revenue generated on a consistent, repeatable basis through subscription renewals. Recurring revenue is the foundation of subscription businesses and a key metric for forecasting, valuation, and capital efficiency.
The percentage of in-app purchases or subscriptions that are refunded due to user dissatisfaction or platform policy. High refund rates can signal poor value perception, billing issues, or onboarding problems and may impact platform standing or reported revenue.
The continuation of a subscription after a billing period ends, either manually or through auto-renew. Renewals are a core component of recurring revenue and serve as key milestones in a user's lifecycle.
Botsi automatically shows the right price to every user. Stop guessing and start growing.