Review Guidelines

The Kaia Wave team reviews the Mini Dapp demo version based on the criteria below.

Self-Checklist

Platform Support	Are both LIFF(LINE) and Web versions supported?
SDK	Is the latest version of the Mini Dapp SDK applied? Has the ProjectId been generated via Reown and the domain successfully verified?
Wallet Connect Flow	Does the LINE version follow the Wallet Connect flow below? Access Mini Dapp (LIFF) → Consent to Channel → Add Official Account → Launch Dapp → Wallet Connect (e.g. at payment or reward step) Does the Web version follow the Wallet Connect flow below? Access Mini Dapp (Web) → Wallet Connect → Launch Dapp Is the connected wallet address clearly shown to the user? Is the disconnectWallet feature available?
Payment Features	Is in-app item payment supported via the SDK? (Both Crypto and Stripe must be supported) Are purchase precautions shown before payment? Are payment status notifications (UI/UX) properly provided? Is the openPaymentHistory() feature available? Are fiat/crypto prices displayed based on real-time rates? (e.g., CMC, Kaia Open API)
LINE Integration	Are LINE Login, Messaging API channels, and a Published LIFF created via LINE Developers? Is the Official Account (OA) properly linked and aggressive set? Go to LINE Developers > LINE Login Channel > LIFF > Add friend option, and set it to On (aggressive) Is the OA Rich Menu configured according to the design guide?
Invite Friends	In the LIFF version, is ShareTargetPicker implemented for inviting friends? In the Web version, is a “copy invite link” feature available?
UX/UI	Is the language localization implemeted based on user's browser settings or IP? (English and Japanese must be supported) Is the browser tab title in the format {Mini Dapp Name} | Mini Dapp? Is OpenGraph properly set for the Mini Dapp’s URL? Does the Connect button comply with the Dapp Portal design guideline? Is a Close Confirmation Dialog provided?
Security	Never expose wallet private keys, clientSecret, or other sensitive credentials in frontend code, version control, or unsecured environments. These credentials must be securely stored on the backend or in a protected secrets management system.

Compliance

Gambling-related	Specifications that provide cash or virtual assets as rewards based on probability using items purchased through payment are not permitted. Specifications that provide gacha mechanisms that can offer substantial value based on probability using in-app currency or virtual assets are not permitted. Specifications that allow participants to receive cash rewards through prize lotteries or slot games by paying a fee are not permitted.
Violence	Games or content that contain extreme violent elements are not permitted.
Crime and Drug	Content that promotes crime, drug use, abusive behavior, or inappropriately depicts alcohol and tobacco use is not permitted.
Discrimination and Hate	Content that contains derogatory remarks or statements regarding race, gender, or sexual orientation is not permitted.
Explicitness	Any content that is sexually explicit or contains sexual depictions is not permitted.
Securities	Services that have securities are not permitted (where there is an expectation of profit, investment of assets, the invested assets are in a joint enterprise, and profits come from a third party).
Intellectual Property	Services that use intellectual property that is not owned for commercial purposes are not permitted.
Prize Contest Law	In the case of rewards that are contingent upon payment, the following criteria must be met. Paid below 1,000 YEN ; Max reward 200 YEN Paid equal to/over 1,000 YEN ; Max reward 20% of paid volume
Comprehensive regulatory compliance	Additionally, services that are generally difficult to reference based on societal norms may not be permitted depending on the review by the Dapp Portal team.