Skip to main content
Skip to navigation

Stop tracking revenue

How to stop RevenueCat from recording new purchases and renewals while preserving your project history.

AIAsk AIChatGPTClaude
Last reviewed: September 11, 2026

This guide shows you how to stop RevenueCat from recording new purchases and renewals while preserving your project and historical data. You'll disconnect every client, server, store, and external billing path that can send purchase updates to RevenueCat, then verify that tracking has stopped.

RevenueCat does not have a self-service project pause. Removing the SDK from your latest app release is not enough if older releases, your backend, store notifications, external billing integrations, or RevenueCat's receipt refreshes can still provide purchase updates.

❗️Move customer access off RevenueCat first

Do not disconnect an active app until it no longer relies on RevenueCat Entitlements or CustomerInfo to provide access. After tracking stops, RevenueCat cannot reliably observe renewals, cancellations, billing issues, or expirations.

Prerequisites​

  • Access to your app code, backend, and each connected store or payment provider
  • A replacement for purchase validation and subscription access if the app remains active
  • A list of app versions and backend jobs that may still communicate with RevenueCat

1. Audit every purchase ingestion path​

Identify every way purchase data can reach RevenueCat. Check for:

  • RevenueCat SDK configuration in current and older app releases
  • Calls to syncPurchases(), restorePurchases(), or the POST /receipts API
  • Backend jobs that post receipts, purchase tokens, or external subscriptions
  • Apple App Store Server Notifications
  • Google Real-Time Developer Notifications
  • The Track new purchases from server-to-server notifications setting for Apple or Google apps
  • Stripe, Paddle, Web Billing, or other external purchase integrations

Also identify features that depend on fresh purchase data, including Entitlements, CustomerInfo, webhooks, third-party integrations, Charts, and customer support workflows.

⚠️Older app versions may continue submitting receipts

Installed app versions cannot be changed remotely. Even after you release an update without RevenueCat, older versions may continue submitting receipts until customers update or stop using them.

2. Export the data you need​

Export any data you need before disconnecting the project. Depending on your setup, this may include:

If you need a receipt export that is not available from the dashboard, contact RevenueCat Support before continuing.

3. Stop app and backend submissions​

Release an app version that no longer configures or calls the RevenueCat SDK. Move purchase validation and customer-access logic to your replacement system before releasing the update.

Stop every backend process that sends purchases to RevenueCat. This includes direct receipt submissions, purchase-token imports, subscription migrations, and external purchase synchronization.

Removing the SDK only affects customers who install the new version. Continue to the next steps to stop store-side updates and RevenueCat refreshes for customers on older versions.

4. Disconnect store and external purchase updates​

For each Apple app:

  1. Turn off Track new purchases from server-to-server notifications in RevenueCat.
  2. Remove the RevenueCat notification URL from the production and sandbox App Store Server Notifications fields in App Store Connect.
  3. Stop any backend process that forwards Apple notifications or receipts to RevenueCat.

For each Google Play app:

  1. Turn off Track new purchases from server-to-server notifications in RevenueCat.
  2. Remove the RevenueCat Pub/Sub topic from Real-time developer notifications in Google Play Console.
  3. Stop any backend process that forwards Google purchase tokens or notifications to RevenueCat.

If you use Stripe, Paddle, Web Billing, or another external purchase source, stop forwarding new purchases and subscription updates to RevenueCat. Review the provider-specific integration before disconnecting it so your replacement system continues receiving the events it needs.

5. Ask RevenueCat Support to complete the disconnection​

Store credentials can allow RevenueCat to refresh receipts it already knows about, even after SDK and notification traffic stops. Contact RevenueCat Support and ask to stop purchase tracking while preserving the project.

Include:

  • The RevenueCat project ID
  • Every affected app
  • Confirmation that your app no longer relies on RevenueCat Entitlements or CustomerInfo
  • Confirmation that SDK, API, store-notification, and external purchase inputs have been disabled

The project owner must make or confirm the request. Support can then clear the applicable store credentials and remove existing receipts from RevenueCat's background refresh system without deleting the project's historical data.

For Apple apps, removing only one credential may leave another validation path active. For example, older StoreKit 1 integrations can use an app-specific shared secret even when an In-App Purchase Key has been removed. Support must clear every applicable credential and receipt-refresh path.

6. Verify that tracking stopped​

Record a cutoff time and monitor the project's recent transactions and Monthly Tracked Revenue. The success criterion is that RevenueCat records no new purchases or renewals after the disconnection finishes.

Do not use these as immediate success criteria:

  • MTR or historical revenue reaching zero. Revenue already recorded in the billing period still counts for that period, and historical reports remain unchanged. Revenue from other apps or projects on the account can also continue contributing to account-level MTR.
  • Active Subscriptions or MRR reaching zero. The Overview page and standard charts use each subscription's last known expiration date, so subscriptions wind down as their recorded periods expire. V3 and other event-driven metrics may instead keep counting active subscriptions and MRR indefinitely because RevenueCat never receives the expiration events. Churn metrics also do not reflect those unobserved expirations.
  • Store subscriptions ending. Disconnecting RevenueCat does not cancel subscriptions or stop Apple, Google, Stripe, or another provider from charging customers.

RevenueCat also stops sending webhook and third-party integration events for the disconnected purchase sources. This includes expiration events that would otherwise occur after the cutoff.

If new transactions continue after a short processing window, check for an old app release, backend receipt submission, store notification, external billing integration, or remaining receipt-refresh path.

Delete the project instead​

Delete the project only if you do not need its history or configuration. Project deletion is immediate and irreversible. App versions that still use the project will lose access to RevenueCat services, but customers' store subscriptions will remain active.

To delete your entire RevenueCat account, first delete every project. See Billing and account settings for the complete shutdown sequence.

Next steps​

Was this page helpful?