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

It captures 3 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 2 backoff/retry policies defined and response codes documented for throttled.

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

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

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