Skip to main content
Solved

Best practices for handling non-subscription transactions and refunds

  • November 22, 2021
  • 1 reply
  • 403 views

Forum|alt.badge.img+3

I have one consumable product in my iOS app that doesn’t link to any entitlements as recommended in the docs:

If you have non-subscription products, you may or may not want to add them to entitlements depending on your use case. If the product is non-consumable (e.g. lifetime access to "pro" features), you likely want to attach it to an entitlement. However, if it is consumable (e.g. purchase more lives in a game) you likely do not want to add them to an entitlement.

Right now I’m using the transaction history to keep track of the purchases and unlock in-app content accordingly. Not sure what’s the best approach for this to correctly handle refunds. 

Best answer by jazmine

Hi @Anh

 

There are webhook events for refunds which include non-subscription IAP (note for Google you need to grant the refund through RevenueCat to be detected). When you receive this webhook event you can handle access on your end. 

View original
Did this post help you find an answer to your question?

1 reply

jazmine
Forum|alt.badge.img+7
  • Dedicated Contributor
  • 122 replies
  • Answer
  • December 10, 2021

Hi @Anh

 

There are webhook events for refunds which include non-subscription IAP (note for Google you need to grant the refund through RevenueCat to be detected). When you receive this webhook event you can handle access on your end. 


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings