Transfer back handling via API

Hi ​@Syit,

At this time, entitlements can’t be transferred via an API endpoint, but we do have a way to manually transfer entitlements from user to user in the dashboard. This option can be found on the customer history page - documentation walking through the steps can be found here: https://www.revenuecat.com/docs/dashboard-and-metrics/customer-history/active-entitlements#transferring-entitlements

Hi ​@kaitlin ,

I am aware with the transfer option you shared. But my app users facing unnecessary transfers among different app users as in my app user can do log out and another user can do login. To resolve this, I was thinking about to get back transfer to original user and wanted any API through which I can do it.

I have came across this conversation where you were talking about using same fetch token with different user app id, to transfer to that user can you please look into that post and check if there is a way to do so. I am attaching link to that conversation along with that API docs.

https://community.revenuecat.com/sdks-51/api-how-to-transfer-or-remove-a-purchase-3232 

API doc:

https://www.revenuecat.com/docs/api-v1#tag/transactions/operation/receipts

Hi ​@Syit,

Yes, if you have the fetch token, you could post it with another app user id to force a transfer. This isn’t in the documentation as it’s a bit of a hacky workaround. I wouldn’t recommend doing it often or making it a part of your flow.

If you’re seeing a lot of transfers between user ids, is it possible that they are on the same device? If that’s the case, even after a forced transfer, the purchase would likely transfer back as soon as the second user logged in again. There isn’t a good way to allow multiple user ids attached to one store id.