Skip to main content

I have a question about the TRANSFER event flow. I see this in the docs -

For example, if UserA buys a subscription, then UserB logs into your app on the same device and restores transactions, UserB would now have access to the subscription and it would be revoked from UserA.

Currently I’m implementing the handling of the TRANSFER event, so right now when trying to transfer our handler is returning a 500 because it’s not checking for the ids in the right place, which is fine, I can fix that. But even with the 500 response I see that UserB now has the entitlement but it has not being revoked for UserA. Is fixing this minor error so we now return 200 if the ids are valid enough to trigger UserA’s entitlement being revoked?

We have some tracking of entitlements our side that we’ll be updating since I understand that the TRANSFER event doesn’t trigger any follow up webhooks but just wanted to clarify this point.

Thanks!

Are you manually determining when a user is entitled or not? Or are you checking the entitlement on the CustomerInfo object as we describe here: https://www.revenuecat.com/docs/customers/customer-info?

If the latter, then you wouldn’t need to handle the revocation of the entitlement from User A—we do that automatically when the restore occurs.

I was checking in the ui, either way I fixed the issue and now everything is behaving as expected, seems like fixing our handler to not return a 500 fixed the behaviour.

Reply


Terms & ConditionsCookie settings