You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
constdata=awaitPurchases.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 :)
The text was updated successfully, but these errors were encountered:
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:
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 :)
The text was updated successfully, but these errors were encountered: