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, in the API Commons Rate Limits shape.
It captures 6 rate-limit definitions.
Limit state is signalled in the retryAfter response header, and 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 response codes documented for throttled and quotaExceeded.
Tagged areas include Payments, Rate Limiting, and Africa.
retryAfter
generated, dated 2026-05-24.
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.