PayMongo · Rate Limits

Paymongo Rate Limits

PayMongo enforces a global request-rate cap on the REST API. Per the developer documentation, if the request rate exceeds 100 requests per second (6,000 per minute) requests are blocked; the block is automatically lifted within the next minute once the rate returns to normal. Throttled requests return HTTP 429 Too Many Requests. PayMongo recommends idempotency keys on create calls so retries after a 429 do not double-charge.

Paymongo Rate Limits is the machine-readable rate-limit profile for PayMongo 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 3 backoff/retry policies defined and response codes documented for throttled.

Tagged areas include Payments, FinTech, Philippines, Rate Limiting, and Quotas.

2 Limits Throttle: 429
PaymentsFinTechPhilippinesRate LimitingQuotasThrottling

Limits

Requests Per Second account
requests
100
Exceeding this blocks requests until the rate normalizes (auto-lifted within the next minute).
Requests Per Minute account
requests
6000
Equivalent per-minute expression of the 100 req/s cap.

Policies

Automatic Unblock
Blocks are automatically lifted within the following minute once the request rate drops back below the threshold.
Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 responses.
Idempotency
Send an idempotency key on create requests so that safe retries after a 429 or network failure do not create duplicate charges.

Sources