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: Global Payments
providerId: global-payments
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Rate Limiting
  - Payments
  - Payment Processing
description: Global Payments does not publish numeric per-second / per-minute API rate limits on its public
  developer documentation. Throttling is applied at the gateway level and varies by product (Unified Payments
  API vs Global Payments Integrated). Merchants experiencing throttling should contact integration support
  for limit raises.
notes: Reconcile after the developer portal publishes per-product numeric limits.
sources:
  - https://developer.globalpay.com/
  - https://developer.globalpaymentsintegrated.com/
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Unified Payments API throttling
    scope: account
    metric: varies
    limit: see Global Payments developer support
  - name: Global Payments Integrated API throttling
    scope: account
    metric: varies
    limit: see Global Payments Integrated support
policies:
  - name: Backoff Strategy
    description: Apply exponential backoff with jitter on 429 / 503 responses; retry idempotent reads
      only.
  - name: Idempotency
    description: Use idempotency keys on payment-creation endpoints to prevent duplicate authorizations
      on retry.
  - name: Support escalation
    description: For sustained high-volume processing, contact Global Payments integration support to
      raise gateway-level limits before launch.
maintainers:
  - FN: Kin Lane
    email: info@apievangelist.com