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, in the API Commons Rate Limits shape.

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

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

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 Exhausted: HTTP 429
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
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

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