Wise · Rate Limits

Wise Rate Limits

Wise does not publish a fixed numeric request-per-second rate limit for the Platform API. Limits are applied at the account level and adjusted dynamically based on usage patterns and risk signals. Excessive request volume returns HTTP 429 Too Many Requests and integrators are expected to honour Retry-After. Webhook delivery is retried with exponential backoff. Reconciliation against a published numeric ceiling pending - Wise asks partners with high-volume needs to coordinate via account management.

3 Limits Throttle: 429
PaymentsFXCross-BorderBankingMulti-CurrencyRate LimitingThrottling

Limits

Account-Level Throttle account
requests ยท minute
dynamic
Wise applies dynamic per-account limits. There is no public RPS ceiling. Partners requiring elevated throughput coordinate via account management.
Authentication Endpoints client
requests
tighter than data endpoints
Token issuance and OAuth endpoints are throttled more aggressively than data endpoints to deter credential stuffing.
Webhook Delivery subscription
events
best-effort with retry
Failed webhook deliveries are retried with exponential backoff for up to ~14 attempts before the subscription is marked unhealthy.

Policies

429 Throttling
When the dynamic account-level threshold is exceeded the API returns 429 Too Many Requests. Clients should respect any Retry-After header.
Backoff Strategy
Implement exponential backoff with jitter for both 429 and 5xx responses; cache idempotent reads (profiles, recipients, currencies) to reduce volume.
Idempotency
Use the X-idempotence-uuid header on transfer creation and funding calls so retries do not create duplicate money movements.

Sources