Technical Requirements
Partner Google Cloud Project (GCP) Setup
Partners must set up a GCP project to enable and use the Payments Reseller Subscription API to
- Create a GCP project one each for Sandbox and production with a non-gmail, Google Account
- Create OAuth2.0 credentials
- Enable Payments Reseller Subscription API
OAuth 2.0 app verification
Partners must get approval on the usage of the OAuth2.0 API prior to starting the e2e testing. As part of the verification, the domain associated with the integration must also be verified (Verify your Site Ownership). FAQs about the app verification can be found at OAuth 2.0 API verification FAQs.
QPS
Partners must limit the QPS (Queries Per Second) to 10 QPS across all Payments APIs.
Subscribing to Cloud Pub/Sub Notifications
Each partner will be assigned with a unique Cloud Pubsub Topic IDs, where notifications are published for subscriptions and/or purchase orders. Partners must subscribe to their topics to receive notifications for subscription and purchase order state changes.
Handling Access/Refresh Tokens
- Partners must store OAuth2.0 refresh tokens for each user to handle upgrade/downgrade to the subscription.
- When refresh tokens become invalid, partners should trigger a new OAuth2.0 flow to obtain new tokens.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-08-06 UTC.
[null,null,["Last updated 2024-08-06 UTC."],[[["Partners must establish a Google Cloud Project (GCP) and enable the Payments Reseller Subscription API to manage subscriptions."],["OAuth 2.0 app verification is required, involving domain verification and adherence to QPS limits for API usage."],["Partners need to subscribe to designated Cloud Pub/Sub topics to receive real-time notifications on subscription and purchase order status changes."],["Secure storage and management of OAuth2.0 refresh tokens are crucial for handling subscription modifications and token renewals."]]],["Partners need to create separate Google Cloud Platform (GCP) projects for sandbox and production, using non-Gmail accounts. They must then create OAuth 2.0 credentials and enable the Payments Reseller Subscription API. OAuth 2.0 app verification, including domain verification, is required before testing. Partners should limit API calls to 10 Queries Per Second (QPS). They must also subscribe to designated Cloud Pub/Sub topics to receive subscription and purchase order notifications and store refresh tokens, triggering a new OAuth flow when they are invalid.\n"]]