Paysafe · Rate Limits

Paysafe Rate Limits

Paysafe does not publish specific per-second or per-minute API rate-limit numbers in its public developer documentation. Throttling is enforced server-side; responses return HTTP 429 when limits are exceeded. All Paysafe REST APIs share Basic Access Authorization over HTTPS and use the same base domain (api.paysafe.com for production, api.test.paysafe.com for the test environment). Test environment accounts have lower capacity than production and are intended for integration testing, not load testing. For negotiated higher capacity, merchants should contact integrations@paysafe.com.

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

It captures 5 rate-limit definitions, measuring varies.

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

Tagged areas include Payments, Digital Wallets, Prepaid Cards, and Rate Limiting.

5 Limits Throttle: 429
PaymentsDigital WalletsPrepaid CardsRate Limiting

Limits

Production API request rate merchant-account
varies
not publicly documented
Throttling enforced server-side; returns HTTP 429 on excess. Contact integrations@paysafe.com.
Test environment request rate merchant-account
varies
lower than production
Test (api.test.paysafe.com) is for integration testing only, not load or stress testing.
Payment Scheduler API merchant-account
varies
not publicly documented
REST API for subscriptions/plans shares general gateway capacity.
Applications API platform-account
varies
not publicly documented
Merchant onboarding API capacity available upon request through Paysafe account management.
Embedded Wallets API platform-account
varies
not publicly documented
Digital wallet and prepaid card API capacity tied to platform agreement terms.

Policies

Backoff Strategy
Apply exponential backoff with jitter when receiving HTTP 429 or 5xx responses. Honor the Retry-After header when present to determine safe retry timing.
Idempotency
Use deterministic and unique identifiers for payment requests to safely retry transient failures without risk of duplicate charges or enrollments.
Sandbox Discipline
Reserve test environment credentials (api.test.paysafe.com) for integration and unit testing only. Do not run sustained load tests or stress tests against the sandbox.
Capacity Requests
Production capacity increases must be coordinated through your Paysafe account manager or by contacting integrations@paysafe.com. Capacity is tied to processing history and risk review.
Separate Credentials per Environment
Maintain separate API key sets for test and production environments. Never use production credentials in a test or CI/CD context.

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/paysafe-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 email required.

GitHub Google LinkedIn

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