Mini apps overview

Mini apps embed your web experience inside the mMoney wallet. The user browses your products in a WebView. mMoney handles identity and payment. You ship the order.

What you receive from mMoney

Item	Where you use it
Mini-app ID and slug	The slug is the JWT aud claim and part of your launch URL.
Launch-token signing secret	Per-app HS256 secret. Verifies the JWT the wallet passes to you.
API key (x-api-key)	Scoped to invoice creation for this mini app only.
Webhook signing secret	HMAC secret for invoice.paid webhooks.
Entry URL and allowed origins	The wallet opens the entry URL and blocks navigation outside the origins.

Each secret shows exactly once in the merchant dashboard. mMoney keeps no recoverable copy. Store secrets in your secret manager at once.

mMoney never exposes real wallet identifiers. You see each user as a pseudonymous ID. Different mini apps see different pseudonyms for the same user.

Lifecycle

Status	Who moves it	Meaning
draft	You	Editable manifest. Not visible in the wallet.
review	You submit; mMoney approves	Manifest locked except during draft.
active	mMoney	Live in the wallet.
disabled	mMoney	Removed from the wallet. History kept.

Manage your mini apps on Dashboard → Mini Apps. You can build and test against a draft or review mini app.

The flow

1. The user taps your mini app in the wallet.
2. The wallet opens your entry URL with ?mm_launch_token=<jwt>.
3. Your backend verifies the JWT. See Verify the launch token.
4. The user shops. Your backend creates an invoice.
5. Your page calls MMoneyMiniApp.requestPayment(...). See Payments.
6. The wallet collects PIN or biometric and pays.
7. mMoney sends a signed invoice.paid webhook to your server.

App Store policy

Apple and Google require their own purchase rails for digital goods inside an app. Use mini apps for physical goods, real-world services, bill payment, top-ups, and transport. Talk to your mMoney contact before you sell anything digital.