HyperPay · Rate Limits

Hyperpay Rate Limits

HyperPay (ACI / OPPWA) does not publish specific public API rate-limit numbers. As a card-present-scale payment platform it applies transaction-throughput controls and anti-fraud / velocity checks per merchant channel (entityId) rather than a documented requests-per-minute quota. Bursty or abnormal traffic can be throttled or blocked by fraud tooling. Concrete numeric limits are not documented and are not reconciled in this artifact.

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

It captures 2 rate-limit definitions, measuring transactions.

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

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

2 Limits Throttle: 429
PaymentsPayment GatewayMENASaudi ArabiaRate LimitingQuotas

Limits

Per-channel transaction throughput entityId
transactions
see provider / account manager
Throughput is governed per merchant channel; no public numeric quota is documented.
Velocity / anti-fraud controls merchant
transactions
risk-based
Abnormal velocity or fraud signals can trigger throttling or blocking independent of a fixed rate limit.

Policies

Risk-Based Throttling
Limits are enforced by fraud and risk tooling per merchant channel rather than a published RPM ceiling.
Backoff Strategy
Clients should implement retries with exponential backoff and idempotent merchantTransactionId values to avoid duplicate charges.

Sources