Paga · Rate Limits

Paga Rate Limits

Paga does not publish explicit numeric rate limits for its Business, Collect, or Direct Debit APIs. Access is gated primarily by IP whitelisting (Business API) and by idempotency: each operation requires a unique client-generated referenceNumber, and replaying a reference returns the prior result rather than creating a duplicate. Abnormal traffic is subject to fraud controls and account-level throttling at Paga's discretion.

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

It captures 2 rate-limit definitions, measuring requests and source_ip.

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

Tagged areas include Payments, Mobile Money, Fintech, Nigeria, and Rate Limiting.

2 Limits Throttle: 429
PaymentsMobile MoneyFintechNigeriaRate LimitingQuotas

Limits

Documented numeric limit account
requests
not published
Paga does not publish explicit rate-limit numbers for the developer APIs.
IP whitelisting (Business API) account
source_ip
whitelisted IPs only
Business API rejects calls from non-whitelisted IP addresses.

Policies

Idempotency
Each operation requires a unique referenceNumber; replays return the original result and do not duplicate transactions.
Backoff Strategy
Clients should implement exponential backoff with jitter on 5xx/timeouts and reconcile via the status endpoints.
Fraud Controls
Account-level throttling and review may be applied to anomalous or high-value activity.

Sources