Culqi · Rate Limits

Culqi Rate Limits

Culqi does not publish specific numeric API rate limits (RPM/RPS or daily quotas) in its public developer documentation. As a card-present-grade payment processor it applies platform-level abuse protection, per-merchant risk controls and antifraud checks, and returns standard HTTP throttling responses under sustained load. Concrete per-endpoint limits are not documented and should be confirmed with Culqi support for high-volume use.

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

It captures 2 rate-limit definitions, measuring requests.

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

Tagged areas include Payments, Payment Gateway, FinTech, Peru, and Rate Limiting.

2 Limits Throttle: 429
PaymentsPayment GatewayFinTechPeruRate LimitingQuotasThrottling

Limits

API request rate merchant
requests
not published
No public RPM/RPS quota; platform-level abuse protection applies.
Tokenization attempts merchant
requests
not published
Repeated failed tokenization / charge attempts may be throttled or flagged by antifraud.

Policies

Antifraud controls
Culqi applies antifraud (antifraude) evaluation and device fingerprinting on charges; suspicious volume may be blocked independent of a fixed rate limit.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
3-D Secure
Card charges may require Culqi 3DS challenge/confirm, which paces card-not-present traffic per cardholder.

Sources