PAY.JP · Rate Limits

Payjp Rate Limits

PAY.JP enforces per-second request rate limits split into three zones by key type and operation. Token creation (publishable-key "pk" zone), payment operations such as charges and refunds ("payment" zone), and other secret-key requests ("sk" zone) each have their own thresholds, with much lower limits in test mode. Exceeding a limit returns HTTP 429 with the over_capacity error code.

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

It captures 3 rate-limit definitions, measuring requests_per_second.

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

Tagged areas include Payments, FinTech, Japan, Rate Limiting, and Quotas.

3 Limits Throttle: 429
PaymentsFinTechJapanRate LimitingQuotasThrottling

Limits

Token zone (pk) account
requests_per_second
10 rps live / 2 rps test
Applies to token creation via the publishable key (POST /tokens).
Payment zone account
requests_per_second
14 rps live / 2 rps test
Applies to payment operations such as charges and refunds.
Secret-key zone (sk) account
requests_per_second
30 rps live / 2 rps test
Applies to other secret-key requests (customers, plans, subscriptions, reads, etc.).

Policies

Test-mode throttling
Test keys (sk_test_ / pk_test_) are limited to ~2 rps across all zones.
Backoff Strategy
On HTTP 429 over_capacity, back off with exponential delay and jitter and retry idempotent reads.

Sources