specification: API Commons Rate Limits
specificationVersion: '0.1'
schema: https://raw.githubusercontent.com/api-evangelist/interface-research/main/schema/api-commons.yml#/$defs/RateLimits
provider: Decentro
providerId: decentro
created: '2026-05-04'
# Provenance stamped 2026-08-11: this artifact was written by the API Evangelist
# bulk sweep dated 2026-05-04, not harvested from the provider. See roadmap#35.
method: generated
modified: '2026-05-05'
reconciled: false
tags:
  - Banking-as-a-Service
  - FinTech
  - India
  - Payments
  - Rate Limiting
description: 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.
sources:
  - https://decentro.tech
  - https://in.decentro.tech
notes: No public numeric rate limits. Limits depend on rail (UPI, IMPS, NEFT, RTGS) and the
  sponsor-bank contract. KYC/Aadhaar/DigiLocker limits are governed by upstream regulators.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits:
  - name: Rail-specific TPS
    scope: merchant
    metric: transactions_per_second
    limit: rail-specific — see Decentro enterprise portal
    notes: UPI, IMPS, NEFT, and RTGS each carry distinct rail-side TPS allowances negotiated with
      the sponsor bank.
  - name: KYC / Aadhaar / DigiLocker upstream throttles
    scope: merchant
    metric: requests_per_minute
    limit: regulator/issuer-defined
    notes: These calls are subject to UIDAI, DigiLocker, and credit-bureau throttles that flow
      through Decentro and cannot be raised by Decentro alone.
policies:
  - name: Backoff Strategy
    description: Retry on 429 with exponential backoff and jitter; honor any Retry-After header.
  - name: Idempotency for Payments
    description: Use Decentro's idempotency / reference identifiers for payment transactions to
      avoid double-debits during retries.
  - name: Webhook Reliability
    description: Treat webhook delivery as at-least-once. Build idempotent receivers so duplicate
      delivery does not double-credit ledgers.
  - name: Rail Saturation
    description: 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.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com