In our model, a user registers to our service with a google account and can 
have in-app subscriptions through that account. 
We want to be able to support a request from the user to change the 
registered google account. 
We can easily update any in-app subscriptions the user has in our back-end 
server, but the problem is, on Google's side of things, the old account's 
subscription remains valid (and possibly auto-renewable), and the new 
account doesn't have a valid subscription of any kind.

Is there any standard way to deal with this scenario? (Other then telling 
the user to manually unsubscribe, change their details and their 
subscription details in our db, tell the user to subscribe again with the 
new user and probably refund some part of his payment)?

Thanks,
Vlad

-- 
You received this message because you are subscribed to the Google Groups 
"Android Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/android-developers.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/android-developers/e32cb8b6-9023-411e-8b15-6e80ad3d9c63%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to