Paytronix · Rate Limits

Paytronix Rate Limits

Paytronix does not publish numeric request-rate, concurrency, or quota limits in its public integration documentation (the API Primer and PXS API Reference describe authentication, formatting, versioning, and service-level error codes, but no rate-limit numbers or rate-limit headers). Access is provisioned per integration via an integration identifier and secret, so any applied throttling is governed by the integration agreement rather than a public tier. The limits below are therefore descriptive placeholders with string values pointing at the documentation; reconciled is false because no numeric limits could be verified. Confirm specific limits with Paytronix during integration onboarding.

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

It captures 2 rate-limit definitions, measuring varies.

The profile also includes 3 backoff/retry policies defined and response codes documented for badRequest, unauthorized, forbidden, and notFound.

Tagged areas include Rate Limiting, Loyalty, and Online Ordering.

2 Limits
Rate LimitingLoyaltyOnline Ordering

Limits

Server (PXS) API requests integration
varies
not publicly documented — governed by the integration agreement
No per-second or per-minute numbers are published; the PXS API Reference documents service-specific error codes but not throttling thresholds.
Online Ordering API requests integration
varies
not publicly documented — see docs.opendining.net
The Open Dining documentation does not publish request-rate or concurrency limits for the ordering endpoints.

Policies

Per-integration scoping
Requests are authenticated with a per-integration identifier and secret (HTTP Basic); any applied limits are scoped to the integration and negotiated during onboarding rather than published as public tiers.
Confirm during onboarding
Because no public numeric limits exist, integrators should confirm acceptable request rates, batch sizes, and concurrency with Paytronix before launch, especially for high-volume POS and batch operations.
Backoff and retry
No Retry-After header is documented; clients should implement conservative exponential backoff on 4xx/5xx responses and idempotent retries keyed on externalTransactionId where supported.

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/paytronix-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.