Apple Pay · Rate Limits

Apple Pay Rate Limits

Apple does not publish numeric rate limits for the Apple Pay merchant validation endpoint (apple-pay-gateway.apple.com), the Apple Pay JS / ApplePaySession surface, or PassKit native APIs. Throughput is bounded in practice by the merchant's payment-processor capacity (Stripe, Adyen, Braintree, etc.) and Apple's anti-abuse fairness throttling. Apple may apply dynamic throttling on suspicious patterns and signals 429/503 in those cases.

Apple Pay Rate Limits is the machine-readable rate-limit profile for Apple Pay on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring varies.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 4 backoff/retry policies defined and response codes documented for throttled and serviceUnavailable.

Tagged areas include Rate Limiting, Payments, and Apple.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-05-05.
Written by API Evangelist on 2026-05-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Rate LimitingPaymentsApple

Limits

Merchant validation endpoint merchant-id
varies
not publicly documented
Calls to apple-pay-gateway.apple.com for merchant session creation are subject to Apple's anti-abuse fairness controls.
ApplePaySession (client) device
varies
bounded by user interaction
ApplePaySession is user-initiated; server-side throughput is bounded by the merchant's checkout volume and payment-processor capacity.
PassKit device
varies
bounded by device

Policies

Backoff Strategy
Implement exponential backoff with jitter on merchant-validation 429/503 responses; surface a generic 'try again' state to the buyer to avoid duplicate session creation.
Processor Coordination
Apple Pay tokens are exchanged with the merchant's payment processor (Stripe, Adyen, Braintree, etc.) — that processor's rate limits and idempotency keys govern downstream charge attempts.
Sandbox Testing
Use Apple Pay sandbox tester accounts and processor sandbox endpoints for load and edge-case testing rather than touching production endpoints.
Anti-abuse Detection
Apple may dynamically throttle suspicious merchant validation patterns; ensure server-to-server merchant identity calls are signed correctly and not retried in tight loops.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/apple-pay-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.