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, conforming to the API Commons Rate Limits specification.

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

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 Throttle: 429
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