PayTabs · Rate Limits

Paytabs Rate Limits

PayTabs does not publish explicit numeric API rate limits (RPM/RPD) for the PT2 REST API. As a card acquirer, throughput is governed by risk, fraud, and velocity controls at the profile/merchant level rather than a public developer quota. Abusive or abnormal request patterns may be throttled or blocked. Clients should implement retries with backoff and rely on the idempotency of cart_id / tran_ref plus /payment/query to reconcile rather than blindly retry /payment/request.

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

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

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

Tagged areas include Payments, Payment Gateway, MENA, Rate Limiting, and Throttling.

2 Limits Throttle: 429
PaymentsPayment GatewayMENARate LimitingThrottling

Limits

Request throughput profile
requests
not publicly documented (risk/velocity managed)
Governed by fraud/velocity controls per merchant profile, not a published quota.
Transaction velocity merchant
transactions
risk-based
Unusual volume or value may trigger review, hold, or decline.

Policies

Backoff Strategy
Use exponential backoff with jitter; honor Retry-After on 429.
Safe Retries
Reconcile with POST /payment/query on the same cart_id/tran_ref before retrying a payment to avoid duplicate charges.

Sources