Stay organized with collections
Save and categorize content based on your preferences.
Google enforces several Service Level Agreements (SLAs) to ensure a reliable and
responsive user experience. Examples of common Google Standard Payments SLAs and
how they are measured are provided here.
Example SLAs
System availability
Example terms
The Payment Integrator shall make their Systems available to
Google for 99.9% of requests over any 24 hour period (per API method).
The System shall be considered unavailable for a given request if System fails
to respond to a valid API request with a valid API response within 7 seconds as
measured by Google after a well-formed transactional packet has been sent to
the Payment Integrator.
The measurement period will be defined as one hour if more than 1000 API request
are sent to a given API method over the course of an hour. If fewer than 1000
API requests are sent to a given API method per hour, the measurement period
will be defined as the 24 hour period from midnight to midnight (UTC). Any calls
sent during a scheduled maintenance period will be ignored when calculating the
System availability SLA.
Example evaluation
System availability is then calculated as follows (for each API method):
The System responds to 95% of API requests within 5 seconds, and 90% of API
requests within 3 seconds over any one hour period (per API method).
The measurement period will be defined as one hour if more than 1000 API request
are sent to a given API method over the course of an hour. If fewer than 1000
API requests are sent to a given API method per hour, the measurement period
will be defined as the 24 hour period from midnight to midnight (UTC). Any calls
sent during a scheduled maintenance period will be ignored when calculating the
Latency SLA.
Example evaluation
Latency is measuring the time it takes for the Payment Integrator's System to
respond to a Google API request sent while the system is available. Therefore,
latency is calculated as follows:
All rights reserved. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-02-06 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 2025-02-06 UTC."],[[["\u003cp\u003eGoogle enforces Service Level Agreements (SLAs) to maintain a reliable user experience, and the examples provided are related to Google Standard Payments.\u003c/p\u003e\n"],["\u003cp\u003eSystem availability SLAs require the Payment Integrator's systems to be available for 99.9% of requests over a 24-hour period, with a 7-second response time limit.\u003c/p\u003e\n"],["\u003cp\u003eLatency SLAs stipulate that the system must respond to 95% of API requests within 5 seconds, and 90% within 3 seconds over any one hour period.\u003c/p\u003e\n"],["\u003cp\u003eThe content provided is for informational purposes only, and one must refer to the Google Standard Payments contract or Payment Processing Services Agreement for the specific, legally-binding SLAs.\u003c/p\u003e\n"]]],["Google Standard Payments SLAs, though not legally binding here, outline system availability and latency requirements. Systems must be available for 99.9% of requests within 24 hours, responding to valid API requests within 7 seconds. Latency requires responses to 95% of requests within 5 seconds and 90% within 3 seconds. Availability is calculated as successful calls divided by total calls. Latency is measured as the difference between the response received and request sent times. Measurement periods are hourly or daily, dependent on request volume.\n"],null,["Google enforces several Service Level Agreements (SLAs) to ensure a reliable and\nresponsive user experience. Examples of common Google Standard Payments SLAs and\nhow they are measured are provided here.\n| **Warning:** The terms on this page are not legally-binding. You must refer to the specific terms in your Google Standard Payments contract or Payment Processing Services Agreement for the complete set of SLAs your integration is expected to adhere to.\n\nExample SLAs\n\nSystem availability\n\nExample terms\n\nThe Payment Integrator shall make their Systems available to\nGoogle for 99.9% of requests over any 24 hour period (per API method).\n\nThe System shall be considered unavailable for a given request if System fails\nto respond to a valid API request with a valid API response within 7 seconds as\nmeasured by Google after a well-formed transactional packet has been sent to\nthe Payment Integrator.\n\nThe measurement period will be defined as one hour if more than 1000 API request\nare sent to a given API method over the course of an hour. If fewer than 1000\nAPI requests are sent to a given API method per hour, the measurement period\nwill be defined as the 24 hour period from midnight to midnight (UTC). Any calls\nsent during a scheduled maintenance period will be ignored when calculating the\nSystem availability SLA.\n\nExample evaluation\n\nSystem availability is then calculated as follows (for each API method): \n$$ Availability = \\\\frac{CountOfSuccessfulCalls}{CountOfTotalCalls} $$\n\nLatency\n\nExample terms\n\nThe System responds to 95% of API requests within 5 seconds, and 90% of API\nrequests within 3 seconds over any one hour period (per API method).\n\nThe measurement period will be defined as one hour if more than 1000 API request\nare sent to a given API method over the course of an hour. If fewer than 1000\nAPI requests are sent to a given API method per hour, the measurement period\nwill be defined as the 24 hour period from midnight to midnight (UTC). Any calls\nsent during a scheduled maintenance period will be ignored when calculating the\nLatency SLA.\n\nExample evaluation\n\nLatency is measuring the time it takes for the Payment Integrator's System to\nrespond to a Google API request sent while the system is available. Therefore,\nlatency is calculated as follows: \n$$ Latency = DatetimeResponseReceivedByGoogle - DatetimeRequestSentByGoogle $$"]]