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 결제 시스템은 이 두 가지 구매 유형을 위한 실시간 개발자 알림(RTDN)을 전송하므로 백엔드는 이러한 메시지를 가져오고 필요한 변경사항을 적용할 수 있어야 합니다. RTDN 클라이언트와 Google Play Developer API를 사용하여 구매 수명 주기를 관리하는 방법을 알아보려면 구매 수명 주기 가이드를 참고하세요.
사기 및 악용 방지
민감한 로직을 백엔드로 이동하고 무효화된 Google Play 구매를 모니터링하여 악용을 방지하세요. Google Play Developer API는 새로운 구매를 확인하고, 인앱 상품 구매를 소비하고, 무효화된 구매를 처리하는 함수를 제공합니다. 사기 및 악용 방지에 관한 자세한 내용은 사기 및 악용 사례 방지를 참고하세요.
이 페이지에 나와 있는 콘텐츠와 코드 샘플에는 콘텐츠 라이선스에서 설명하는 라이선스가 적용됩니다. 자바 및 OpenJDK는 Oracle 및 Oracle 계열사의 상표 또는 등록 상표입니다.
최종 업데이트: 2025-07-27(UTC)
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["필요한 정보가 없음","missingTheInformationINeed","thumb-down"],["너무 복잡함/단계 수가 너무 많음","tooComplicatedTooManySteps","thumb-down"],["오래됨","outOfDate","thumb-down"],["번역 문제","translationIssue","thumb-down"],["샘플/코드 문제","samplesCodeIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-07-27(UTC)"],[],[],null,["# Integrate Google Play with your server backend\n\nYour secure server backend plays a key role in your app's management of in-app\npurchases through Google Play. Google Play's billing system provides a way to\nmanage the most important aspects of your digital product business, from setting\nup the catalog to tracking your transactions.\n**Figure 1.** Diagram of a typical backend integration with Google Play's billing system.\n\nThe [Google Play Developer API](https://developers.google.com/android-publisher)\nincludes several endpoints to keep your backend in sync with the Google Play\nbackend. In particular, the [Subscriptions and in-app purchases\nAPI](https://developers.google.com/android-publisher#subscriptions) handles\nfunctionality related to your digital product sales on Google Play.\n**Figure 2.** Billing-related endpoints provided by the Google Play Developer API.\n\nAutomated digital product catalog management\n--------------------------------------------\n\nThere are many use cases where it's potentially useful to have a digital product\ncatalog management integration in your backend. For example, this integration\ncould enable you to do the following:\n\n- Keep a mirror of your products' details on your backend for access when granting entitlements.\n- Set up a batch process to update all of your prices automatically.\n- Connect your own catalog management system with the catalog in Google Play's billing system to make sure it's updated synchronously.\n\nYou can use the\n[`monetization.subscriptions`](https://developers.google.com/android-publisher/api-ref/rest/v3/monetization.subscriptions)\nand\n[`inappproducts`](https://developers.google.com/android-publisher/api-ref/rest/v3/inappproducts)\nendpoints to manage your digital product catalog.\n\nPurchase lifecycle management and entitlement sync\n--------------------------------------------------\n\nMonitoring purchase lifecycle events is essential for quick, accurate response\nto changes in your users' entitlements. You should build purchase status\nmanagement into your backend for both subscriptions and one-time purchases so\nthat all of your purchases are secure and all of your entitlements are\nconsistent.\n\nGoogle Play's billing system sends [Real-time developer\nnotifications](/google/play/billing/rtdn-reference) (RTDN) for both types of\npurchase, and your backend should be ready to import these messages and make the\nnecessary changes. To learn how to leverage an RTDN client and the\nGoogle Play Developer API to manage your purchase lifecycle, see the\n[purchase lifecycle guide](/google/play/billing/lifecycle).\n\nFraud and abuse prevention\n--------------------------\n\nPrevent abuse by moving sensitive logic to your backend and monitoring voided\npurchases on Google Play. The Google Play Developer API offers functions\nto acknowledge new purchases, consume in-app product purchases, and handle\nvoided purchases. To learn more about preventing fraud and abuse, see [Fight\nfraud and abuse](/google/play/billing/security).\n\nAutomated financial conciliation and reporting\n----------------------------------------------\n\nYou can import your reporting data from Google Play by downloading your [Play\nConsole\nreports](https://support.google.com/googleplay/android-developer/answer/6135870).\nYou can leverage [Google Cloud Storage APIs](https://cloud.google.com/storage/)\nto download the information available to you on the Play Console to address any\nuse cases related to this information.\n\nExternal transaction management\n-------------------------------\n\nIf you are integrating with the\n[alternative billing](/google/play/billing/alternative) or\n[external offers](/google/play/billing/external) APIs, use\nthe [`Externaltransactions APIs`](/google/play/billing/outside-gpb-backend)\nto report and manage completed transactions."]]
