Apps in Toss Review Pass Record — Turning 8 Rejections into a Checklist
A record of fixing 5 issues before review by turning 8 rejections from a financial information service into a checklist for a game portal. Terms agreement gate, 30-day pass instead of subscription, display amount, back button — it’s not features that block you, but policies.
This article documents our review experience launching two services, Briefin (financial information) and Playin (game portal), on Toss Apps in Toss. These are not Toss’s official guidelines, but the items we actually got caught on.
Problem
The first wall developers face when trying to deploy mini apps or games on Toss Apps in Toss is not technical defects, but policy rejections. We have experienced situations where features work perfectly, yet the review keeps blocking us. This is a major cause of project delays in directions developers did not anticipate.
This article analyzes the reasons for repeated rejections in Apps in Toss reviews and records the process of systematically resolving them. It is based on actual rejection histories from operating a financial information service and a game portal. We present methods to help readers reduce the same trial and error and pass quickly.
Why It’s Difficult
The first difficulty is that review criteria are not organized into clear documentation. Rejection reasons focus on policy elements not directly related to features, such as terms agreement, payment product configuration, and back button behavior. Therefore, developers face the challenge of finding policy violations rather than code errors.
Secondly, the Toss platform has a structural constraint: it does not support subscription-based product registration. If your existing business model is subscription-based, you cannot bring it over as is. This creates a burden to modify the business logic itself, such as converting to consumable items.
Thirdly, financial information services must strictly adhere to the legal boundaries of investment advisory. Features like automatic stop-loss, trading signals, and rebalancing carry high regulatory risks. Services containing these features are highly likely to be immediately rejected in reviews.
What We Did
We submitted the financial information service Briefin as the first channel for Apps in Toss review, and had to completely remove securities API integrations and dependent features due to review requests. Stop-loss alerts, trading signals, strategy settings, rebalancing, and portfolio features were rejected for crossing investment advisory boundaries. During this process, we recorded a total of 8 rejection histories to understand the policy details.
For the game portal Playin, we converted the previous 8 rejection histories into a checklist. We conducted a full code inspection before submitting for review and proactively fixed 5 issues. This increased the probability of passing the review and reduced unnecessary round-trip time.
Specific fixes included adding a gate for agreeing to 2 terms and a Toss launch splash screen. To resolve the subscription non-support issue, we changed the ad removal feature to a 30-day pass consumable. On the store screen, we prioritized displaying the displayAmount and matched the ad removal product name.
Navigation handling was also finely adjusted. We implemented a back button handler that exits the app on the home screen and calls history.back on other screens. In Toss mode, we hid the custom back button to prevent UI conflicts.
The review packaging process was automated as a skill, covering build, upload, application, and sandbox testing (game, ad, IAP). Thanks to this automation, packaging time was reduced to approximately 2–3 hours. We integrated Web, Android, iOS, and Toss into a pnpm and Turborepo monorepo, handling branching with a single platform switch.
By the Numbers
| Metric | Value | Notes |
|---|---|---|
| Rejection History | 8 | Converted to checklist |
| Proactive Fixes | 5 | Code inspection before review |
| Mini-games | 12 | Active lineup |
| Platforms | 4 | Single codebase |
| Packaging Time | 2–3 hours | Automation skill applied |
| Open Source Porting | 3 | vitest 60 · 37 · 42 passed |
What This Article Says
Apps in Toss reviews pose a greater barrier in policy compliance than feature completeness. Accumulating repeated rejection histories into a checklist is the most efficient passing strategy.
Readers, please first take the 5-question suitability diagnosis to identify where your service might get stuck tomorrow.
Further Reading
- Apps in Toss Suitability Diagnosis — 5 Questions
- Apps in Toss Solutions — Teams That Design Reviews First
- Case Study: Playin
CoreCode is a Korean development team with a legal entity in Ho Chi Minh City. We build enterprise AI, web/apps for companies entering Vietnam, and Toss Apps in Toss mini apps, delivering what operates, not just demos. Tell us your current status, and we will summarize it with numbers in a 30-minute consultation — Book a 30-minute Consultation.