Paystack Rate Limits
Reconciled rate-limit policy for the Paystack API. Paystack does not publish hard per-second request limits in its public reference; in practice it applies a leaky-bucket policy at the payment-orchestration layer and throttles abusive callers with HTTP 429 plus a Retry-After header. Sensitive write operations (transfer, refund) carry additional OTP and per-day caps.
Paystack Rate Limits is the machine-readable rate-limit profile for Paystack on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 6 rate-limit definitions.
The profile also includes response codes documented for throttled and quotaExceeded.
Tagged areas include Payments, Rate Limiting, and Africa.
Limits
Sources
- https://paystack.com/docs/api/
- https://paystack.com/docs/payments/transfers/
- https://paystack.com/docs/api/errors/
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/paystack-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.