How to Pass LINE MINI App Verification Review: Submission Checklist and Common Rejection Reasons
To pass LINE MINI App verification review, submit a channel whose provider name, service provider, and privacy-policy company are the same legal entity, attach publicly accessible privacy-policy and terms-of-use URLs, prepare test scenarios for every reservation, payment, or order flow the reviewer must complete, and confirm the service avoids the prohibited industries and content listed in the LINE MINI App Policy. LY Corporation normally completes the review in about one to two weeks; a rejected submission requires changes and another review cycle, and applicants cannot specify a completion date.
Key takeaways
- Verification is the only path to production service messages, Custom Path, home-screen shortcuts, Common Profile Quick-fill, channel-consent simplification, and the branded header with a verified badge.
- The most common rejection is a mismatch between the provider name, the service provider name, and the company named in the privacy policy — all three must reference the same legal entity.
- Prohibited industries (gambling, lending, tobacco, dating, fundraising, and others) and prohibited content (infringement, misleading comparison, spam) are hard policy gates, not styling issues.
- Review takes about one to two weeks with no expedite option; a production Endpoint URL change after submission can trigger another review, so freeze the endpoint first.
- If your real need is to receive ordinary LINE customer messages, that is a separate inbound architecture decision, not a verification step.
What verification review actually checks
A LINE MINI App channel begins as unverified. On the internal Developing channel you can test features and iterate. Moving a Published channel from unverified to verified requires submitting the channel to LY Corporation for review, and the review evaluates identity consistency, policy compliance, and whether a reviewer can actually complete the core flows — not just whether the app launches.
Verification should not be confused with two adjacent decisions. First, it is different from a Verified LINE Official Account, which is a separate product with its own review path; if that is what you need, start with the LINE country and Official Account options guide. Second, verification answers “can this MINI App use production-only features,” whereas the unverified restrictions guide answers “what can I ship before review” — a different question.
Submission checklist: information and materials
Gather the following before opening the Review request tab in the LINE Developers Console. The official submission guide is the source for these requirements.
| Item | What to prepare | Why review cares |
|---|---|---|
| Provider name | The legal entity name, matching the service provider | Reviewed against the privacy-policy company for consistency |
| Service provider name | The organization actually operating the service | Must be the same entity as the provider and policy holder |
| Channel description | A clear statement of what the MINI App does | Reviewers use it to scope the test pass |
| Privacy policy URL | Publicly accessible page whose stated company matches the provider | A mismatch here is the single most common rejection |
| Terms-of-use URL | Publicly accessible page covering the service | Required for policy compliance |
| Callback / Endpoint URL | Production endpoint, frozen before submission | A post-review change can trigger another review |
| Reference materials | Test accounts, sample products, store or reservation scenarios, and Basic Auth credentials if enabled | Lets the reviewer complete every flow without guessing |
| API scopes | Only the permissions the service actually uses | Over-broad scopes are flagged against stated purpose |
| Official Account linkage | Connected only if the MINI App relies on it | Reviewed for consistency with the MINI App flow |
For service messages specifically, you also need approved templates that confirm or respond to a user action in the MINI App. Prepare those with the service-message template review checklist before submitting, because production service messages require both a verified channel and reviewed templates.
Common rejection reasons
Most rejections fall into four groups. LY Corporation is not obligated to explain a review result in detail, so preventing these before submission is far cheaper than appealing after a rejection.
1. Identity inconsistency (the leading cause). The provider name, service provider name, and the company named in the privacy policy must be the same legal entity. A common failure is a privacy policy written for a parent company or a brand name while the provider channel is registered under a subsidiary or a trading name. Align all three before requesting review.
2. Prohibited industries. The LINE MINI App Policy bars certain categories entirely, including religious organizations, nightclubs, gambling, dating and matchmaking, lending, fundraising, multi-level marketing, tobacco and e-cigarettes, weapons and poisons, and clinical trials. A service in one of these categories cannot pass review regardless of build quality.
3. Prohibited content. Even within an allowed industry, content can trigger rejection: intellectual-property infringement, misleading or aggressive marketing, spam, violence or sexual expression, and unfair comparison or ranking against other companies’ products. Service-message copy that drifts into promotion — coupons, new-product notices, rewards, or general event announcements — is also rejected, because service messages must confirm or respond to a user action.
4. Technical and documentation gaps. These are not feature bugs. The frequent ones are a production Endpoint URL that changed after the last review, screen transitions or copy that do not match the submitted description, missing test credentials when Basic Auth is enabled, and API scopes that exceed the stated purpose. Each forces a resubmission.
Review timeline and status
LINE states the review normally takes approximately one to two weeks. There is no expedite option and applicants cannot specify a completion date. Review status is visible in the LINE Developers Console, and a rejected submission requires you to fix the cited issue and request review again, which adds another cycle.
The practical implication is schedule risk. If a seasonal campaign or launch depends on verified-only features, submit with enough buffer for one re-review. Freezing the production endpoint and finalizing the privacy-policy and terms-of-use copy before the first submission is the highest-leverage way to avoid losing a week to a preventable rejection.
Do you need verification at all?
Verification is worth requesting only when a production-only feature is on the critical path. The official custom-features matrix lists what unverified Published channels can already do — including custom action buttons, Official Account friend prompts, and region-supported payment integration — so those alone do not justify review.
Use verification when you need at least one of:
- Production service messages tied to reservations, orders, or other in-app actions.
- A recognizable Custom Path such as
miniapp.line.me/#/<your-brand>. - Home-screen shortcuts, Common Profile Quick-fill, or channel-consent simplification.
- A branded header showing the MINI App name with a verified badge, or discovery through LINE Home and search.
If none of those apply, shipping the core flow as an unverified Published channel and revisiting verification later is a legitimate sequencing choice, not a failure.
Where UnifyPort fits
UnifyPort does not verify a LINE MINI App, submit it for review, approve service-message templates, or grant any LINE platform privilege. Use the official review path above whenever verification is required.
UnifyPort fits a different, independent requirement: receiving ordinary customer messages from a connected LINE account and routing them into your own support system while the MINI App review is pending or afterward. LINE authorization uses a QR-code login, and the QR URL and PIN arrive asynchronously through account authorization events rather than in the synchronous response. Once connected, inbound text messages arrive in the standard message.received envelope with id, type, provider, account_id, occurred_at, and data.
If the webhook endpoint has a signing_secret, each delivery is signed with X-Device-Timestamp and X-Device-Signature. The signature is a hex-encoded HMAC-SHA256 over the raw request body in the form "<X-Device-Timestamp>" + "." + "<raw body>", and your receiver must verify it against the raw body before storing or routing the event. Supported replies use the normal POST /v1/messages path. The webhook delivery and signature guide describes this verification step in detail.
This split keeps two decisions honest: choose verified MINI App status for official identity, discovery, and transactional service messages; choose an inbound messaging layer separately when the operational need is to receive and route free-form LINE customer conversations. The two are not substitutes — verification does not deliver customer messages, and an inbound webhook does not unlock MINI App features.
Limitations and trade-offs
The official verified route is the better fit whenever the MINI App itself owns reservations, orders, membership, or other actions that need approved transactional notifications, or when discovery through LINE and a branded header matter to adoption.
An unofficial interface cannot grant any LINE platform privilege. It does not turn ordinary account messages into MINI App service messages, and it does not affect template review, Custom Path eligibility, or the verified badge. Its role is narrower: connect an account, deliver supported inbound messages with a verifiable signature, and expose supported replies through a standard API. Keep the MINI App product and the customer-message pipeline as separate systems unless your application deliberately joins them with shared customer or order identifiers.
FAQ
How long does LINE MINI App verification review take?
LINE states the review normally takes approximately one to two weeks. There is no expedite option, applicants cannot specify a completion date, and a rejected submission requires fixes and another review cycle.
Why do LINE MINI Apps get rejected?
The most common reason is a mismatch between the provider name, service provider name, and the company in the privacy policy. Other frequent causes are prohibited industries or content, promotional service-message copy, a production Endpoint URL changed after submission, and missing test credentials or inconsistent screen transitions.
Can an unverified LINE MINI App be published?
In supported markets, permitted customers can publish unverified MINI Apps and validate the core flow before committing to verification. Verified status is still required for production service messages, Custom Path, home-screen shortcuts, and related features. The unverified restrictions guide covers the full capability comparison.
Do I need verification to receive LINE customer messages?
No. Receiving ordinary LINE customer messages is a separate inbound architecture decision from MINI App verification. An inbound webhook delivers supported messages from a connected account; it does not unlock MINI App features.
Does verification approve my service-message templates?
Verification makes a channel eligible to send production service messages, but each template still requires its own review. Prepare templates with an action-linked use case, valid variables, and permanent links before submitting both reviews.
Next step
If your requirement is ordinary LINE customer-message intake rather than MINI App verification, start with the LINE authorization guide to understand the QR-login flow, then confirm the send and receive boundary in the provider capability matrix before designing your support workflow.
Sources
Official LINE sources checked on 2026-08-03: