Guide July 15, 2026

Can Unverified LINE MINI Apps Send Service Messages? 2026 Limits and Review Checklist

No. An unverified LINE MINI App can test service messages on its internal Developing channel, but it cannot send them from the Published channel to production users. Production service messages require a verified LINE MINI App and approved templates. Verification also unlocks Custom Path, home-screen shortcuts, Common Profile Quick-fill, and branded header display; an unverified app can still validate its core web flow before review.

Key takeaways

Service messages are a verified-only production feature. Unverified apps can test them with channel administrators or testers, not real users on the Published channel.
A service message must confirm or respond to a user action in the MINI App. It is not a general support chat, promotion, or broadcast channel.
Taiwan and Thailand allow permitted customers to publish unverified MINI Apps, but verification review there requires a channel under a certified provider.
LINE says verification normally takes about one to two weeks; rejected submissions and re-review add time.
If your actual requirement is to receive ordinary LINE customer messages, decide that architecture separately from MINI App verification.

LINE MINI App verified vs unverified restrictions

Every new LINE MINI App channel begins as unverified. The official custom-features matrix draws a clear line between features you can ship before review and features that require verified status.

Capability	Unverified Published channel	Verified Published channel	What it means for the decision
Service messages	No; Developing-channel tests only	Yes, with reviewed templates	Verification is mandatory for reservation, delivery, or other post-action notifications
Custom Path	No	Yes	Verification is needed for a recognizable `miniapp.line.me` path
Home-screen shortcut	No	Yes	Use verified status if repeat access from a device home screen is part of the experience
Common Profile Quick-fill	No	Yes	Verification is required to reduce form entry with approved profile data
MINI App name and verified badge in the header	No; the domain is shown	Yes	Verification adds a stronger identity and trust surface
Add Official Account friend prompt	Yes	Yes	This alone does not justify review
Custom action button	Yes	Yes	You can validate sharing or navigation before verification
Payment-system integration	Yes, subject to regional method rules	Yes, subject to regional method rules	Verification is not a universal payment switch; specific products can have extra requirements
Ads	Yes, where the regional product is available	Yes	Availability still depends on LINE’s regional rules

Do not confuse a verified LINE MINI App with a Verified LINE Official Account. They are different products with different review paths. If the Official Account question is what brought you here, start with the LINE country and Official Account options guide instead.

Can an unverified LINE MINI App send service messages in production?

No. LINE’s service-message documentation says an unverified MINI App may prepare and test the feature on its internal Developing channel, but it cannot use the feature on the Published channel. A verified MINI App still needs service-message templates that pass LY Corporation’s review.

The content rules are narrower than normal chat messaging:

A message must confirm or respond to an action the user took in the MINI App.
Allowed examples include reservation confirmation, an order-shipment result, or a reminder tied to the original action.
Advertising, coupons, new-product notices, rewards, and general event announcements are prohibited.
LINE permits up to five service messages for one user action, although the approved limit can vary by use case.
A channel can prepare up to 20 service-message templates, and production templates must pass review.

That makes the Service Message API useful for transactional follow-up, not for opening a free-form customer conversation. If a customer replies with a support question, the message-intake requirement should not be assumed to be solved by the MINI App notification flow.

Region and provider checks before requesting verification

On March 11, 2026, LINE opened unverified MINI App publication in Taiwan and Thailand to customers permitted by the LINE MINI App Policy. That change makes it easier to publish and validate a service before committing to verification.

Verified status still has an additional gate in those two markets: only LINE MINI App channels under a certified provider can apply for verification review. The official submission guide links to the relevant Taiwan and Thailand provider programs.

Before choosing a path, answer these questions:

Which feature creates the verification requirement? Name it precisely: service messages, Custom Path, home-screen shortcut, Quick-fill, branded header, or LINE discovery.
Where will the service operate? Confirm the MINI App’s service region and whether a certified provider is required for review.
Can the core flow launch unverified first? Friend prompts, custom action buttons, and region-supported payment methods may be testable without verified status.
Does the launch date allow review time? LINE estimates approximately one to two weeks, but a rejection can add rework and another review cycle.
Is the notification truly tied to a user action? If the content is promotional or unrelated to a MINI App action, verification does not make it an allowed service message.

Verification review checklist

Use this checklist before opening the Review request tab in the LINE Developers Console:

Confirm the service follows the LINE MINI App Policy and the current UI, icon, safe-area, loading, custom-action-button, and performance guidelines.
Make the provider name, service provider, channel description, and privacy-policy company consistent.
Verify that the Published-channel and Review-channel LIFF URLs show the same service.
Prepare test scenarios and test credentials for reservations, payments, orders, or other flows the reviewer must complete.
Add the service-message templates you need, document each exact use case, and remove promotional copy.
Leave schedule buffer for the stated one-to-two-week review and possible re-review.
Decide how ordinary customer questions will be received and routed; do not treat transactional service messages as a support inbox.

If your project also uses LINE MINI App in-app purchase, review that approval sequence separately. The existing LINE MINI App fee and payment-webhook guide explains why payment processing and customer-message intake should remain separate systems.

Where UnifyPort fits

UnifyPort does not verify a LINE MINI App, submit service-message templates, unlock Custom Path, or provide LINE MINI App payment and consent APIs. Use LINE’s official review path whenever those features are required.

UnifyPort fits a different requirement: receiving ordinary customer messages from a connected LINE account and routing them into your own support system. LINE authorization uses a QR flow, and the QR URL and PIN arrive asynchronously through account authorization events. After connection, 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, UnifyPort signs the raw delivery with X-Device-Timestamp and X-Device-Signature. Your receiver verifies the HMAC-SHA256 signature before storing or routing the event. Supported replies use the normal POST /v1/messages path; consult the provider capability matrix before relying on a provider-specific action.

This split keeps two independent decisions honest:

Choose verified LINE MINI App status for official MINI App identity, discovery, Quick-fill, shortcuts, and transactional service messages.
Choose an inbound messaging layer when the operational need is to receive and route free-form LINE customer conversations.

For the second path, the guide to receiving LINE messages without an Official Account provides the surrounding architecture. It does not change LINE MINI App eligibility or service-message policy.

Limitations and trade-offs

The official verified route is the better fit when the MINI App itself owns reservations, orders, membership flows, or other actions that need approved transactional notifications. It is also the right route when users must discover the MINI App through LINE, trust a verified brand header, add a home-screen shortcut, or use Common Profile Quick-fill.

An unofficial interface cannot grant any of those LINE platform privileges. It also does not turn ordinary account messages into MINI App service messages. Its role is narrower: connect an account, deliver supported inbound messages, and expose supported replies through a standard API. Keep the official MINI App product and the support-message pipeline separate unless your own application deliberately joins them with shared customer or order identifiers.

FAQ

Can an unverified LINE MINI App send service messages?

Only for testing on the internal Developing channel. Production service messages from the Published channel require a verified LINE MINI App and approved service-message templates.

Can anyone publish an unverified LINE MINI App in Taiwan or Thailand?

As of March 11, 2026, customers permitted by the LINE MINI App Policy can publish unverified MINI Apps in Taiwan and Thailand. Applying for verified status there still requires a channel under a certified provider.

How long does LINE MINI App verification take?

LINE says the review normally takes approximately one to two weeks. A rejected submission can require changes and another review, and LINE does not let applicants specify a completion date.

Are service messages the same as LINE customer-support messages?

No. Service messages are approved transactional notifications tied to a user’s action in the MINI App. They cannot be used for advertising or general announcements and do not replace a free-form support inbox.

Does an unverified MINI App support payments?

LINE’s feature matrix allows payment-system integration for both unverified and verified MINI Apps, but available methods differ by region and individual payment products can add approval requirements. For example, LINE MINI App in-app purchase is a Japan-specific product with its own production conditions.

Next step

If your requirement is ordinary LINE customer-message intake rather than MINI App service messages, review the LINE authorization guide first. Then confirm the exact send and receive boundary in the provider capability matrix before designing the support workflow.

Sources

Official LINE sources checked on 2026-07-15: