Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 9250441
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 18, 20262026-06-18T10:26:46+00:00 2026-06-18T10:26:46+00:00

How do I implement (Auto-renewable) Subscriptions for an Android App. I’ve read the documentation

  • 0

How do I implement (Auto-renewable) Subscriptions for an Android App.

I’ve read the documentation

and as far as I understand, the process is the following:

  • User subscribes to such a subscriptions on the app. This will generate a Purchase token.
  • The app sends this token to the server along with something to identify this user
  • The server will store this Purchase token with this user and will mark the subscription as valid
  • the server validates this Purchase token via the http-api periodically (typically once per day) with something like a cronjob
  • if the subscription isn’t valid anymore, the subscription will be marked as invalid on the server-side.
  • If the app makes requests to the server to resources that need the subscription, the client will send this user-identity-string along with the requests. We then check in the database, if the subscription of this user is still marked as valid.

My question is now, how we should identify this users? Do we have a simple user id available that we can share between our app and our server? or should we use something different? What is the best practice here?

We did already similar subscriptions on ios and we used the uuid of the device to identify the users (at least as long as we were able to use the uuid).


From the Answer below we should generate a unique ID. This would be unique per device (or per app-installation). But if a user changes his device or reinstalls the application this id would not be the same anymore. So I’m not sure, how the process is in this use case. I thought of something like this:

  • The user is logged in with the same google play account on his second device.
  • As the app starts (or becomes active) we would fetch the users subscriptions
  • We then would receive this purchase token from the subscriptions and send them along with the new unique-ID to our backend-server as if the user had made a new subscription.

Would this be the right process? And stays the purchase token the same as it was on the first device?


Ok, my question about identifiying users is answered, the link provided delivers enough informations. I’ll put further questions in new threads on SO, if I have some.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-18T10:26:48+00:00Added an answer on June 18, 2026 at 10:26 am

    This link maybe helpful to you as you want to identify the users uniquely.Please note that the personal information of a user rests with Google only.And you should avoid getting private information of a user.
    http://www.pocketmagic.net/2011/02/android-unique-device-id/#.URIe_B3Wgr7

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I'm looking to implement the new Auto Renewable subscriptions using In App purchase but
i receive the following error when trying to implement auto-complete based on edismax type.
In order to implement auto-vivification of Ruby hash, one can employ the following class
The app I'm working on was recently rejected by Apple for containing an auto-renewable
I have implemented a couple of months ago the in app auto renewable subscription
Is there any means to implement the auto-complete word hint in Android, with the
Is there some way to implement an auto-upgrade for an iPad app. I would
Is there a minimum version of iOS that is needed to support auto-renewable subscriptions?
I have implemented Auto renewable subscription for In-App purchase. At time of login I
I want to implement auto suggest functionality in Google App Engine (GAE/GWT). The client

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.