blocks|key|2258437|text|您将需要在应用程序采购中实现，就像在应用程序项目中的任何其他应用程序一样。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2258438|确保在Dev控制台中创建项目时，它是非托管的，因为每个帐户只能购买一次托管项目。|2258439|当您在购买非托管项目时收到确认消息时，请将诸如唯一ID之类的详细信息发送到服务器并将其存储在那里。|2258440|现在，每当您的应用程序启动，检查您的服务器，如果它是一个授权的设备。如果不是，则提示用户购买它。如果是的话，让他们继续使用这个应用程序。|2258441|这只在你需要一次性付款的情况下才有效。如果您需要订阅，您将不得不弥补多次一次性付款，因为订阅就像有管理的购买，只能通过任何帐户支付一次。|2258442|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|M|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|N|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|O|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|P|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|K|$]]

You will need to implement in app purchases as you would for any other in app item.

Make sure when you create your item in the Dev Console, it is unmanaged, as managed items can only be purchased once per account.

When you receive a confirmation on purchase of your unmanaged item, send the details like the unique ID to your server and store them there.

Now whenever your app starts, check with your server if it is an authorized device. If it isn't, prompt the user to buy it. If it is, let them continue to the app.

This only works if you need a one time payment. If you need a subscription, you will have to make it up of multiple one time payments, as subscriptions are like managed purchases and can only be paid for once by any account.

blocks|key|2462094|text|Google最初提供的文档似乎使这一目标无法实现，但深入挖掘后，我发现了以下内容.|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2462095|在Google+2.0版本中，您可以创建所谓的“非托管”产品类型，允许用户多次购买相同的东西。虽然Gooogle开发人员控制台显然支持这一点，但这在API+3.0中似乎已经部分消失了。我认为它仍然被支持，因为使用2.0API的应用程序仍然存在，而Google就是不能放弃对它的支持。|2462096|然而，在3.0中，API文档中没有列出“非托管”产品类型，但是docs说明了关于为同一产品类型(一次性购买或订阅)进行多次购买的情况：|2462097|如果使用的是版本3+API，也可以在应用程序中使用托管项。您通常会实现对可多次购买的物品的消费(例如游戏中的货币、燃料或魔法咒语)。一旦购买，通过向Google发送消费请求，在您使用该项目之前，无法再次购买托管项目。若要了解有关应用程序内产品消费的更多信息，请参见消费项目。
|blockquote|2462098|2462099|http://developer.android.com/google/play/billing/api.html#consume|offset|length|2462100|的重要性:订阅不能使用，这意味着如果您希望客户定期更新他们的许可证，您将不得不与他们联系并告诉他们必须再次购买许可证。如果您的服务需要定期更新，这是一个缺点。|style|BOLD|2462101|为了获得你想要的东西，你需要一个后端服务器来处理设备的注册，并在购买时存储从Google收到的令牌。当用户想从另一个设备购买您的许可证、功能、服务(或其他任何东西)时，另一个设备必须首先通过一个名为“消费”的过程，与Google一起释放其对该产品的“所有权”。它或多或少会像这样工作：|2462102|第一个设备进行购买，并从Google接收一个purchaseToken字符串。|ordered-list-item|2462103|purchaseToken和设备ID将从应用程序发送到服务器并存储。|2462104|用户转到第二个设备，并希望购买该设备的许可证。该应用程序首先需要进入您的服务器，并获得purchaseToken+(第一个设备上传的)，然后调用Google与consumePurchase，这将从用户那里释放产品的“所有权”。|2462105|然后，该应用程序从Google购买新的许可证(或其他任何东西)，获得一个新的purchaseToken，并将其与设备ID一起存储在服务器上。|2462106|2462107|2462108|从本质上讲，Google不会跟踪哪个设备拥有该产品。它只将Google帐户与正在购买的产品关联起来。这取决于您的应用程序和服务器来管理许可证。|2462109|有一个潜在的问题，我认为你需要解决。如果应用程序由于某些原因未能将purchaseToken发送回您的服务器(您的服务器关闭了，用户丢弃了他们的设备并将其损坏，您的应用程序在将令牌保存在设备上之前就崩溃了，等等)，那么您可能不知道用户是否支付了该服务的费用。Google确实提供了一个服务器API，可以让您的后端服务器查询Google在Google服务器上播放有关购买的信息，但我不熟悉它，也不了解它的局限性。|2462110|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|1T|0|0|0|27|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1G|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1H|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1I|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|1K|8|@]|9|@$L|1L|M|1M|1|1N]]|A|$]]|$1|N|3|O|5|6|7|1O|8|@$L|1P|M|1Q|P|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|1R|8|@]|9|@]|A|$]]|$1|T|3|U|5|V|7|1S|8|@]|9|@]|A|$]]|$1|W|3|X|5|V|7|1T|8|@]|9|@]|A|$]]|$1|Y|3|Z|5|V|7|1U|8|@]|9|@]|A|$]]|$1|10|3|11|5|V|7|1V|8|@]|9|@]|A|$]]|$1|12|3|-4|5|6|7|1W|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|14|3|15|5|6|7|1Y|8|@]|9|@]|A|$]]|$1|16|3|17|5|6|7|1Z|8|@]|9|@]|A|$]]|$1|18|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|19|$1A|$5|1B|1C|1D|A|$1E|K]]]]

The documentation from Google initially seems to make this impossible to achieve but digging deeper, I uncovered the following...

In the Google Play API version 2.0, you could create what was called an "unmanaged" product type that allowed the user to purchase the same thing multiple times. That seems to have partly disappeared in API 3.0 although the Gooogle Developer Console clearly supports this. I assume it's still supported because apps that used the 2.0 API are still out there and Google just can't drop support for that.

In 3.0 however, the "unmanaged" product type is not listed in the API docs but the docs state the following about making multiple purchases for the same product type (one-time purchase or subscription):

<blockquote>
 If you are using the Version 3 API, you can also consume managed items
 within your application. You would typically implement consumption for
 items that can be purchased multiple times (such as in-game currency,
 fuel, or magic spells). Once purchased, a managed item cannot be
 purchased again until you consume the item, by sending a consumption
 request to Google Play. To learn more about in-app product consumption,
 see Consuming Items
</blockquote>

<a href="http://developer.android.com/google/play/billing/api.html#consume" rel="noreferrer">http://developer.android.com/google/play/billing/api.html#consume</a>

IMPORTANT: Subscriptions CANNOT be consumed which means that if you want the customer to periodically renew their license, you will have to contact them and tell them that they must purchase the license again. That's a downside if your service requires a periodic renewal.

To obtain what you are after, you will need a backend server to handle the registration of devices and store tokens the apps receive from Google Play when purchasing. When a user wants to purchase your license, feature, service (or whatever) from another device, the other device MUST first release its "ownership" of the product with Google Play, through a process known as "consuming". It would work something more or less like this:

<ol>
<li>The first device makes a purchase and receives a purchaseToken
string from Google Play.</li>
<li>The purchaseToken along with the device ID is sent from the app to your server and stored.</li>
<li>The user goes to the second device and wants to purchase the license as well for that device. The app first needs to go to your server and obtain the purchaseToken (that the first device uploaded) and then call Google Play with consumePurchase which releases the "ownership" of the product from the user.</li>
<li>The app then purchases the new license (or whatever) from Google Play, gets a new purchaseToken and stores it on your server along with its device ID.</li>
</ol>

In essence, Google Play won't keep track of which device has the product. It only associates the Google Account with the product being purchased. It's up to your app and server to manage the licenses.

There is one potential problem I see that you need to address. If for some reason the app fails to send the purchaseToken back to your server (your server is down, the user dropped their device and broke it, your app crashes before it saves the token on the device, etc.), then you may not know if the user paid for the service. Google does provide a server API that lets your backend server query Google Play on Google's server for information about purchases, but I'm not familiar with it nor its limitations.

I would like to setup subscription based billing for an app that will be sold through Google Play. Is it possible to sell the same subscription to the same user but on a different devices? So that every device that user tries to use the app on would need an active subscription?

I was thinking I could store the device id and user id on my own server and authenticate it that way, but is it correct that a user can't purchase the same subscription more than once? So would I need a pool of basically the same subscriptions if the user wishes to purchase multiple "licenses"? Can Google Play Billing handle any of this natively?

Thanks

Per Device subscriptions for purchases through Google Play

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我想建立订阅为基础的计费应用程序，将出售通过谷歌发挥。是否有可能将相同的订阅出售给同一用户，但在不同的设备上出售？这样，每个用户尝试使用应用程序的设备都需要主动订阅吗？我想我可以将设备id和用户id存储在自己的服务器上，并以这种方式对其进行身份验证，但是用户不能购买相同的订阅一次以上是正确的吗？因此，如果用户希望购买多...

问通过Google购买设备的每个订阅
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问通过Google购买设备的每个订阅EN