Loading video...
Video Failed to Load
(Re)Introducing Refund Control! Some background; on iOS, Apple approves every refund request unless you respond to the notification they send. RevenueCat responds for you, and for a long time one of the options was "always decline". We removed it. Declining every request regardless of the reason pushes users into... show more
16,203 views • 1 month ago •via X (Twitter)
14 Comments

@elwatto Amazing! I wanted to implement exactly this on our backend and set the preference in RC, much easier this way!

Can you preview which policy a past refund would match before enabling it? With ordered rules, a broad audience could quietly catch requests meant for a more specific one.

Launching a 7-day trial next month, and the policy I actually want is: approve if they never opened the app after the trial converted, decline if they've been using it daily. Can an Audience see in-app usage, or only purchase history?

can a policy look at how long they've been subscribed or only activity?

Policy-powered refunds are a better fit than a universal decline toggle. The interesting metric is whether chargebacks drop without increasing support load.

🙌

Decline every refund and you train people to charge back. I would approve anyone who never finished the core job, and only fight refunds after a completed session.

これは素晴らしい取り組みですね!返金管理の方法が変わると、業界全体に良い影響を与えそう。

Refund flows need plain language because frustration arrives before anyone reads the policy. Clarity is a feature when money is involved.

the ‘active for weeks’ example feels tricky. someone might keep opening an app because it's broken, not because they got value from it. can support history factor into a refund policy?

great feature!

なるほど、Appleの通知に対応しないとダメなんですね。わかりやすくて助かります!

Great feature!

refunds are the quiet ios tax: apple takes 30% up front and gives devs no say over the refund, so you eat the loss twice. good to finally see tooling.
