Ozow · Rate Limits

Ozow Rate Limits

Ozow does not publish explicit numeric API rate limits in its developer hub. As a card/EFT payment gateway it applies standard fraud, velocity and abuse controls server-side, and merchant integrations are expected to generate a fresh SHA512 HashCheck per request and to reconcile via the NotifyUrl webhook rather than aggressively polling the transaction-query endpoints. Specific per-endpoint limits are not documented.

Ozow Rate Limits is the machine-readable rate-limit profile for Ozow on the APIs.io network, in the API Commons Rate Limits shape.

It captures 2 rate-limit definitions, measuring requests.

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 2 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Payments, Instant EFT, Pay by Bank, Fintech, and South Africa.

2 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-17.
Written by API Evangelist on 2026-07-17 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsInstant EFTPay by BankFintechSouth AfricaRate LimitingQuotas

Limits

Payment request submission merchant
requests
see provider documentation
Not numerically published; subject to fraud/velocity controls.
Transaction query (GetTransaction / GetTransactionByReference) merchant
requests
see provider documentation
Prefer NotifyUrl webhooks over polling; no published poll ceiling.

Policies

Webhook-first reconciliation
Use the NotifyUrl server-to-server callback for status rather than polling query endpoints.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429.

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/ozow-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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