Introduction
Stay organized with collections
Save and categorize content based on your preferences.
Google Standard Payments provides a set of APIs for companies that provide payment services to enable their services in the Google ecosystem.
While each integration has its own APIs and customer flows, the overall process is standard. Here is an overview of the process.
- The payment integrator implements the payment specification (APIs).
- Google reviews the integration by running through an API specific testing checklist in a sandbox environment. In Google's sandbox environment, no real world money is moved.
- The Integrator runs through an API specific production testing checklist using allowlisted accounts provided by Google. Google will then verify payments between the integrator and Google.
- Google will test the integration across various devices and connection types to gather feedback. Google will then certify that the integration meets required standards for UX, error handling, and latency.
- Google launches the integration in phases, ramping up in stages of 1%, 5%, 20%, and finally 100%.
Getting started
1. Become familiar with applicable flows
When one of your customers chooses your service, they will go through certain flows. Become familiar with the flows that apply to your integration under the Concepts tab. Notice how your servers interact with Google throughout this process.
2. Identify your integration points
Implementing the APIs may involve modifications to your servers, Android apps, or web frontend . Read the information under Concepts, which will describe ways your servers will interact with Google. Decide which servers you will use in order to apply the Payment Integrator APIs.
Make sure your servers support the communication requirements listed in Communication Protocol Details, and your PGP keys support the best practices listed in PGP Encryption.
3. Implement all of the Payment integrator APIs
Implement the necessary Google Standard Payment APIs that enable your use case. Use the guides to help you with this.
In the end, your APIs should be accessible by Google’s servers. Also, make sure you've implemented clients to support calling the Google APIs.
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2024-09-03 UTC.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-09-03 UTC."],[[["\u003cp\u003eGoogle Standard Payments offers APIs for payment service providers to integrate with the Google ecosystem.\u003c/p\u003e\n"],["\u003cp\u003eThe integration process involves implementing APIs, rigorous testing in sandbox and production environments, and a phased launch.\u003c/p\u003e\n"],["\u003cp\u003ePayment providers need to understand relevant customer flows, identify integration points within their systems, and implement all necessary Google Standard Payment APIs.\u003c/p\u003e\n"],["\u003cp\u003eGoogle ensures the integration meets quality standards for user experience, error handling, and latency before launching.\u003c/p\u003e\n"]]],["Payment integrators must implement Google Standard Payment APIs. Google then reviews the integration in a sandbox environment using a testing checklist. Production testing follows with allowlisted accounts, and Google verifies payments. Google tests across devices and certifies UX, error handling, and latency. Launch occurs in phases (1%, 5%, 20%, 100%). Integrators must also familiarize themselves with customer flows, identify integration points, and ensure server compatibility and PGP encryption. All necessary APIs need implementation, accessible by Google's servers, with supporting client implementations.\n"],null,["Google Standard Payments provides a set of APIs for companies that provide payment services to enable their services in the Google ecosystem.\n\nWhile each integration has its own APIs and customer flows, the overall process is standard. Here is an overview of the process.\n\n1. The payment integrator implements the payment specification (APIs).\n2. Google reviews the integration by running through an API specific testing checklist in a sandbox environment. In Google's sandbox environment, no real world money is moved.\n3. The Integrator runs through an API specific production testing checklist using allowlisted accounts provided by Google. Google will then verify payments between the integrator and Google.\n4. Google will test the integration across various devices and connection types to gather feedback. Google will then certify that the integration meets required standards for UX, error handling, and latency.\n5. Google launches the integration in phases, ramping up in stages of 1%, 5%, 20%, and finally 100%.\n\nGetting started\n\n1. Become familiar with applicable flows\n\nWhen one of your customers chooses your service, they will go through certain flows. Become familiar with the flows that apply to your integration under the Concepts tab. Notice how your servers interact with Google throughout this process.\n\n2. Identify your integration points\n\nImplementing the APIs may involve modifications to your servers, Android apps, or web frontend . Read the information under Concepts, which will describe ways your servers will interact with Google. Decide which servers you will use in order to apply the Payment Integrator APIs.\n\nMake sure your servers support the communication requirements listed in [Communication Protocol Details](/guides/connectivity/overview), and your PGP keys support the best practices listed in [PGP Encryption](/guides/connectivity/security/application-layer#pgp_encryption).\n\n3. Implement all of the Payment integrator APIs\n\nImplement the necessary Google Standard Payment APIs that enable your use case. Use the [guides](/guides/overview) to help you with this.\n\nIn the end, your APIs should be accessible by Google's servers. Also, make sure you've implemented clients to support calling the Google APIs."]]