Toss Payments · Rate Limits

Toss Payments Rate Limits

Toss Payments does not publish fixed numeric per-account or per-endpoint rate limits for the Core API. Practical throughput is governed by the nature of the operation rather than a documented per-minute request cap: billing-key authorization can take up to 60 seconds to complete, transaction queries return up to 5000 records per page (cursor pagination via startingAfter), cash receipt queries up to 10000 records, and payout requests accept up to 100 payouts per call (max 1 billion KRW). Clients should implement idempotency (via Idempotency-Key on mutating calls where supported), exponential backoff, and webhook-based reconciliation rather than tight polling.

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

It captures 5 rate-limit definitions, measuring requests, records, payouts, and seconds.

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

Tagged areas include Payments, Payment Gateway, South Korea, Rate Limiting, and Quotas.

5 Limits Throttle: 429
PaymentsPayment GatewaySouth KoreaRate LimitingQuotas

Limits

Core API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Core API.
Transactions Query Page Size account
records
5000 per page
The /v1/transactions endpoint returns up to 5000 records per page with cursor pagination (startingAfter).
Cash Receipts Query Page Size account
records
10000 per page
The /v1/cash-receipts query returns up to 10000 records per page.
Payout Batch Size account
payouts
100 per request
The v2 payouts endpoint accepts up to 100 payout requests per call (max 1 billion KRW total).
Billing Authorization Time request
seconds
up to 60s
Charging a billing key / authorization can take up to 60 seconds to complete.

Policies

Idempotency
Mutating operations such as cancellation support an Idempotency-Key header so retries do not double-apply.
Webhook Retries
Undelivered webhooks are retried up to seven times with exponentially increasing intervals (from 1 minute up to 4096 minutes); endpoints must return HTTP 200.
Backoff Strategy
Clients should implement exponential backoff with jitter and honor Retry-After on 429 responses, and reconcile via webhooks rather than tight polling.

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/toss-payments-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.