MoMo is Vietnam's largest mobile-money and e-wallet platform, operated by Online Mobile Services Joint Stock Company (Cong ty Co phan Dich vu Di dong Truc tuyen, "M_Service"), founded in 2007 and licensed by the State Bank of Vietnam for e-wallet, money transfer and collection/disbursement services. Alongside the consumer wallet it runs a merchant payments business whose public developer surface at developers.momo.vn documents the All-in-One (AIO v2) Payment Gateway for wallet, domestic ATM card, credit card, Apple Pay, Google Pay, Buy Now Pay Later, POS Quick Pay and static/dynamic QR acceptance, single and batch disbursement, collection links, and tokenised one-click and subscription payments. It also publishes a Business Page OpenAPI, a Voucher Distribution API and a Mini App Open Platform for third-party apps embedded inside the MoMo app. Integration is HMAC-SHA256 signed with RSA and AES payload encryption, uses requestId-based idempotency and server-to-server IPN callbacks, and is distributed as fourteen public Postman collections plus first-party PHP, Java and mobile SDKs.
MoMo is listed with 4 APIs on the APIs.io network, including All-in-One Payment Gateway (AIO v2), and 3 more. Tagged areas include Payments, Mobile Payments, Fintech, Digital Wallet, and Payment Gateway.
The MoMo catalog on APIs.io includes 1 event-driven AsyncAPI specification.
MoMo’s developer surface includes documentation, API reference, getting-started guide, support, engineering blog, signup flow, authentication, and 27 more developer resources.
47.4/100developing▬ flatAgent28/100agent awareFront door AI4/6
moderate
Heartbeat0/100
dormant
saas
Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →
Regulatory Posture applies to this provider. Its tags matched the
Payments regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for
this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero:
never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and
several others — scorable at all.
The six quality facets above are damped to 85 points between them,
because the conditional facet above carries the other
15. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 85% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/momo/"><img src="https://apis.io/badge/momo/card.svg" alt="MoMo on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Raise your score.
Agent readiness — checks not met, largest first (exact, from this profile):
MCP Server+12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Delegated User Identity+6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)
7 more unmet checks in the Agent Readiness table above.
Kin Score — facets with the most composite points still available (weight × headroom):
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.
Server-to-server API for operating a MoMo Business Page: list and read managed pages, update page detail, images, logo, opening times, utilities and ambiences, publish and read ...
API for creating and distributing promotion campaigns and voucher codes to MoMo users, and for reconciling redemption. Create and update campaigns, upload voucher codes by file,...
The M_Service Open Platform server-to-server API used by Mini Apps embedded in the MoMo app. Exchange a user authorisation code for a short-lived access token, read the user pro...
aid: momo
name: MoMo
description: MoMo is Vietnam's largest mobile-money and e-wallet platform, operated by Online Mobile Services Joint Stock
Company (Cong ty Co phan Dich vu Di dong Truc tuyen, "M_Service"), founded in 2007 and licensed by the State Bank of Vietnam
for e-wallet, money transfer and collection/disbursement services. Alongside the consumer wallet it runs a merchant payments
business whose public developer surface at developers.momo.vn documents the All-in-One (AIO v2) Payment Gateway for wallet,
domestic ATM card, credit card, Apple Pay, Google Pay, Buy Now Pay Later, POS Quick Pay and static/dynamic QR acceptance,
single and batch disbursement, collection links, and tokenised one-click and subscription payments. It also publishes a
Business Page OpenAPI, a Voucher Distribution API and a Mini App Open Platform for third-party apps embedded inside the
MoMo app. Integration is HMAC-SHA256 signed with RSA and AES payload encryption, uses requestId-based idempotency and server-to-server
IPN callbacks, and is distributed as fourteen public Postman collections plus first-party PHP, Java and mobile SDKs.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source:
- authentication
- scopes
- rate-limits
- security
- sandbox
generated: '2026-11-02'
method: derived
image: https://homepage.momocdn.net/img/momo-amazone-s3-api-241029082636-638657871963540172.jpg
url: https://raw.githubusercontent.com/api-evangelist/momo/refs/heads/main/apis.yml
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-26'
modified: '2026-08-26'
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Payments
- Mobile Payments
- Fintech
- Digital Wallet
- Payment Gateway
- QR Payments
- Disbursements
- Buy Now Pay Later
- E-Commerce
- Vietnam
tags_raw:
- Payments
- Mobile Payments
- FinTech
- Digital Wallet
- Payment Gateway
- QR Payments
- Disbursement
- Buy Now Pay Later
- E-commerce
- Vietnam
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
apis:
- aid: momo:aio-payment-gateway
name: MoMo All-in-One Payment Gateway (AIO v2)
description: The MoMo All-in-One (AIO v2) merchant payment gateway. One integration covers MoMo e-wallet, domestic ATM card,
credit card, Apple Pay, Google Pay, Buy Now Pay Later, Quick Pay POS scanner, collection links and static/dynamic QR acceptance,
plus transaction query, two-step capture/cancel confirm, reverse and refund, tokenisation (account binding and subscription)
and single/batch disbursement. All calls are POST JSON signed with HMAC-SHA256; results are pushed back over IPN.
humanURL: https://developers.momo.vn/v3/docs/payment/guides/payment-with-aio/
baseURL: https://payment.momo.vn/v2/gateway/api
tags:
- Payments
- Payment Gateway
- Refunds
- Disbursements
- Tokenization
tags_raw:
- Payments
- Payment Gateway
- Refunds
- Disbursement
- Tokenization
properties:
- type: Documentation
url: https://developers.momo.vn/v3/docs/payment/guides/payment-with-aio/
- type: APIReference
url: https://developers.momo.vn/v3/docs/payment/api/wallet/onetime/
- type: Postman
url: https://developers.momo.vn/v3/docs/payment/api/other/postman/
- type: Sandbox
url: https://developers.momo.vn/v3/docs/payment/onboarding/test-instructions/
- aid: momo:business-page-openapi
name: MoMo Business Page OpenAPI
description: 'Server-to-server API for operating a MoMo Business Page: list and read managed pages, update page detail,
images, logo, opening times, utilities and ambiences, publish and read posts and their comments, read ratings and reviews,
build customer segments, register and send customer-care and automated notification messages, and pull page view/interaction/payment
reports. Authenticated with a Partner Id plus an X-API-KEY scoped to the permission groups granted in the MoMo for Business
portal.'
humanURL: https://developers.momo.vn/v3/docs/business-page/overall/
baseURL: https://business.momo.vn/api
tags:
- Business Page
- Messaging
- Content
- Reporting
properties:
- type: Documentation
url: https://developers.momo.vn/v3/docs/business-page/overall/
- type: GettingStarted
url: https://developers.momo.vn/v3/docs/business-page/start/
- aid: momo:voucher-distribution
name: MoMo Voucher Distribution API
description: API for creating and distributing promotion campaigns and voucher codes to MoMo users, and for reconciling
redemption. Create and update campaigns, upload voucher codes by file, query campaign and voucher-code status, and post
redemption results back to MoMo. Authenticated with clientId/clientSecret exchanged for a 24-hour bearer access token;
every request carries an X-Request-Id UUID.
humanURL: https://developers.momo.vn/v3/docs/voucher-distribution/overall/
baseURL: https://business.momo.vn/api
tags:
- Vouchers
- Promotions
- Loyalty
properties:
- type: Documentation
url: https://developers.momo.vn/v3/docs/voucher-distribution/overall/
- type: GettingStarted
url: https://developers.momo.vn/v3/docs/voucher-distribution/integration-documentation/
- aid: momo:mini-app-open-api
name: MoMo Mini App Open API
description: The M_Service Open Platform server-to-server API used by Mini Apps embedded in the MoMo app. Exchange a user
authorisation code for a short-lived access token, read the user profile fields the user consented to share, and push
notifications into the MoMo app. Requests carry an OAuth 2.0-style bearer JWT plus an OP-Signature (SHA256withRSA over
data + M-Timestamp + openSecretKey) and optional AES payload encryption under an RSA-wrapped symmetric key.
humanURL: https://developers.momo.vn/v3/docs/app-center/development-guideline/components-api-sdk/open-api/api-specifications/
baseURL: https://openapi.momo.vn/gateway/open/v1
tags:
- Mini App
- Identity
- Notification
tags_raw:
- Mini App
- Identity
- Notifications
properties:
- type: Documentation
url: https://developers.momo.vn/v3/docs/app-center/development-guideline/components-api-sdk/open-api/api-specifications/
- type: APIReference
url: https://developers.momo.vn/v3/docs/app-center/development-guideline/components-api-sdk/open-api/catalog-functions/
- type: Authentication
url: https://developers.momo.vn/v3/docs/app-center/development-guideline/components-api-sdk/open-api/open-api-security/
common:
- type: DomainSecurity
url: security/momo-domain-security.yml
- type: Website
url: https://www.momo.vn/
- type: DeveloperPortal
url: https://developers.momo.vn/
- type: Documentation
url: https://developers.momo.vn/v3/docs/payment/guides/home/
- type: APIReference
url: https://developers.momo.vn/v3/docs/payment/api/wallet/onetime/
- type: GettingStarted
url: https://developers.momo.vn/v3/docs/payment/onboarding/integration-process/
- type: Support
url: https://developers.momo.vn/v3/docs/app-center/technical-support/
- type: HelpCenter
url: https://www.momo.vn/hoi-dap
- type: Blog
url: https://www.momo.vn/blog
- type: GitHubOrganization
url: https://github.com/momo-wallet
- type: SignUp
url: https://business.momo.vn/
- type: TermsOfService
url: https://www.momo.vn/dieu-khoan-dieu-le
- type: PrivacyPolicy
url: https://www.momo.vn/chinh-sach-quyen-rieng-tu
- type: Postman
url: https://developers.momo.vn/v3/docs/payment/api/other/postman/
- type: Packages
url: packages/momo-packages.yml
- type: SDKs
url: packages/momo-packages.yml
- type: Authentication
url: authentication/momo-authentication.yml
- type: OAuthScopes
url: scopes/momo-scopes.yml
- type: Conventions
url: conventions/momo-conventions.yml
- type: Idempotency
url: conventions/momo-conventions.yml
- type: ErrorCatalog
url: errors/momo-error-codes.yml
- type: DeclineCodes
url: errors/momo-decline-codes.yml
- type: Webhooks
url: asyncapi/momo-webhooks.yml
- type: Sandbox
url: sandbox/momo-sandbox.yml
- type: CLI
url: cli/momo-cli.yml
- type: Components
url: components/momo-components.yml
- type: DataModel
url: data-model/momo-data-model.yml
- type: ChangeLog
url: changelog/momo-changelog.yml
- type: Lifecycle
url: lifecycle/momo-lifecycle.yml
- type: Conformance
url: conformance/momo-conformance.yml
- type: Compliance
url: conformance/momo-conformance.yml
- type: Plans
url: plans/momo-plans-pricing.yml
- type: RateLimits
url: rate-limits/momo-rate-limits.yml
- type: LLMsTxt
url: llms/momo-llms.txt
x-enrichment:
date: '2026-08-26'
status: enriched
artifacts_added: 35
pass: local-v1
MoMo API — frequently asked questions
Does MoMo have an API?
Yes. APIs.io lists 4 APIs from MoMo, including MoMo All-in-One Payment Gateway (AIO v2), MoMo Business Page OpenAPI and MoMo Voucher Distribution API, and 1 more.
How do I authenticate with the MoMo API?
MoMo uses bearer-token authentication (7 schemes). The details are profiled on APIs.io as Momo Authentication.
Is the MoMo API ready for AI agents?
MoMo has a Kin Score of 47.4 out of 100 (developing) and an Agent Readiness score of 28.4 (agent-aware), scored by API Evangelist on 2026-11-02.
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: