RevenueCat / RevenueCat/react-native-purchases
Accessing raw receipt data
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 117
- Avg merge
- 14h 40m
- Merged PRs (30d)
- 40
Description
It would be quite nice a re-assuring to have access to raw receipt data after making a purchase.
Perfectly reasonable place to find it:
const data = await Purchases.purchasePackage(item);
Having this data exposed via webhooks would also be nice.
I can only imagine the reason of not giving it away is making it harder to migrate. Vendor lock-in is understandable from the business side of things, but receipts is too important piece of the too important part of the software to leave it like that.
Am I missing something? Could not find anything in docs.
Part of the "feeling bad"
feeling is that how close yet unreachable the receipt data is. The internals use it extensively, just do not exposing it.
Wish you nice profits, it's in my interest also, but gimme my receipts, thanks :)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the purchasePackage API shown in the issue and the existing webhook documentation or behavior. Determine how raw receipt data could be exposed in the purchase result and through webhooks, then verify that both requested access paths are documented and covered by the project’s existing checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react-native, typescript
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100