Move your existing in-app purchases to RevenueDot and keep every subscriber

• Checking purchases with the store. RevenueDot verifies StoreKit 2 signed transactions with Apple and reads Google Play purchase tokens with the Play Developer API. Your server no longer trusts the device.
• Renewals, cancellations, billing problems and refunds. App Store Server Notifications and Google Play real-time notifications update each customer, and webhooks tell your backend.
• One answer to "is this user premium?" A customer who pays on iOS, Android or the web has the same access everywhere.
• Paywalls, experiments and charts. Paywall templates, price tests and 43 charts work from the first purchase.

1. 01

   Create a free project and add your store apps

   Start for free on RevenueDot Cloud and add your App Store, Google Play or Stripe app with its credentials. Paste RevenueDot's notification URLs into App Store Connect and Google Play. If your own server receives those notifications today, set the app's forward URL to it, so it keeps getting every notification while you move.

2. 02

   Import your products

   Click Import products. RevenueDot reads App Store Connect, Google Play or Stripe and creates each product with its type and duration. Attach them to an entitlement such as pro (the access your app checks) and put them in the offering your paywall shows. See import products.

3. 03

   Install the RevenueDot SDK

   Add the RevenueDot SDK for your platform and configure it with your app's key and your own user ID, so purchases land on the right customer. Replace your purchase calls with the SDK's: load the offering, buy a package, check the entitlement.

4. 04

   Bring your subscribers over

   Call syncPurchases() once on the first launch of the update. It sends the device's purchases to RevenueDot, which checks them with the store. To also record subscribers who have not opened the update yet, turn on track_new_purchases for the app.

5. 05

   Check access from your backend

   Read a customer's active entitlements with a secret key, or receive webhooks for every renewal, cancellation and refund. Then retire your own receipt code.

The RevenueDot SDK is built from RevenueCat's open-source SDK (MIT license), so your code imports RevenueCat and calls Purchases. It sends every request to RevenueDot and needs no RevenueCat account. Android, React Native and Flutter have the same calls; see the SDK guides.

import RevenueCat   // the module name of the open-source SDK the RevenueDot SDK is built from

Purchases.configure(withAPIKey: "appl_...", appUserID: currentUser.id)

// Once, on the first launch of this update: send the device's existing App Store purchases to RevenueDot.
if !UserDefaults.standard.bool(forKey: "revenuedotSynced") {
    _ = try? await Purchases.shared.syncPurchases()
    UserDefaults.standard.set(true, forKey: "revenuedotSynced")
}
let isPro = try await Purchases.shared.customerInfo().entitlements["pro"]?.isActive == true

• Adapty or Qonversion: replace their SDK with the RevenueDot SDK. Your App Store and Google Play products stay exactly as they are, and syncPurchases() brings each subscriber over. See RevenueDot vs Adapty and RevenueDot vs Qonversion.
• Stripe: your backend posts each Stripe subscription ID to RevenueDot with the Stripe app's key, and new web sales can use RevenueDot's web checkout on your own Stripe account. See Stripe.
• RevenueCat: you do not need these steps. Keep your SDK and change one line; see Migrate from RevenueCat.

• You change code. Moving from your own code means replacing your purchase calls with the SDK's. Most apps touch the paywall screen, the purchase call and the access check.
• RevenueDot launched in 2026. A real App Store sandbox purchase has run end to end on an iPhone. Google Play handling is tested against a copy of Google's API, so run a Play sandbox purchase before you ship.
• Subscribers who never open the update are recorded from store notifications only when track_new_purchases is on. Without it, they come over the next time they open the app.