Unexpected Refund Approvals – Can RevenueCat Team Please Verify

Hi ​@yan-cheng-cheok-107847,

You are correct, we noticed it with many other apps as well that has the “Always decline” set and it looks like it’s an intended change from Apple. We’ve shared everything we know here. 

Best,

Hi ​@joan-cardona 

Would it be possible for RevenueCat to provide a dedicated page showing the detailed response data sent to Apple when handling a CONSUMPTION_REQUEST?

This would help us inspect and verify the outgoing response RevenueCat sends to Apple during the CONSUMPTION_REQUEST process.

Thank you!

Hi ​@yan-cheng-cheok-107847,

We have this detailed post on how it’s done and how to do it without RevenueCat with links to Apple’s documentation. 

Does that help?

Best,

Hi, thanks for pointing that out. I’m aware of this, but we prefer not to implement our own solution, as we want to avoid spending time and resources on it.

That's exactly why we’re using RevenueCat - we want RevenueCat to handle this for us so we don’t have to deal with the underlying details.

Hi ​@yan-cheng-cheok-107847,

Sorry I misunderstood your question. If I understand it correctly, you’d like an event tab for the `CONSUMPTION_REQUEST` sent to Apple, correct? Kind of what we show when you have integrations configured or webhooks, where we show the data sent. 

If that’s correct, I’ll share it with the team and see if that’s something we can do and prioritize it.

Best,

1. Correct. We would like to know what data is sent to Apple, when RevenueCat receiving CONSUMPTION_REQUEST

2. We would like to provide accurate playTime information from our app. Currently, RevenueCat is sending playTime with a value of 0, as referenced here: https://www.revenuecat.com/docs/platform-resources/apple-platform-resources/handling-refund-requests

   However, we do have actual usage data for each user. If there is a way for us to supply this playTime value directly, it could further assist Apple in fairly evaluating and potentially rejecting refund requests based on real user engagement.