Yoco · Rate Limits

Yoco Rate Limits

Yoco does not publish fixed numeric rate limits for its online payments APIs. The Checkout API (payments.yoco.com/api) and the versioned Yoco API (api.yoco.com/v1) are transactional REST surfaces; practical throughput is governed by payment processing and standard abuse protection rather than a documented per-minute request cap. Idempotency-Key headers are supported on checkout creation and refunds to make retries safe. Clients should implement exponential backoff with jitter and honor Retry-After on any 429 response.

Yoco Rate Limits is the machine-readable rate-limit profile for Yoco on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests and records.

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

Tagged areas include Payments, Fintech, Payment Gateway, Card Payments, and Rate Limiting.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-12.
Written by API Evangelist on 2026-07-12 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
PaymentsFintechPayment GatewayCard PaymentsRate LimitingQuotas

Limits

Checkout API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Checkout API.
Yoco API (v1) Requests account
requests
not published
No fixed numeric request-rate limit is documented for the versioned read API.
List Payments Page Size request
records
50 default (cursor paginated)
GET /v1/payments returns up to a limit per page and a cursor for the next page.

Policies

Idempotency
Checkout creation and refunds accept an Idempotency-Key header so retries do not create duplicates.
Backoff Strategy
Clients should use exponential backoff with jitter and honor Retry-After on 429 responses.
Webhook Retries
Yoco delivers signed webhook events; consumers should respond quickly and rely on retries plus idempotent handling for reliable processing.

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