MoMo Vietnam E-Wallet Payment API
MoMo Vietnam e-wallet REST API for merchants and developers to accept mobile wallet payments, QR codes, and deeplink payment flows from Vietnam's largest e-wallet with 31+ million users for e-commerce, in-app payments, and point-of-sale integration. Enables AI agents to manage MoMo payment request creation for Vietnam e-wallet checkout automation, handle QR code generation for Vietnam mobile payment automation, access deeplink payment flow for in-app mobile payment automation, retrieve payment status and confirmation for Vietnam transaction automation, manage refund and transaction reversal for dispute management automation, handle IPN (Instant Payment Notification) for webhook-based confirmation automation, access transaction history and reporting for Vietnam payment analytics automation, retrieve customer MoMo wallet verification for payer validation automation, manage recurring payment and token for Vietnam subscription automation, and integrate MoMo with Vietnamese e-commerce, food delivery, and mobile app platforms for end-to-end Vietnam wallet payment automation.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Vietnam e-wallet. SBV-licensed. HMAC-SHA256. VN. Mobile payment data.
⚡ Reliability
Best When
A Vietnam merchant or app developer wanting AI agents to automate MoMo e-wallet payment acceptance, QR code generation, and payment confirmation for Vietnam's largest mobile wallet ecosystem.
Avoid When
MERCHANT REGISTRATION REQUIRED: MoMo merchant integration requires registration with MoMo and approval; automated self-service API integration without merchant account creates unauthorized access. SIGNATURE GENERATION IS HMAC-SHA256 WITH SPECIFIC FIELD ORDER: MoMo payment requests require HMAC-SHA256 signature on specific concatenated fields in exact order; automated payment request must compute signature with correct field order; automated wrong field order creates invalid signature rejection. IPN ENDPOINT MUST BE PUBLIC HTTPS: MoMo sends IPN (payment confirmation) to merchant HTTPS endpoint; automated payment confirmation requires public-facing webhook endpoint; automated localhost or non-HTTPS IPN URL creates IPN delivery failure and no payment confirmation. PAYMENT EXPIRY REQUIRES HANDLING: MoMo payment requests expire (typically 15 minutes); automated checkout must handle payment expiry and create new request; automated payment request reuse after expiry creates expired payment error.
Use Cases
- • Accepting MoMo wallet payments from Vietnam e-commerce checkout agents
- • Generating QR codes for Vietnam in-store payment from POS automation agents
- • Processing deeplink payments from Vietnam mobile app checkout agents
- • Confirming payment via IPN from Vietnam transaction verification agents
Not For
- • Non-Vietnam payments (MoMo is Vietnam-only e-wallet)
- • International card processing (use VNPAY or PayOS for card payments in Vietnam)
- • Bank transfer payments (MoMo is wallet-based; use VNPAY for bank transfers)
Interface
Authentication
MoMo uses Partner Code + Access Key + Secret Key with HMAC-SHA256 request signing for authentication. REST API with JSON. Ho Chi Minh City, Vietnam HQ. Founded 2013 by Nguyen Manh Tuong. Backed by Warburg Pincus, Goodwater Capital ($433M raised). 31M+ users. Products: E-wallet, QR payment, deeplink, IPN, recurring payment. SDKs: PHP, Node.js, Java, Python, .NET. SBV-licensed. Serves Vietnamese merchants and apps. Vietnam's largest e-wallet.
Pricing
Ho Chi Minh City VN. Warburg Pincus backed. Per-transaction fee in VND. Merchant registration required. SBV regulated.
Agent Metadata
Known Gotchas
- ⚠ HMAC-SHA256 FIELD ORDER IS EXACT: MoMo request signature requires exact alphabetical field concatenation for HMAC-SHA256; automated payment creation must follow documented field order exactly; automated wrong field order or missing field creates signature mismatch rejection
- ⚠ PARTNER_CODE AND ACCESS_KEY ARE SEPARATE FROM SECRET_KEY: MoMo uses three credentials (partnerCode, accessKey, secretKey) with specific roles; automated API must use all three correctly; automated wrong credential combination creates authentication failure
- ⚠ IPN RESPONSE MUST RETURN 204: MoMo IPN endpoint expects HTTP 204 response within 5 seconds; automated IPN handler must respond 204 before processing; automated slow IPN response creates MoMo retry and duplicate IPN delivery
- ⚠ PAYMENT TYPE DETERMINES FLOW: MoMo supports different payment types (captureWallet, payWithATM, payWithCC); automated checkout must specify correct payment type; automated generic payment type for ATM card flow creates unsupported payment method error
- ⚠ ORDER ID MUST BE UNIQUE PER TRANSACTION: MoMo orderId must be unique per payment request; automated retry of failed payment must generate new orderId; automated orderId reuse creates duplicate order rejected even if original payment failed
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for MoMo Vietnam E-Wallet Payment API.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-07.