2C2P Rate Limits
2C2P does not publish fixed numeric rate limits for the Payment Gateway (PGW v4.3) API. As a payment acquirer, throughput is governed by the merchant agreement, risk / fraud controls, and the underlying card scheme and alternative-payment-method processors rather than by a documented requests-per-second cap. Idempotency is anchored on a unique invoiceNo per transaction, and transaction results should be confirmed via the backend notification webhook and Payment Inquiry rather than by tight polling.
2C2P Rate Limits is the machine-readable rate-limit profile for 2C2P on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 3 rate-limit definitions, measuring requests and invoiceNo.
The profile also includes 3 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Payments, Payment Gateway, Southeast Asia, Rate Limiting, and Quotas.
Limits
Policies
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.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/rate-limits/2c2p-rate-limits"
curl "https://apis.io/api/v1/rate-limits?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.