Skip to main content

Product Review Checklist

1. STANDARD FUNCTIONS FOR MINI APP​

1.1 Toolkit Implementation​

Implement the toolkit header and bottom drawer for your app. For more information, refer to our More Icon & Bottom Menu capabilities. Sample rejection cases include but are not limited to:

  • Do not use default header icons (More, Close) provided by MoMo.
  • Do not use navigation correctly based on MoMo’s guideline (to be updated).
  • Do not provide customer support information. For an access guide, refer to our Customer Support Info capability.

1.2 User Authentication​

Automatically authenticate users and save user information using PartnerUserID provided by MoMo. For more information, refer to our guideline (to be updated).

1.3 User Data Sharing​

Request data permissions that you want to use in Mini App while using the User Data Sharing capability. For more information, refer to our User Data Sharing capability. Sample rejection cases include but are not limited to:

  • Deny access to Mini App in case users refuse to share requested information.
  • Repeatedly request the same information on different screens.
  • Continue to collect and use user information after the user turns off the permission for requested information.
  • Do not use requested information to support users in using Mini App. For example: requesting location but do not use it in any scenario (suggest nearby stores, auto input location, etc.)

1.4 Payment Integration​

1.4.1 If your app has Payment capability, make sure the payment process works. For more information, refer to the Payment integration process. Sample rejection cases include but are not limited to:

  • Using other payment methods other than MoMo.
  • When clicking on the accept payment button, the transaction does not perform or fail.
  • The amount of the transaction is different from the displayed price of the product.
  • Do not redirect to Mini App to show transaction details after completing the payment.

1.4.2 Follow our Branding Guidelines when using or displaying MoMo’s products (logo, icon, trademark). Sample rejection cases include but are not limited to:

  • Use the old or event logo.
  • Change logo appearance: rotate, distort, transparent icon, color or tone, etc.

2. BASIC USER EXPERIENCE​

2.1 App Performance​

2.1.1 The submitted Mini App must be the final version that can be opened and run normally. Sample rejection cases include but are not limited to:

  • Any Mini App that crashes or causes the MoMo App to crash will be rejected.
  • Any Mini App with major bugs (inability to load, return to the previous pages and exit, serious stutter, freeze, etc.) will be rejected.
  • All interactable components does not respond with an action or warning when an error occurs.
  • Showing white screens with no components.

2.1.2 Make sure the data is loaded successfully. Sample rejection cases include but are not limited to:

  • The screen is limited and cannot be loaded.
  • The server does not respond and the screen is stuck at “Loading.”
  • No data to be loaded.

2.2 App Content​

Avoid showing irrelevant products or services data. Sample rejection cases include but are not limited to:

  • Products and services screens show code or data only used for development purposes.
  • Buttons or call-to-actions have their actions mismatched with UI texts.
  • The error message does not reflect the error of the app correctly.

2.3 App Security​

Make sure all user data is cleared in the Mini App when the user logs out.

3. MINI APP TESTING​

3.1 App Requirements​

All Main flow of product should work correctly before submitting the rollout request. Sample rejection cases include but are not limited to:

  • If there are no products in the applet, or all products are sold out, the audit cannot verify the purchase process.
  • The address needs to be filled in when purchasing goods, but there is no relevant entry on the page.
  • There is no submit button after filling in the content.
  • Cancel and Refund functions are working incorrectly.

3.2 Rollout Request Requirements​

During submitting a rollout request, provide necessary test data in the rollout request form. Sample data to provide for a rollout include but are not limited to:

  • Test account: login number/name, login password.
  • Data related to promotion campaigns: voucher, code, etc.
  • Sample products that are only used for testing.
  • In case the app needs offline interactions, provide a digital test subject or a screen recording showing successful interaction. Some cases that need offline interaction are: scanning QR codes, purchasing a product from a vending machine, interacting with an unmanned cashier shop, etc.

3.3 Documentation Requirements​

Provide documents related to Mini App when requested. Sample documents include but are not limited to:

  • Payment flow (diagram, videos).
  • Operation flow.

3.4 App Update Requirements​

During request rollout for a new app update, the Rollout Description must include:

  • The errors have been resolved for the current version (if existed).
  • Listing changes compared to previous versions.
  • Special requirements need to be noted for MoMo Tester (developer support time, server problem, etc.)
ON THIS PAGE