Kora · Rate Limits

Korapay Rate Limits

Kora does not publish fixed numeric API rate limits in its developer documentation. As a payments processor, practical throughput is governed more by transaction-level controls than by a per-minute request cap: bulk payouts are bounded by a per-batch payout count (minimum 2), payouts require a sufficient available balance, and certain products (card payments, mobile money) must be enabled on the account. Payout security controls such as IP whitelisting can also gate requests. Clients should treat the API as rate-limited in principle, handle HTTP 429 responses with backoff, and rely on idempotent references to avoid duplicate charges or payouts on retries.

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

It captures 4 rate-limit definitions, measuring requests, payouts, balance, and amount.

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

Tagged areas include Payments, Payment Gateway, Africa, Nigeria, and Rate Limiting.

4 Limits Throttle: 429
PaymentsPayment GatewayAfricaNigeriaRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the merchant API.
Bulk Payout Batch Size request
payouts
minimum 2 per batch; maximum not published
A bulk payout must contain at least 2 payouts; the upper bound is not documented.
Payout Balance account
balance
bounded by available balance
Payouts (single and bulk) are disbursed from your positive available balance and fail without sufficient funds.
Transaction Amount transaction
amount
per product / market
Per-product minimum and maximum transaction amounts apply and vary by market and channel; verify with Kora.

Policies

Backoff Strategy
On HTTP 429 or transient errors, retry with exponential backoff and jitter.
Idempotency via References
Use unique merchant references (and batch_reference for bulk) so retries do not create duplicate charges or payouts.
Payout IP Whitelisting
Payout requests can be restricted to whitelisted IP addresses configured on the merchant dashboard.

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/korapay-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.