MoMo · Rate Limits
Momo Rate Limits
Momo Rate Limits is the rate-limit profile for MoMo on the APIs.io network.
The provider publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
Limit state is signalled in the rate_limit_headers, retry_after, and exhaustion_status response headers.
Tagged areas include Payments, Mobile Payments, Fintech, Digital Wallet, and Payment Gateway.
0 Limits
rate_limit_headersretry_afterexhaustion_status
Transcribed from the provider's documentation on 2026-08-26 — developers.momo.vn/v3/docs/payment/onboarding/integration....
View Source
Limits
MoMo publishes no rate limits that could be read; the profile records that absence rather than inventing a ceiling.
MoMo publishes NO rate limits. Searched all 212 developer-docs URLs plus the Business Page, Voucher Distribution and Mini App Open API sections: there is no requests-per-second figure, no quota, no burst allowance, no 429 status code, and no X-RateLimit-*, RateLimit-* or Retry-After header documented anywhere. An agent calling MoMo has no runtime signal telling it to back off, and no documented number telling it how fast it may go. That absence is the finding and is recorded as limit_count: 0 rather than omitted. What MoMo does publish are TIMING contracts in the other direction — how long the caller must be prepared to wait, and how fast the caller must answer MoMo — which are captured below because they are the only runtime pacing rules an integrator actually gets.
PaymentsMobile PaymentsFintechDigital WalletPayment GatewayQR PaymentsDisbursementsBuy Now Pay LaterE-CommerceVietnam
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.