Openpay · Rate Limits

Openpay Rate Limits

Openpay does not publish explicit numeric request-per-second or request-per-minute rate limits in its public API reference. As a payments platform it applies account- and merchant-level throttling and anti-fraud controls, and may return HTTP 429 or service-unavailable responses under excessive load. List endpoints are paginated via offset and limit query parameters. Specific per-merchant limits are not reconciled in this artifact and should be confirmed with Openpay.

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

It captures 3 rate-limit definitions, measuring requests, records, and transactions.

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

Tagged areas include Payments, Fintech, Cards, SPEI, and Subscriptions.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-06-21.
Written by API Evangelist on 2026-06-21 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsFintechCardsSPEISubscriptionsRate LimitingQuotasThrottling

Limits

Requests Per Merchant merchant
requests
see provider documentation
No public numeric per-merchant request rate limit is documented.
List Pagination endpoint
records
offset / limit query parameters
List endpoints return paginated results; default limit is small (commonly 10).
Anti-Fraud Throttling account
transactions
dynamic
Velocity and anti-fraud rules may decline or throttle bursts of card charges.

Policies

Pagination
Use offset and limit on list endpoints to page through charges, customers, payouts, and fees.
Backoff Strategy
Clients should implement exponential backoff with jitter on 429 and 5xx responses and avoid retrying non-idempotent charge creation without an order_id.
Idempotency
Send a unique order_id on charges and payouts to avoid duplicate transactions on retry.

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/openpay-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.