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, conforming to the API Commons Rate Limits specification.

It captures 2 rate-limit definitions, measuring requests.

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 Throttle: 429
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