Reminder: By Aug 31, 2025, all new apps and updates to existing apps must use Billing Library version 7 or newer. If you need more time to update your app, you can request an extension until Nov 1, 2025. Learn about Play Billing Library version deprecation.
Google Play の課金システムは、Android アプリでデジタル商品とデジタル コンテンツを販売するためのサービスです。1 回だけの購入で収益を上げることも、サービスを定期購入できるようにすることも可能です。Google Play では、Android アプリとサーバー バックエンドの両方と統合するための API 一式を用意しており、ユーザーは安全性が高く使い慣れた Google Play で購入できます。
統合アーキテクチャ
このセクションでは、構築できるさまざまな機能モジュールと、プロセスの合理化に使用できる API とライブラリを紹介します。
図 1. 一般的な Google Play 請求サービスの統合を表した図
Play Billing Library を使用して、Google Play の課金システムと Android アプリを統合できます。このライブラリにより、アプリ内の各ユーザーが利用できるローカライズされた商品を提供する Google Play 開発者サービスレイヤと、購入フローの開始やその結果の処理といった、その他の必要なユーザー操作を処理するメソッドとの通信が可能になります。
Google Play の課金システムをサーバー バックエンドと統合して、必要なデベロッパー フローも作成する必要があります。購入管理とクロス プラットフォームでの利用資格の効率性と安全性を確保するうえで、これは重要です。この統合は Google Play Developer API の Subscriptions and In-App Purchases API を使って作成できます。バックエンドの統合では、一部の Google Cloud Platform ツールも使用します。
図 2. Google Play Developer API による API とサービス
用語
このセクションでは、Google Play の課金システムをアプリに統合する際に目にする可能性がある、テクノロジーと概念について大まかに説明します。このリストを参照しながら、統合ガイダンスに沿って進めてください。
テクノロジー
Google Play: ユーザーがアプリやその他のデジタル アイテムをダウンロードできるオンライン ストアです。
Google Play Console: アプリを Google Play に公開するためのインターフェースを備えたプラットフォームです。Google Play Console には、Google Play で販売する商品やコンテンツなど、アプリの詳細も表示されます。
購入トークン: Google Play 上のアイテムに対する購入者の利用資格を示す文字列です。特定のアイテムに対して Google ユーザーが支払いを行ったことを示します。
オーダー ID: Google Play 上の支払いトランザクションを示す文字列です。オーダー ID は支払いトランザクションが発生するたびに作成されます。この文字列は、購入者にメールで送信される領収書に記載されます。オーダー ID を使って、Google Play Console の [注文管理] で払い戻しを管理できます。オーダー ID は、販売と支払いのレポートでも使用されます。
次のステップ
Google Play の課金システムをアプリおよびサーバー バックエンドと統合するには、設定ガイドをご覧ください。
[null,null,["最終更新日 2025-07-27 UTC。"],[],[],null,["# Google Play's billing system is a service that enables you to sell digital products\nand content in your Android app, whether you want to monetize through one-time\npurchases or offer subscriptions to your services. Google Play offers a full set\nof APIs for integration with both your Android app and your server backend that\nunlock the familiarity and safety of Google Play purchases for your users.\n| **Note:** Google Play's billing system is only for digital items. For physical goods and services, or other non-digital content, see the [Google Pay SDK](https://developers.google.com/pay/api/android/overview).\n\nIntegration architecture\n------------------------\n\nThis section introduces the different functional modules that you can build and\nthe APIs and libraries available to simplify the process.\n**Figure 1.** Diagram of a typical Google Play billing integration.\n\nYou can integrate Google Play's billing system with your Android app using the [Play\nBilling Library](/reference/com/android/billingclient/classes). This library\nenables communication with the Google Play Services layer that provides the\nlocalized product offering available to each user in your app, as well as\nmethods to handle other necessary user operations, like launching the purchase\nflow and handling its outcome.\n\nYou should also integrate Google Play's billing system with your server backend to\ncreate the necessary developer flows. This is essential to guarantee that your\npurchase management and cross-platform entitlements are efficient and secure.\nYou can create this integration with the [Subscriptions and in-app purchases\nAPI](https://developers.google.com/android-publisher#subscriptions) provided by\nthe Google Play Developer API. The backend integration also leverages some\nGoogle Cloud platform tools.\n**Figure 2.** APIs and services provided by the Google Play Developer API.\n\nTerminology\n-----------\n\nThis section lists and describes the high-level technologies and concepts that\nyou might encounter when integrating Google Play's billing system into your app.\nReference this list as you proceed through the integration guidance.\n\n### Technologies\n\n- [**Google Play**](https://play.google.com). An online store where users can download apps and other digital products.\n- [**Google Play Console**](https://play.google.com/console). A platform that provides an interface where you can publish your app to Google Play. The Google Play Console also shows details about your app, including any products or content that you sell with Google Play.\n- [**Google Cloud Console**](https://console.developers.google.com/). A platform that manages backend APIs, such as the Google Play Developer API.\n- [**Google Play Billing Library**](/google/play/billing/integrate). An API that you can use to integrate Google Play's billing system into your app.\n- [**Google Play Developer API**](https://developers.google.com/android-publisher/). A REST API that you can use to programmatically handle publishing and app management tasks.\n- [**Cloud Pub/Sub**](https://cloud.google.com/pubsub/). A fully managed real-time messaging service that enables you to send and receive messages between independent applications. Google Play uses Cloud Pub/Sub to deliver Real-time developer notifications. To use [Cloud\n Pub/Sub](https://cloud.google.com/pubsub/), you must have a project on the [Google Cloud Platform (GCP)](https://cloud.google.com/) with the Cloud Pub/Sub API enabled. If you aren't familiar with GCP and Cloud Pub/Sub, see the [Quickstart guide](https://cloud.google.com/pubsub/docs/quickstart-console).\n- [**Real-time developer notifications**](/google/play/billing/getting-ready#configure-rtdn). A mechanism that lets you monitor state changes for Google Play-managed subscriptions in real time by leveraging [Cloud\n Pub/Sub](https://cloud.google.com/pubsub).\n- **Secure backend server**. As part of integrating Google Play's billing system into your app, we strongly recommend that you use a secure backend server to implement billing-related tasks such as purchase verification, subscription-specific features, and handling Real-time developer notifications.\n- **Google Play Store app**. An app that manages all operations related to Google Play. All requests made by your app are handled by the Google Play Store app.\n\n### Concepts\n\n- **Flow** . A flow shows the typical steps involved in a billing-related task. For example, a *purchase flow* outlines the steps involved when a user purchases your product. A *subscription flow* might show how a subscription transitions between states.\n- **Entitlement** . When a user purchases an in-app product, they are then *entitled* to that product within your app. For one-time products, this means that the user should now have permanent access to the product. For subscriptions, this means that the user should have access while the subscription is active.\n- **Product ID**. The ID of a specific product type.\n- **Purchase token**. A string that represents a buyer's entitlement to a product on Google Play. It indicates that a Google user has paid for a specific product.\n- **Order ID** . A string that represents a financial transaction on Google Play. An order ID is created every time a financial transaction occurs. This string is included in a receipt that is emailed to the buyer. You can use the order ID to manage refunds in the **Order Management** section of the Google Play Console. Order IDs are also used in sales and payout reports.\n\nNext steps\n----------\n\nTo begin integrating Google Play's billing system with your app and server backend,\nsee the [setup guide](/google/play/billing/getting-ready)."]]
