corecode:~$cd ./solutions/apps-in-toss
Apps in Toss development ? Toss mini app outsourcing ? A team that plans for review first
For mini apps and games that run inside Toss, review is harder than building features. We turn rejection history into a checklist, fix issues before review, and release together with web, Android, and iOS using the same code.
If this sounds familiar
- You want to launch on Apps in Toss, but cannot find documentation that brings together the SDK, console, and review criteria, so you do not know where to start
- Your app was rejected for reasons unrelated to its features, such as terms consent, payment products, or back navigation
- Building separately for Toss would split the code from your existing app and double the maintenance work
What we build
Toss in-app games ? Game portals
We launched a portal on Toss that brings together 12 mini games with a single coin currency. We implement Toss automatic login, ads, in-app purchases, and back navigation according to Toss specifications.
Non-game mini apps (content ? Commerce ? Utilities)
We submitted the financial information service Briefin for review with Apps in Toss as its first channel. We screen out features that can cause review issues, such as crossing into discretionary investment, during design.
Review checklist
Before submitting for review, we check all code against a checklist compiled from 8 rejections. Terms consent gates, payment product policies, displayed amounts, back navigation, and Toss mode UI are recurring items.
1 codebase, 4 platforms
We build for web, Android, iOS, and Toss from a single monorepo. A single platform switch separates Toss-specific code paths, so new features reach all 4 platforms at once.
What we have built
We only list projects that have been launched on Toss or gone through review.
How we work
- 1
Assessment (1 week)
We review your existing app and plans, then first list in a table any issues with Toss policies on ads, payments, authentication, and the boundaries of financial features.
- 2
Design (1 week)
We design the Toss SDK integration points (login, payments, ads, and back navigation) and platform-specific code paths. We finalize the review checklist at this stage.
- 3
Build (3?5 weeks)
We validate on physical devices and in the Toss sandbox. Before submitting for review, we run through the entire checklist once more.
- 4
Review ? Operations
We automate review packaging (build ? upload ? submission) so that we can resubmit within half a day after a rejection. After launch, we review console metrics together.
Scope and timeline
6 weeks is the baseline for 1 mini game or a single-feature mini app. Pricing depends on the number of games and the scope of payment and ad integrations, so we define the scope first in a 30-minute consultation.
Frequently asked questions
What does the Apps in Toss review check?
It focuses on policies more than features. Common reasons for rejection include the terms consent flow, how in-app purchase products are registered (Toss does not support subscription products), displayed amounts, back navigation behavior, ad policies, and whether financial features cross into discretionary investment.
Can you bring an existing app to Toss?
Yes. If it is web-based, we add platform-specific code paths and release using the same code. We build our game portal for web, Android, iOS, and Toss from one codebase.
How do in-app purchases and ads work?
We integrate the Toss in-app purchase and in-app advertising SDKs. Since Toss does not support subscriptions, we design time-limited passes as consumable products. Ad removal products work the same way.
What happens if the app is rejected?
We add the rejection reasons to the checklist, fix the issues, and resubmit. Packaging is automated, so resubmission itself takes half a day. Our current checklist started with a history of 8 rejections.
How long does it take?
The baseline for 1 mini game or a single-feature mini app is 6 weeks (1 week for assessment, 1 week for design, and 3?5 weeks for the build). The review period depends on the Toss schedule.
Just send us your project brief or existing app URL
We will list the items that conflict with Toss policies in a table and show you during the consultation.