Tap Payments Rate Limits
Tap Payments does not publish fixed numeric rate limits for its REST API in the public developer reference. As a card-present/card-not-present payment gateway, throughput is governed operationally - by acquirer and scheme limits, fraud and velocity controls, and per-merchant risk configuration - rather than by a published per-minute request cap. Clients should treat the API as rate-limited in principle, handle HTTP 429 responses with exponential backoff, and rely on idempotency/reference fields to avoid duplicate charges on retry.
Tap Payments Rate Limits is the machine-readable rate-limit profile for Tap Payments on the APIs.io network, conforming to the API Commons Rate Limits specification.
It captures 2 rate-limit definitions, measuring requests and transactions.
The profile also includes 2 backoff/retry policies defined and response codes documented for throttled.
Tagged areas include Payments, Fintech, Payment Gateway, MENA, and Rate Limiting.
Limits
Policies
Sources
- https://developers.tap.company/docs/get-started
- https://developers.tap.company/reference/api-endpoint
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/tap-payments-rate-limits"curl "https://apis.io/api/v1/rate-limits?limit=25"Discovery needs no key. Ratings and market analysis are Pro.