Decentro · Rate Limits

Decentro Rate Limits

Decentro does not publish numeric API rate limits on its public site. Per-merchant TPS allowances are tied to the sponsor-bank rail (UPI, IMPS, NEFT, RTGS) and the contractual enrollment with that rail. KYC, DigiLocker, and Aadhaar lookups are also subject to upstream regulator/issuer throttles outside Decentro's control. Numbers are visible only inside the enterprise portal at in.decentro.tech.

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

It captures 2 rate-limit definitions, measuring transactions_per_second and requests_per_minute.

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

Tagged areas include Banking-as-a-Service, FinTech, India, Payments, and Rate Limiting.

2 Limits Throttle: 429
Banking-as-a-ServiceFinTechIndiaPaymentsRate Limiting

Limits

Rail-specific TPS merchant
transactions_per_second
rail-specific — see Decentro enterprise portal
UPI, IMPS, NEFT, and RTGS each carry distinct rail-side TPS allowances negotiated with the sponsor bank.
KYC / Aadhaar / DigiLocker upstream throttles merchant
requests_per_minute
regulator/issuer-defined
These calls are subject to UIDAI, DigiLocker, and credit-bureau throttles that flow through Decentro and cannot be raised by Decentro alone.

Policies

Backoff Strategy
Retry on 429 with exponential backoff and jitter; honor any Retry-After header.
Idempotency for Payments
Use Decentro's idempotency / reference identifiers for payment transactions to avoid double-debits during retries.
Webhook Reliability
Treat webhook delivery as at-least-once. Build idempotent receivers so duplicate delivery does not double-credit ledgers.
Rail Saturation
During festival or salary-cycle peaks, UPI/IMPS rails saturate at the bank side; throttle outbound payouts and pre-fund virtual accounts to absorb spikes.

Sources