braintree · Rate Limits

Braintree Rate Limits

Braintree (a PayPal service) does not publish per-second or per-minute API rate-limit numbers on its public developer documentation. Throttling is enforced server-side and returns HTTP 429 or 503 on overuse. The Braintree GraphQL API and legacy server SDKs share the same gateway capacity per merchant account. Sandbox accounts have lower headroom than production and exist primarily for integration testing.

Braintree Rate Limits is the machine-readable rate-limit profile for braintree on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 3 rate-limit definitions, measuring varies.

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

Tagged areas include Payments, Credit Cards, PayPal, Venmo, and Rate Limiting.

3 Limits Throttle: 429
PaymentsCredit CardsPayPalVenmoRate Limiting

Limits

Production gateway request rate merchant-account
varies
see Braintree support
Not publicly documented; throttling returns 429 / 503.
Sandbox gateway request rate merchant-account
varies
lower than production - integration testing only
Sandbox is meant for integration testing, not load testing.
GraphQL API merchant-account
varies
shares production gateway capacity

Policies

Backoff Strategy
Apply exponential backoff with jitter on 429 and 5xx responses; honor Retry-After when present.
Idempotency
Use deterministic transaction identifiers and the SDK's built-in idempotency support to safely retry transient failures without double-charging.
Sandbox Discipline
Reserve sandbox credentials for integration tests; do not run sustained load tests against sandbox.
Capacity Increase
Production capacity increases are negotiated through Braintree support and are tied to processing history and risk review.

Sources