Mini Apps

Appearance

Submit your MiniApp ​

To get your Mini App listed in MiniPay's Discover page, submit it using our submission form.

Submission Form ​

Submit your Mini App

Listing fields ​

When you submit, you will be asked for the following. Prepare these before filling the form:

FieldDescription
App nameClear, descriptive name for your Mini App.
TaglineBrief description (1–2 sentences).
PublisherYour name or organization.
Support URLIn-app support link (visible inside the Mini App). Ideally Telegram, WhatsApp, email, or a web support portal.
Terms of ServiceAccessible link within the app to your Terms of Service.
Privacy PolicyAccessible link within the app to your Privacy Policy.
CategoryOne of: games, social, finance, utility, productivity, health-fitness, news-media, music, shopping, education, developer-tools, entertainment, art-creativity, rewards, sports.
App URL (linkUrl)The HTTPS URL where your Mini App is hosted. Must be publicly accessible over HTTPS.
IconHigh-quality icon (recommended: 512×512px).

There is no manifest or config file in your repo—listing is done only through this submission process.

Submission requirements ​

Before submitting, ensure your Mini App meets these requirements:

Technical requirements ​

  • ✅ Auto-connects to wallet - No connect button, connection happens automatically
  • ✅ HTTPS enabled - Your app must be served over HTTPS
  • ✅ Mobile-optimized - Responsive design that works on mobile devices (minimum viewport 360×640; see UI & container)
  • ✅ Works on Celo networks - Supports Celo Mainnet and/or Celo Sepolia testnet
  • ✅ Error handling - Graceful error handling for wallet operations
  • ✅ Performance - Provide a PageSpeed Insights score for your production URL. High performance is a prerequisite for listing.
  • ✅ Network manifest - Provide a full manifest of all URLs, subdomains, and origins your app uses (including external links for JS, CSS, and APIs).

Content requirements ​

Use the listing fields above as a checklist. Ensure your app name, tagline, icon, category, support URL, and publisher are accurate and complete.

  • Clear ownership - Your app must clearly display its name and logo. It must be obvious to the user that the service is operated by your entity and not by MiniPay.
  • Terms of Service and Privacy Policy - Provide accessible in-app links to your Terms of Service and Privacy Policy.

Dependency security ​

To reduce exposure to npm supply chain attacks (compromised or malicious package versions that are typically yanked within days of being published), pin a minimum published age for all npm dependencies.

  • Pin exact versions — Use exact versions in package.json (e.g. "viem": "2.21.0"), not ranges (^2.21.0, ~2.21.0, *). Ranges let a fresh malicious release slip in on the next install, even with a lockfile if it's regenerated.
  • Minimum published age — Require at least 7 days before a newly published version may be installed. Prefer a longer window (e.g. 14 or 30 days) if your release cadence allows.
  • How to enforce — Configure your package manager so installs reject versions younger than the threshold:
    • npm (v11+) — set minimumReleaseAge in .npmrc (e.g. minimum-release-age=10080 for 7 days, in minutes).
    • pnpm (v10.16+) — set minimumReleaseAge: 10080 in pnpm-workspace.yaml or .npmrc.
    • Bun — pass --minimum-release-age=604800 (in seconds) or set it in bunfig.toml.
  • Ignore install scripts — Set ignore-scripts=true in .npmrc so postinstall scripts from dependencies cannot run automatically.
  • Lockfile — Commit your lockfile and use npm ci / pnpm install --frozen-lockfile / bun install --frozen-lockfile in CI so installs are reproducible and cannot silently pull a newer version.

Smart contracts (if your app uses them) ​

  • Contract verification - All contract source code must be published and verified on Celoscan.
  • Sample transactions - Provide links to sample transactions for every user-facing contract method. See Interacting with smart contracts for guidance.

Support and SLA ​

  • Dedicated support - Provide an in-app support link (see listing fields); ideally Telegram, WhatsApp, email, or a web support portal.
  • Critical issues - You must fix reported critical issues within 24 hours, or the listing may be temporarily disabled.

Best practices ​

  • Test thoroughly - Test your app in MiniPay's Developer Mode before submitting
  • Clear value proposition - Users should understand what your app does immediately
  • Fast loading - Optimize for quick load times
  • User-friendly - Intuitive interface and clear error messages

What Happens After Submission ​

  1. Review Process - Our team reviews your submission
  2. Testing - We test your app in MiniPay
  3. Feedback - If needed, we'll provide feedback for improvements
  4. Approval - Once approved, your app will be listed in MiniPay's Discover page

Common Rejection Reasons ​

  • App doesn't auto-connect to wallet
  • App not served over HTTPS
  • Poor mobile experience
  • Missing error handling
  • App doesn't work on Celo networks
  • Incomplete or unclear submission information

Tips for Successful Submission ​

  1. Follow guidelines - Read and follow all documentation guidelines
  2. Test in MiniPay - Use Developer Mode to test your app thoroughly
  3. Provide clear information - Fill out all submission fields completely
  4. Include support - Provide a support URL or contact information
  5. Polish your app - Ensure it's production-ready before submitting

Need Help? ​

If you have questions about the submission process or need help with your Mini App: