Moyasar · Rate Limits

Moyasar Rate Limits

Moyasar does not publish fixed numeric per-account or per-endpoint rate limits for its REST API in the public documentation. Standard payment-gateway hygiene applies: authenticate every request over HTTPS with a valid API key, use the `given_id` idempotency field on payment creation to avoid duplicate charges on retries, and implement exponential backoff with jitter on transient errors. Webhook delivery is retried by Moyasar (up to six attempts) when the merchant endpoint does not return a 2xx quickly.

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

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

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

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

3 Limits Throttle: 429
PaymentsPayment GatewaySaudi ArabiamadaRate LimitingQuotas

Limits

REST API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Moyasar REST API.
Payment Idempotency account
requests
client-controlled
Supply a UUID in `given_id` on create-payment to make retries idempotent and avoid duplicate charges.
Webhook Delivery Retries webhook
attempts
up to 6 attempts
Moyasar retries webhook delivery when the endpoint does not quickly return a 2xx status code.

Policies

HTTPS Required
All API calls must be made over HTTPS; plain HTTP requests are rejected.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on any 429 responses.
Idempotency
Use the given_id field on payment creation so network retries do not create duplicate payments.

Sources