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.
- Cost in Using pub/sub notifications : Pricing for Google Cloud Pub/Sub
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.