Build a customized mobile subscription business with RevenueCat. We do the heavy lifting of normalizing subscribers from any source and maintain a single source of truth for subscription status, so you can get back to building your app.
RevenueCat is a powerful, secure, reliable, and free to use in-app purchase server with global support. All you need to get started is an API key.
Hi, I'm currently evaluating revenue cat for subscription handling. Our security policies require sensitive user data not being stored outside of our servers (apart from Apple/Google). Hence I would like to know if you have an option for us get a licensed copy of your backend system that can be hosted on our infrastructure. Let me know if this is possible. Thanks, Venkat
Posted by Venkatesa Prasannaa Selvaraj a day ago
The scenario we want is: - Current users subscribe at a low rate - We want to raise prices (and / or remove the old plan) - But leave anyone who has already purchased on the old plan I believe Apple will not let you keep two subscription plans available unless they are both offered. So, I'm unsure if we can support this scenario (Grandfathered old plans).
Posted by christopher fullname 3 days ago
I configured a consumable purchase on iOS app store with the product ID "com.motioniq.bikemodel". In RevenueCat I created a new product, then created the legacy entitlement, then added the offering to the legacy entitlement and finally attached the product to the offering. When I call entitlements() I see the new product in the list of entitlements. When I call makePurchase() I now see the product is included in the list of active entitlements, but I also see a new list named "nonConsumablePurchases" and my product is in that list. Here is the log output: nonConsumablePurchases: {( "com.motioniq.bikemodel" )}, Not what I expected but maybe I can ignore that? Later when I make the 2nd and 3rd purchase of this consumable product there is no change to the data returned by makePurchase() other than "latestPurchaseDate" is updated. Should I be looking at the date change to confirm the purchase was successful? Or can I assume the transaction was good as long as makePurchase() does not return an error. Is there a better way to configure consumables with v2?
Posted by Michael Chartier 9 days ago
Hello, I've been in touch with one of the developers working on the Unity SDK for RevenueCat on GitHub, but I also wanted to followup directly here in the official discussion forum as well. I'm on a tight deadline to finish an app that will be released for iOS, Android, Windows, and MacOS, and need to make it possible for users to use their IAP subscription across any platform. It appears that at this time, the Unity SDK does not support standalone MacOS or standalone Windows apps at this time. I am hoping that support might be coming soon for MacOS and Windows apps in the Unity SDK? Given that RevenueCat itself does support MacOS and Windows, it doesn't seem like it would be too much of a reach to have those platforms supported in the Unity SDK as well? Thank you, Peter
Posted by Peter Shannon 11 days ago
I'm on iOS and called: `Purchases.shared.offerings` For just one user, this is returning no error but also no current offerings. Here's my code: ``` Purchases.shared.offerings { offerings, error in if let error = error { Log.error(error) completion(.failure(error)) } else { guard let offerings = offerings, let current = offerings.current else { // This point is reached!!! return } ``` What case would cause this point to be reached? Everyone else is able to get the current offerings. Just one user so far has hit this point. Any ideas?
Posted by Peter Livesey 12 days ago
New to RevenueCat... Don't see any mention of two issues that come immediately to mind with cross-platform subscriptions: - Are there no passwords associated with user data? If someone is able to guess or knows someone's user ID, they can just type that in and get access to the subscription? Is there any way to have users use passwords with RevenueCat? - If this is the case, then as the Documentation suggests, obviously User IDs should not be guessable. However, this really isn't desirable from a user perspective, as their username would have to be something auto-generated like a string of letters and numbers. I was planning on letting users choose their user name, and then checking if it's already been taken in the database. It seems like in RevenueCat, I'd instead just be assigning them a random username?
Posted by Peter Shannon 14 days ago
Hi, we just started testing an integration with RevenueCat before we decide to use it as our framework for iAP... I'm a bit confused about the Offering layer, although I understand the purpose. In your example you assume there is only a Pro version of an App which can be purchased either via a monthly or yearly (with discount) subscription fee... This would most probably be an app with only one Entitlement (i.e. Pro) In our case though, we have the following setup: - 3 x Products: Autorenewable Subscription (Bronze, Silver, Gold) on Monthly basis - 3 x Entitlements: Bronze, Silver, Gold Since we only want to offer monthly subscriptions, how would we go about creating Offerings since we cannot add multiple packages with the Monthly Identifier to an Offering? Thanks for your help Vince
Posted by Vince Weil 14 days ago
Hi everyone, I am Beta testing my app which has auto-renewing subscriptions and everything is working great. The only problem I am having is that after 6 payments (the subscription is £2.99 per month) the customer history log is saying "Opted out of renewal". The thing is I am testing it on my phone and know for sure I didn't opt-out. Is this just how it works whilst beta testing with RevenueCat and once the app is published on the App Store it will just auto-renew until the user cancels? Thanks for your help!
Posted by James 16 days ago
Hi, I'm looking for a way to be able to quickly identify a user with a purchase in the RC dashboard. We have a UUID that's used for the App User ID but i'd like to attach a username so i can quickly identify the actual user who paid. Should I use Alias for this? Should I not do this for some reason? Please help.
Posted by Desmond 16 days ago
Does RevenueCat support Ionic React (v4) with Capacitor? I see there is a Cordova plugin, but this cannot be used on Ionic React projects ("Error: Cordova is not supported for react projects"). We would need a Capacitor plugin instead (https://capacitor.ionicframework.com/docs/plugins/). Any plans to release this?
Posted by Marco 25 days ago
Hi, We are using revenuecat in one of our iOS application and we provide. Monthly - yearly - Lifetime subscription for users. However lifetime is a part of non-consumeble. So when we start app we are getting response like following. <PurchaserInfo originalApplicationVersion: 1.0, latestExpirationDate: 2019-12-23 12:15:43 +0000 activeEntitlements: { Pro = { expiresDate = null; }; }, activeSubscriptions: { "com.123.y3u33k3i.product.monthlyPlan" = { expiresDate = "2019-12-23 12:15:43 +0000"; }; }, nonConsumablePurchases: {( "com.123.y3u33k3i.product.product.lifetimeTime" )}, requestDate: 2019-12-23 12:14:22 +0000 ====== But issue is started while user cancel thier auto-renew and at that time we are getting response from revenuecat is following. <PurchaserInfo originalApplicationVersion: 1.0, latestExpirationDate: 2019-12-23 12:15:43 +0000 activeEntitlements: { Pro = { expiresDate = null; }; }, activeSubscriptions: { }, nonConsumablePurchases: {( "com.123.y3u33k3i.product.product.lifetimeTime" )}, requestDate: 2019-12-23 12:14:22 +0000 ===== So user automaticully get lifetime purchase so how can we deal with that issue?
Posted by Nitin Gohel 26 days ago
I'd like to transition customers who paid for my app to a subscription model. My current thinking is to check the originalApplicationVersion and compare it to the current paid App Store version of the app, and then provide them with a free year trial before converting to monthly / yearly plans. When I only called purchaserInfo the originalApplicationVersion is nil, but it shows 1.0 after I call restoreTransactions. Is this expected? I'm trying to figure out how our upsell screen should appear, will I need a message to let every customer know to use `restoreTransactions` if they purchased the app before?
Posted by Maximilian Litteral about a month ago
We have a couple of doubts with the offerings and webhooks. 1) Are Entitlements deprecated? 2) We have one "Offering" with 2 "Packages" (monthly and annual) and 1 "Product" per platform per package. The problem is that we are expecting the "presented_offering_id" value to be present in the webhooks payload but it's coming with "null" value: { ... "event": { ... ... "presented_offering_id": null, ... ... } } Why is the "presented_offering_id" null ? Thanks!!
Posted by Martin Santini about a month ago
I have a bunch of unassigned, obsolete products that I used when first getting to know RevenueCat. They still appear in for example the Activity filter dropdown list, which makes it a bit frustrating to find the actual product you're looking for when there are 30 unused ones mixed in with the one you're looking for...
Posted by Magnus W about a month ago
I am integrating our backend with RevenueCat, but kind of in observer mode. I am more interested in using RevenueCat as analysis tool, rather than anything else. So far it looks like everything works. I'll just mention that the examples in REST-API are not working out of box due to header names being case sensitive (examples have them lower-case, but API expects them to be in Content-Type style, rather content-type) My question is, what kind of information do I have to store in my database so that nothing is lost if I want to export data to RevenueCat at some point later and see correct revenue / historical price data. My fear is that if I don't store enough data, RevenueCat will be no longer able to understand what exactly has been going on historically. right now I store the following in my database (and update): - transactionId (this is originalTransactionId on Apple, and transactionId on Android) - productId - receipt - platform (iOS/Android) the way I update these records in the table; If transactionId does not exist, I create new record If transactionId already exists, I update existing fields (this could update productId and receipt) Every time I get receipt from server-hook (iOS/play store), I just process the "latest_receipt" or "latest_expired_receipt, verify that receipt and query apple/play store, and update the table with latest information. Is that going to be enough for RevenueCat to understand the data if I decide to re-play these "transactions" against v1/receipts and generate statistics that are 99% up with real world? I've noticed some weird situations happening such as if I cancel a subscription (and get refunded), and then subscribe again, the originalTransactionId stays the same, and it also stays the same if I upgrade/downgrade my plan (but productId changes). I've also noticed that there is "linkedPurchaseToken" on Android, does this require any special attention? Theoretically speaking, correct me if I am wrong, the receipts act as authentication tokens, and if I have managed to get receipt from the user, and store it somewhere, that is going to be enough for RevenueCat to figure out everything that ever has happened to that specific user, including cancellations, refunds, plan upgrades/downgrades (and how the user has been charged for it)
Posted by Chris about a month ago