Formance · Rate Limits

Formance Rate Limits

Formance does not publish fixed public per-endpoint rate limits. Self-hosted open-source deployments are bounded by the resources you provision (database throughput, ledger write contention, and connector-side limits at the upstream payment processors). Formance Cloud applies platform protections and fair-use limits per stack / organization that are governed by your plan and may return HTTP 429 when exceeded. Specific numeric values are not reconciled in this artifact.

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

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

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

Tagged areas include Financial Infrastructure, Ledger, Payments, Rate Limiting, and Quotas.

3 Limits Throttle: 429
Financial InfrastructureLedgerPaymentsRate LimitingQuotasThrottling

Limits

Cloud API Requests organization
requests
see provider documentation
Fair-use / plan-governed request limits per stack on Formance Cloud.
Ledger Write Throughput ledger
transactions
infrastructure-bound
Self-hosted ledger write throughput is bounded by your Postgres sizing; transactions touching the same accounts serialize to preserve double-entry consistency.
Connector Limits connector
requests
upstream-provider dependent
Payment connector operations are additionally subject to the rate limits of the underlying processor (Stripe, Wise, Adyen, Mangopay, etc.).

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses.
Idempotency
Use references / idempotency keys on transaction and payment-initiation creation so retries after throttling do not double-post.

Sources