FIS Global · Rate Limits

Fis Rate Limits

FIS does not publish numeric rate limits for its public-facing API products. Throttles are sized per FI customer's licensed capacity tier and are governed by the master service agreement. Public 429/503 conventions apply to web-facing endpoints; legacy mainframe and IBS connectors typically operate on session/queue throughput limits rather than HTTP rate limits.

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

It captures 1 rate-limit definition, measuring varies.

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

Tagged areas include Banking, Core Banking, Financial Services, Payments, and Wealth Management.

1 Limits Throttle: 429
BankingCore BankingFinancial ServicesPaymentsWealth ManagementRate Limiting

Limits

Per-customer FI throttle customer/api-key
varies
per-FI capacity tier; not publicly published

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter on 429/5xx responses; Retry-After is honored when emitted.
Capacity Tiering
Throughput is provisioned per customer financial institution at onboarding; raises require account-team engagement and capacity planning.
Settlement / Batch Windows
Batch and settlement windows on core banking and payments products may impose stricter throttles or queueing during cutoff periods.
Sandbox vs Production
Sandbox throughput is intentionally low and unsuitable for performance/load testing; production load tests must be coordinated with the FIS account team.

Sources