HitPay · Rate Limits

Hitpay Rate Limits

HitPay does not publish specific numeric API rate limits in its public developer documentation. As a regulated payment gateway it applies standard abuse-prevention throttling and returns HTTP 429 on excessive requests; clients should implement retries with exponential backoff. Concrete per-endpoint or per-merchant limits are not documented and are not reconciled in this artifact.

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

It captures 1 rate-limit definition, measuring requests.

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

Tagged areas include Payments, Fintech, PayNow, Southeast Asia, and SMB.

1 Limits Throttle: 429
PaymentsFintechPayNowSoutheast AsiaSMBRate LimitingQuotasThrottling

Limits

API Requests merchant
requests
see provider documentation
No public numeric rate limit is documented; abuse-prevention throttling applies.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on HTTP 429 and honor Retry-After when present.
Idempotency
Use reference_number on payment requests to correlate and de-duplicate retried creations.

Sources