specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Google Pay
providerId: google-pay
created: '2026-05-04'
modified: '2026-09-12'
generated: '2026-09-12'
method: searched
source: https://developers.google.com/wallet/generic/resources/faq
supersedes: >-
  The 2026-05-04 bulk-sweep scaffold, which invented free/professional/enterprise tiers at
  10/100/1000 requests per minute with X-RateLimit-* headers and applied them to all nine APIs.
  None of those numbers or headers appear anywhere in Google's documentation. They are removed.
description: >-
  Published rate limits for the Google Pay family. Google publishes exactly one number, for the
  Google Wallet API, and publishes no rate-limit response headers at all.
limit_count: 1
limits:
  - name: Google Wallet API request rate
    applies:
      - Google Wallet API
    scope: per-project
    metric: requests_per_second
    limit: 20
    timeFrame: second
    burst: null
    evidence: >-
      "Calls to the Google Wallet API are rate limited to 20 requests per second."
      https://developers.google.com/wallet/generic/resources/faq
undocumented:
  - api: Google Pay API (Web)
    note: >-
      No rate limit published. The surface is a client-side payment sheet invoked by a shopper, so
      there is no server-side quota document.
  - api: Google Pay API for Android
    note: No rate limit published.
  - api: Google Pay & Wallet Developer MCP server
    note: >-
      No rate limit published for paydeveloper.googleapis.com. Google Cloud IAM-gated APIs
      normally carry per-project quotas in the Cloud console, but none is documented publicly for
      this service.
  - api: Google Pay Facilitated Transaction Event API
    note: No rate limit published.
  - api: Google Pay Virtual Cards API
    note: No rate limit published.
  - api: Google Pay Push Provisioning API
    note: No rate limit published.
  - api: Google Pay Payment Card Recognition API
    note: On-device OCR via Google Play Services; no server quota applies.
  - api: Google Pay India Merchant SDK
    note: No rate limit published.
  - api: Google Universal Commerce Protocol
    note: No rate limit published.
headers:
  documented: []
  note: >-
    Google documents NO rate-limit response headers for any Google Pay surface — no
    X-RateLimit-*, no RateLimit-*, no Retry-After, and no stated status code on exhaustion. An
    agent gets a number in a FAQ paragraph and no runtime signal, which is the weakness worth
    recording. The previously-listed header set was scaffold, not observed.
responseCodes:
  throttled: null
  note: >-
    Google's standard JSON error envelope returns HTTP 429 with status RESOURCE_EXHAUSTED across
    googleapis.com services, but Google does not document that for the Wallet 20 rps limit
    specifically, so it is left null rather than asserted.
policies:
  - name: Backoff
    description: >-
      Google publishes no backoff guidance specific to Google Pay. Recorded as absent rather than
      restating generic advice as if it were the provider's policy.