Cancellation Revenuecat: Easy Method

What is Revenuecat

Overview

RevenueCat is a subscription management and analytics service that sits between your app and platform billing systems (App Store, Google Play, Stripe). It simplifies implementing in‑app subscriptions, centralizes receipts and entitlements, and provides dashboards, webhooks and APIs to manage purchases across platforms.

The service does not replace the App Store, Google Play, or Stripe for billing; it synchronizes subscription state and helps developers read and act on purchase events.

How to cancel Revenuecat

Which cancellation steps you follow depends on where the subscription was purchased. Below are practical steps for users and developers to cancel subscriptions tied to RevenueCat-managed products.

• App Store (iOS) - Users must cancel directly in their Apple ID subscriptions (Settings on device or via Apple Support for subscriptions). Developers cannot cancel subscriptions for users. Advise users to turn off auto‑renew at least 24 hours before the next billing date; RevenueCat usually detects the cancellation within a few hours if Apple server notifications are enabled.
• Google Play - Developers may cancel auto‑renewing subscriptions on behalf of customers using the Google Play Console or Google Play Developer API. If you cancel via Google Play or through RevenueCat’s dashboard/API, RevenueCat will detect the change automatically (typically within a few hours when Play notifications are enabled).
• Web (Stripe) - Developers can cancel subscriptions via the Stripe Dashboard or Stripe REST API. When you cancel in Stripe, RevenueCat will reflect the cancellation; using RevenueCat’s API or dashboard to manage Stripe subscriptions will also update RevenueCat’s records.

What happens when you cancel

When a subscription is canceled, future auto‑renewals stop and the subscription will not renew at the next billing date. Access behavior depends on the platform and your entitlement settings: many subscriptions remain active until the end of the already‑paid period (end of current billing cycle), unless a platform issues an immediate revocation.

RevenueCat monitors platform notifications and receipt state and updates user entitlements accordingly. Detection is usually automatic within hours when server notifications/webhooks are configured; if notifications are not enabled, there can be delays. Your RevenueCat dashboard and exported data will reflect the subscription state changes.

Will I get a refund?

Refunds are handled by the platform that processed the payment, not directly by RevenueCat.

For App Store purchases, Apple controls refunds and developers cannot issue refunds themselves; users must contact Apple Support to request a refund. For Google Play purchases, developers can issue refunds; RevenueCat supports issuing refunds through its dashboard or REST API and will detect refunds (propagation can take up to ~24 hours). Refunding from the Google Play Console is possible but may not be reliably tracked by RevenueCat. For web payments processed by Stripe, refunds are issued via the Stripe Dashboard or API; RevenueCat will detect these refunds (often within a couple of hours), and developers can re‑post subscription state to speed updates if needed.

Revenuecat plans and pricing

Your consumer rights in Canada

Under Canadian law there is no automatic 14‑day cooling‑off period for digital content delivered instantly (such as in‑app subscriptions). That means consumers generally do not have a statutory right to cancel and obtain a refund just because a short period has passed after purchase. Refunds and cancellation rights depend on the platform’s policies (Apple, Google, Stripe) and any merchant or developer‑provided refund policy.

Customer experiences

Users commonly praise RevenueCat for simplifying subscription integration and saving development time, and many report that getting started and hooking up common flows is straightforward. Quick responses from support and the unified view across platforms are noted positives.

On the other hand, some customers report issues: documentation gaps, occasional API inconsistencies or downtime, delayed syncs, and concerns about reporting accuracy (for example, VAT handling or revenue figures). Support responsiveness and pricing at larger scale are also recurring criticisms in reviews.

Documentation checklist

• Confirm purchase platform for each affected user (App Store, Google Play, Stripe/web).
• Enable and verify server notifications/webhooks on Apple, Google and Stripe to speed detection.
• Export receipts, subscriber lists and entitlement state from RevenueCat before changes.
• Decide whether to cancel via platform console (Google Play/Stripe) or instruct users to cancel (App Store).
• Review refund policies for each platform and decide who will handle refund requests.
• Plan entitlement updates and communicate any access changes to users.

Common mistakes

One frequent mistake is attempting to cancel or refund iOS subscriptions on behalf of users - Apple does not permit developer‑initiated cancellations or refunds, so users must cancel via their Apple ID and request refunds through Apple Support. Another common error is assuming cancellations or refunds are instantaneous - platform notifications and RevenueCat syncing can take hours or longer, so access might remain until the detection completes. Developers also sometimes forget to export subscriber data or to disable entitlements, resulting in continued access after cancellation.

Comparative recap

After cancelling

After you cancel a subscription, export and archive the relevant subscriber records and receipts from RevenueCat for your records, confirm entitlement changes in your app, and notify affected users about access timelines and refund procedures. If customers request refunds, direct them to the appropriate platform channel: Apple Support for App Store refunds, the Google Play refund flow or your developer refund process for Play purchases, and Stripe for web payments.

Helpful documentation and support links: RevenueCat docs (https://www.revenuecat.com/docs), Apple subscriptions & refunds (Apple Support - subscriptions), Google Play subscriptions help (Google Play - subscriptions), and Stripe refunds docs (Stripe - refunds). If you need to send a formal cancellation notice by registered mail, use the address below.

Address

Use this mailing address for sending cancellation notice via registered mail (raccomandata A/R): 56 Broad St, Ste 14028, Boston, MA 02109, USA.