RAW Data about my receipts

RevenueCat abstracts away a lot of the small details contained in receipts so you get a simplified view of the data in the receipts. (...) We don’t have any APIs to get the raw data of the receipts but if you need them for any one-time tasks or migrations we’d be happy to help

It is slimy of you to not provide easy access to receipts (even on client after the user just has made a purchase).

I presume the reason for not supporting this is to make it harder to migrate away from RevenueCat. But in the process of making that harder, you are making certain other things harder also (not for everyone, but e.g. for me right now).

Similar thought. Vendor locking is good for business, but we as users have to call this out.

Please, provider an easier access. It does not feel great to have this data buried away from me, it’s an important pieces of information I want to have access to.

any solution about reaching the receipt after purchase?

Hey all,

I see this post has gotten some views since our last response so we wanted to update everyone on this.

Vendor lock-in is the last thing we want to do. If you ever want or need to migrate away from RevenueCat for any reason, just let us know and we’ll export all of your receipts in a CSV file.

One of our goals here at RevenueCat is to simplify the purchase process across the App Store, Play Store, Amazon App Store, and Stripe. To do that, we provide a consistent API so that it doesn’t matter which store a customer purchases from, you’ll still get the same neat data. We take care of collecting and validating receipts with Apple’s, Google’s, Amazon’s, and Stripe’s APIs.

If you need do need the receipt, you can always use the native on-device APIs to get them. You can do this alongside RevenueCat without any issues. On iOS you would read the Bundle.main.appStoreReceiptURL property. On Google Play you would use the queryPurchaseHistoryAsync function in BillingClient. On Amazon Appstore you would use the getPurchaseUpdates() function in the com.amazon.device.iap package. And on Stripe of course you should already have the token from Stripe’s API.

Hi all,

One of our mobile engineers also wanted to point out that on-device APIs are not necessarily guaranteed to provide up to date information like server-side APIs provide which is another reason why we don’t provide APIs for native receipt fetching on the device. But you can always reach down into the native APIs like I explained above and get the tokens without any interference from RevenueCat.