Non-game launch guide

These are the standards that apply commonly to mini apps and the feature-specific release guide. Before release, be sure to review the content and follow the guide.

If the checklist below is not followed or dark patterns are found, review approval will not be granted, and even if they are found after release, service exposure may be restricted or suspended.

Please note

The items in the release guide below are continuously being updated.

Access and in-app features

• The mini app opens normally.
• All service features introduced as 'in-app features' can also be used in the mini app in the same way.
• The scheme registered under 'in-app features' connects normally.
• After entering via the app scheme, the back button works normally.

Navigation bar

• You are using the Apps in Toss navigation bar.
• If the back button is displayed, it works properly on all screens.
• If the app name and logo are shown in the navigation bar, use the brand logo and mini app name (in Korean) registered in App Info.
• If the home button is shown, it works properly. (Optional)
• Only up to one mini-app feature button is displayed. (Optional)
• The Toss navigation bar back button and the mini app's self-implemented back button are not visible at the same time.
• The Toss common features (report, share, etc.) are properly provided from the more button (⋯).
• The close button and back button are displayed, and their behavior is clear.
• If you press back on the initial screen, the mini app exits.

User identifier key issuance

• The user identifier value is checked and stored, and the mini app starts normally.
• The user's mini app usage history is retained.
• Even if you exit the mini app and re-enter it, the required data is retained.

Security and stability

• Features that run code received from outside cannot be used. (e.g.: eval etc.)
• Methods that manipulate browser history to move to your own site cannot be used. (e.g.: window.location.replace etc.)
• Server-side rendering (SSR) cannot be used. Only client-side rendering (CSR) or static site generation (SSG) methods can be used.
• If using WebSocket, use only encrypted wss:// connections. (e.g.: Firebase Firestore, Supabase Realtime, etc.)
• For API communication, use only encrypted HTTPS connections.
• Sensitive information such as user login information and payment histories (Toss Pay, in-app purchases) must be encrypted and stored in the DB.
• We recommend encrypting when transmitting personal information from the client to your own server.

Service usage behavior

• When the Android system back button is pressed, it goes back or the mini app exits.
• Except when absolutely necessary, such as maps, gesture-based zoom in/out is disabled.
• The mini app theme is implemented in light mode.
• All UI components work as intended.
• Interaction responses such as scrolling, touch, and screen transitions are not delayed by 2 seconds or more.
• Even if you exit the mini app and come back in, required data is retained.
• External links that are essential for using the service open normally.
• In the share feature intoss-private:// without using links intoss:// use the scheme.
• No profanity, slang, or excessive trendy expressions are included in the mini app text.
• No illegal content such as unlawful or sexually explicit content is included.
• For device permissions such as location and notifications, get user consent first.
• Even if the user does not grant permission, the remaining features continue to work normally.
• Network usage does not spike abnormally.
• Memory usage does not spike abnormally.

UX

• A bottom sheet does not automatically open as soon as you enter the mini app.
• The user's actions are not forcibly guided into a bottom sheet when switching to certain screens.
• On every screen, there is a clear way for the user to exit the mini app.
• Looking at the CTA button, you can predict what action will happen next.
• Do not guide users to move to your own service or install your own app through links or components.
• In-app ads are not shown on temporary screens such as intro/loading/cut scenes/pop-up modals.
• Do not mislead or force users to click in-app ads.

Toss Login

• If using Toss Login, provide a service description on the intro page so users can understand what the service is.
• The URL of the Toss Login terms screen you set appears normally.
• If you disconnect login linkage in the Toss app and then access the mini app again, the terms screen requesting login again is shown.
• If you disconnect login linkage in the Toss app, user data does not remain in the mini app.
• Do not provide your own login or other login methods instead of Toss Login.

In-app purchases

• When processing an in-app purchase, music playing in the mini app is paused.
• The in-app purchase order amount matches the amount shown in the Google or Apple payment window.
• In-app purchases proceed normally. Also check in the Google payment test environment.
• After the in-app purchase is completed and you return to the mini app, the payment result is reflected properly.
• If you choose Cancel in the in-app purchase window, you return to the order screen.
• If payment fails due to insufficient balance, etc., the user can understand the reason for failure.
• In-app purchase cancellation is processed normally.
• Users can check the payment history for in-app purchase products.
• Even if you change the device logged into the Toss app, previously purchased in-app purchase data (such as passes) is retained.

Toss Pay

• When you process Toss Pay simple payment, music playing in the mini app is paused.
• The order amount matches the amount shown in the Toss Pay payment window.
• If Toss Pay payment fails, an error message is displayed and the user can understand the reason for the failure.
• If you choose Cancel immediately before Toss Pay payment, you return to the previous screen.
• Do not provide any payment methods other than Toss Pay.
• If you choose Cancel in the Toss Pay payment window, you move to the order screen.

In-app ads

• When an in-app ad plays, music playing in the mini app is paused.
• Comply with the Toss Ads SSP policy. (#)
• Real in-app ads, not test ads, are displayed properly, and there is no abrupt ending or crashing.
• Do not show in-app ads at moments users would not expect.
• In-app ads are displayed properly, and there is no abrupt ending or crashing.
• In-app ads are preloaded. They are not loaded in real time at the moment they are played.
• When the in-app ad ends, it returns to the mini app screen normally.
• After the in-app ad ends, mini app music plays again.
• If the user watches the reward ad to the end, the reward is granted properly.
• Banner ads are displayed in appropriate positions. (top/middle/bottom)
• Banner ads are displayed only on scrollable screens.

Share reward

• The configured share reward screen is displayed normally.
• When the share reward screen is closed, it returns to the mini app screen normally.
• When the friend invitation is completed, the reward is granted properly.