Geidea · Rate Limits

Geidea Rate Limits

Geidea does not publish fixed numeric rate limits for the Payment Gateway API in its public developer documentation. As a regulated payments platform, request throughput and anti-fraud velocity controls are applied per merchant account at the gateway and are not exposed as public per-minute quotas. Practical throughput is governed by the merchant's onboarding profile, risk controls, and the acquiring bank / scheme limits rather than by a documented developer rate cap.

Geidea Rate Limits is the machine-readable rate-limit profile for Geidea on the APIs.io network, in the API Commons Rate Limits shape.

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

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, Rate Limiting, and Quotas.

2 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 GatewayRate LimitingQuotas

Limits

Payment Gateway API Requests merchant
requests
not published
No fixed numeric request-rate limit is documented for the Payment Gateway API.
Transaction Velocity merchant
transactions
risk-based
Anti-fraud velocity and volume controls are applied per merchant profile, not published as a developer quota.

Policies

Server-to-Server Only
Direct API calls must be made from the merchant backend; the API password must never be exposed in a front-end.
Backoff and Retry
Clients should use exponential backoff with jitter on transient errors and honor any Retry-After header on 429 responses.
Idempotency by Reference
Use a unique merchantReferenceId per order so retried requests can be reconciled and duplicate charges avoided.

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