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: Bancontact
providerId: bancontact
created: '2026-05-04'
modified: '2026-09-17'
generated: '2026-09-17'
method: searched
source: >-
  https://docs.bancontactpro.com/guides/general/errorsandstatuses052025 and the 429 responses
  declared on merchant-get-payment, cancel_payment, search, create and create-refund in
  openapi/bancontact-payment-v3-api-openapi.yml (2026-09-17). Replaces the 2026-05-04 scaffold,
  whose per-minute and monthly numbers were never published by the provider.
tags: [Banking, Belgium, Payments, Rate Limiting]
description: >-
  Bancontact Pro documents THAT it rate-limits (HTTP 429 "Too Many Requests – Rate limit
  exceeded", declared on five Payment V3 operations with an empty Error Codes body) but publishes
  no numeric limit, window, scope or response header. limit_count is therefore an honest 0.
limit_count: 0
headers:
  limit: null
  remaining: null
  reset: null
  retryAfter: null
  note: No rate-limit headers are documented; the errors guide says "respect HTTP 429 responses with retry-after logic" without naming a header.
responseCodes:
  throttled: 429
  serviceUnavailable: 503
limits: []
operations_declaring_429: [merchant-get-payment, cancel_payment, search, create, create-refund]
policies:
  - name: Backoff Strategy
    description: On 429 or 5xx, retry with exponential backoff (provider guidance); TRY_AGAIN_LATER (503) is explicitly retryable after a delay.
  - name: Inbound callback throttling
    description: If the merchant's callback endpoint answers 429, Bancontact retries the callback for up to 24 hours.
maintainers:
  - FN: Kin Lane
    email: kin@apievangelist.com