FAQs

A Mini App is a partner or merchant service that can be accessed within the MoMo ecosystem, allowing customers to discover and use services without leaving the MoMo App experience.

Merchants, partners, aggregators, and service providers may apply to onboard a Mini App, subject to MoMo business, compliance, technical, and commercial approval.

Typical onboarding information may include business registration details, identity or representative details, KYC/KYB documents, banking or settlement details, and contact information for business and technical users

Sandbox access is provided once the required onboarding and approval steps have been completed.

The requirements document states that partners receive sandbox credentials and documentation post-approval.

Yes. The requirements document states that the developer and business owner should be able to work under the same workspace or project.

Submit the following:

• Mini App build/package
• Supporting documentation
• Test evidence
• UX screens or prototype
• Integration details
• Any compliance-related information required for review

Approval depends on the completeness of the submission, compliance review, technical readiness, security review, and whether changes are required.

To avoid delays, ensure all required documents and test evidence are submitted upfront.

MoMo will provide feedback on the items that need to be corrected. The merchant or developer should update the Mini App and resubmit for review.

Yes. Mini Apps should support lifecycle management, including onboarding, managing, updating, and removing Mini Apps, as referenced in the MoMo Mini App BRS scope.

Technical documentation, platform overview, architecture guidance, sample apps, reference implementations, error handling, best practices, FAQs, troubleshooting, and UI/UX guidelines are intended to be available through the documentation hub.

Possible causes

• Account has not been approved
• Incorrect login details
• Access request is still pending
• User role has not been assigned

What to do

Check that registration has been completed and confirm that approval has been granted. Contact support if access is still unavailable.

Possible causes

• Onboarding approval is incomplete
• Required agreements are outstanding
• Compliance or business review is pending

What to do

Confirm that all required documents and agreements have been submitted. If everything has been completed, contact the support team with your business name and onboarding reference.

Possible causes

• Required test scenarios were not completed
• API integration errors occurred
• The payment flow failed
• Error handling is incomplete
• UX does not align with MoMo standards

What to do

Review the failed test results, correct the issues, retest in the sandbox, and resubmit the updated package.

Possible causes

• Error mapping is incomplete
• Backend failure message is not translated into customer-friendly language
• Timeout or network failure is not handled correctly

What to do

Update error handling so customers receive clear and actionable messages. The portal requirements recommend descriptive messages and actionable steps for failed transactions.

Possible causes

• Customer did not approve the payment
• Insufficient wallet balance
• API timeout
• Invalid transaction reference
• Integration or callback failure

What to do

Check the transaction logs, confirm API response codes, validate the payment request, and retest the approval and callback flow.

Possible causes

• Large images or assets
• Heavy scripts
• Poor network handling
• Unoptimised loading sequence

What to do

Compress images, reduce unnecessary scripts, lazy-load non-critical assets, and optimise for lower-end devices.