LINE MINI App development for bookings, orders and membership cards

What is LINE MINI App development?

LINE MINI App development is the work of building a web application that runs inside the LINE messenger and registering it with LY Corporation as a MINI App. The LINE Developers documentation describes a LINE MINI App as a web app built on HTML5 that works like a browser inside LINE, so users reach your service without installing anything.

In practice it has three parts. The front end is the screen your customer sees: a card, a menu, a calendar. The back end stores members, bookings and orders and talks to your other systems. And the channel setup in the LINE Developers Console ties the two to your company’s LINE provider, which is what lets LINE show your name, your icon and, after review, the verified badge.

For a Japanese business the appeal is simple. Most of your customers already carry LINE on their phones, and many already follow your LINE Official Account. A MINI App turns that relationship into something useful: they tap a rich menu button and their point card appears, or they book next Tuesday’s haircut without leaving the chat.

LINE MINI App development is not a replacement for everything. It shines at short, frequent tasks. Long sessions, heavy offline use or hardware features such as Bluetooth devices are still better served by a native app, which we cover further down.

LINE MINI App vs LIFF vs native app: which should you build?

Build a LINE MINI App when your customers already use LINE and the task is short and repeated; build a plain LIFF app for internal or campaign tools that do not need the verified features; build a native app only when you need deep device access or long daily sessions.

LIFF, the LINE Front-end Framework, is the SDK that both LIFF apps and MINI Apps use. A LIFF app lives on a LINE Login channel and opens inside LINE in Full, Tall or Compact size. A MINI App uses the same SDK but sits on its own channel type, can pass a verification review, and gains extra features. LY Corporation’s documentation says it plans to fold LIFF into the LINE MINI App brand and recommends creating new LIFF apps as MINI Apps, so for anything customer-facing we start on a MINI App channel.

A native app still has its place. If your customers open your service every day for long stretches, need offline access, or rely on the camera, sensors or background location beyond what a web view allows, a Flutter or React Native app published under your own store accounts is the stronger choice. Our app outsourcing guide for Japan explains that path.

Why Japanese customers use a MINI App when they would never download yours

Because asking for a download is asking for a lot. A customer at your counter has perhaps twenty seconds of patience; searching the store, waiting for an install and creating a password rarely fits in that window.

A MINI App reached from a QR code on the counter, a rich menu button or a link in a message opens in a second or two. With a verified MINI App and channel consent simplification, a first-time user can get past the permission screens quickly, and LINE supplies their display name so a membership sign-up can be a couple of taps rather than a form.

That lower friction is the whole business case for LINE MINI App development. A salon that hands out paper stamp cards loses the data on every card left in a drawer. A café with a native app sees a small group of loyal downloaders and nobody else. A MINI App reaches the much larger group of customers who will happily tap a button inside LINE but will never visit an app store for a single shop.

It also suits Japan’s habit of carrying loyalty cards for dozens of shops. Moving them into LINE, next to the chat where you already send coupons, puts your card where the customer will actually find it.

What can a LINE MINI App do for a shop, salon or clinic?

A LINE MINI App can handle any short task a customer repeats: showing a membership card, booking a slot, ordering ahead, joining a queue or checking a balance. These are the jobs we are asked to build most often.

• Digital membership card with a barcode or QR code the POS can scan
• Point and stamp cards with tiers, expiry dates and reward coupons
• Reservations for salons, clinics, gyms, studios and restaurants
• Mobile ordering and takeout with pickup time slots
• Numbered queue tickets with a notice when the customer’s turn is near
• Event or class check-in using a QR code on the member card
• Simple surveys and post-visit feedback linked to the member record
• Store finder and opening hours for chains with several branches

Pick one or two for the first release. A MINI App that does one job quickly gets used; one that tries to be a whole website inside LINE usually gets ignored. Features can be added in later releases once real usage shows what customers want. If your use case is mostly bookings, our general booking app developer page describes the scheduling logic we reuse.

Building membership and point cards in a LINE MINI App

A digital member card needs three things: a stable member ID tied to the LINE user, a code the till can scan, and a points ledger your staff can trust. Getting the ledger right matters more than the design.

When the customer first opens the MINI App, the LIFF SDK gives us their LINE user ID and profile after they consent. We create a member record in your database keyed to that ID, so the same person always sees the same card. If you already have members from a plastic-card scheme, we add a one-time linking step: the customer enters their old card number and a verification detail, and the histories merge.

The barcode shown on screen is generated from the member number in a format your POS scanner already reads, usually a standard 1D barcode or a QR code. Points are stored as individual ledger entries (earned, spent, expired, adjusted) rather than a single running total, so a disputed balance can always be traced.

If your POS can send sales to an API, points post automatically. If it cannot, staff add points on a simple tablet screen, and we can import daily CSV exports as a stopgap. Tiers, birthday rewards and expiry rules sit in settings your team can change without calling a developer. For the wider picture of loyalty mechanics, see our customer loyalty app guide.

Reservations and service messages: how does a LINE MINI App confirm a booking?

After a booking, a verified MINI App can send the customer service messages, LINE’s own notification format for confirming what the user just did. They arrive in a dedicated chat from LINE rather than from your Official Account, and they do not require the customer to follow you.

LY Corporation’s service messages documentation sets clear rules. Only verified MINI Apps can use them on a published channel. One user action gives you a notification token that allows up to five service messages, and that token stays valid for one year, so a reservation can produce a confirmation now and a reminder the day before. Messages use pre-approved templates, available in Japanese, English, Traditional Chinese, Thai, Indonesian and Korean, and each template must pass review. Advertising, discount promotions and event announcements are not allowed in them.

That shapes the booking flow we design. Confirmation, reminder, change and cancellation notices go out as service messages. Promotions go out separately through your LINE Official Account, where the customer has chosen to follow you and your plan’s message allowance applies.

On the back end, reservations need the same care as any booking system: slot capacity per staff member or table, buffer times, cut-off times for same-day bookings, and a clear rule for no-shows. We build those rules as settings, not code, so a salon manager can change them on a Sunday evening.

How does the LINE MINI App verification review work?

You submit the MINI App from the Review request tab in the LINE Developers Console, and LY Corporation reviews it; its submission guide says the review takes approximately one to two weeks. Results arrive in the console and by email.

The review checks more than code, which is why good LINE MINI App development includes the paperwork. The provider name must match the business actually offering the service, the channel description must match what the MINI App does, and the privacy policy must name the right company as the party collecting data. The published channel and the review channel must point to the same service. For MINI Apps that take reservations, payments or orders, you must supply test scenarios (test accounts, products or stores) so reviewers can walk the whole flow. In-app purchases need separate approval before the verification review.

The documentation also lists design and technical checks: icon specifications, safe areas in landscape mode, the loading icon, custom action buttons and performance guidelines. We run through that list before submission and fix what fails, because a rejection costs another cycle of waiting.

One regional note: the submission guide says that in Taiwan and Thailand only channels under a certified provider can apply. For a business based in Japan that restriction does not apply, but it matters if you plan the same MINI App for those markets later.

Verified vs unverified LINE MINI App: what changes after review?

An unverified MINI App works and can be shared, but LY Corporation restricts some features; passing review unlocks the verified badge and the features that make the MINI App feel like part of LINE.

Before review, the header shows the app title and the domain name of your endpoint. After review, it shows the MINI App name with a verified badge. Verified MINI Apps can also offer a shortcut on the phone’s home screen, use a custom path for a readable permanent link, share via QR code and external links, use custom action buttons, send service messages, and use channel consent simplification so first-time users see fewer permission screens.

Our advice is to plan any LINE MINI App development project around the verified version from the start, while launching to staff and a few friendly customers on the unverified channel first. That soft launch finds real problems (a scanner that will not read the barcode, a booking rule that confuses people) before the review, and the review submission then goes in with confidence.

A few businesses choose to stay unverified, usually for internal staff tools or short campaigns. That is a fair choice, but if customers are the audience, the verified badge is worth the one to two weeks.

How do payments work in a LINE MINI App now that LINE Pay has closed in Japan?

LINE Pay ended its service in Japan on April 30, 2025, according to the LINE Pay closure notice, so a MINI App that takes money now needs another payment route: most often PayPay, credit and debit cards including JCB, or konbini payments.

The payment itself runs through a processor that your business contracts with directly. The MINI App shows the checkout, the processor handles card data or redirects to the wallet, and a server-side webhook confirms payment before we mark the order paid. Card details never touch our servers or yours. Which methods you offer depends on your processor contract and on your customers: takeout and cafés tend to want PayPay and cards; ticketed events and online courses often add konbini for customers who prefer cash.

Two practical points. First, if the MINI App sells digital items used inside the app, check whether that counts as an in-app purchase, which needs LY Corporation’s separate approval. Second, payment providers in Japan review your website, and most require a Specified Commercial Transactions Act disclosure page. Our konbini payment integration page covers that onboarding in detail.

Many MINI Apps never take payment at all. A point card or a booking with pay-at-the-shop is simpler, faster to review and cheaper to build, and it is often the right first release.

How much does LINE MINI App development cost?

With BtechWaleTech, a focused LINE MINI App starts at US$600, and one with staff dashboards and integrations starts at US$900. The final number depends on screens, integrations, templates and payments, and it is written into an itemised proposal before any work starts.

Across the market, quotes for LINE MINI App development vary widely. Some of that gap is scope, and some is how the work is staffed: a Japanese vendor with a sales team, a bridge engineer and a project office carries costs that three developers working directly with you do not. Ask any vendor to itemise, so you can compare like with like.

• Number of distinct screens and user flows
• Integrations: POS, CRM, booking engine, ecommerce platform, accounting export
• Service message templates to design and get approved
• Payments, refunds and receipts
• Admin screens your staff need, and how many branches or roles
• Existing data to migrate, such as plastic-card members
• Whether you supply final Japanese copy and design, or need help with layout

Your running costs are separate and billed to you: hosting (often a small AWS or Google Cloud setup), your LINE Official Account plan if you send promotional messages, and processor fees if you take payments. After launch you get two months of free maintenance; ongoing care after that starts at US$120/mo per month.

LINE MINI App development timeline, from brief to verified launch

A focused MINI App typically takes six to ten weeks from signed proposal to verified launch, and a MINI App with a back office takes six to twelve. The LY Corporation review sits inside that window, so we plan for it rather than treat it as an afterthought.

Weeks one and two of LINE MINI App development cover the flow and the channels. We map each screen with you, confirm the Japanese labels you will supply, create the MINI App channels under your provider, and agree the data model for members, bookings or orders.

Weeks three to six are the build. You see progress on the unverified channel from the first week of development, on your own phone, inside LINE. Integrations with your POS or booking system are built and tested against a sandbox or test store.

Weeks six to eight cover a soft launch with staff and a handful of customers, fixes, and the review preparation: icons, loading screen, performance checks, privacy policy wording, and test scenarios for reviewers. Then comes the one-to-two-week review. Once approved, we switch the rich menu and QR codes to the verified link and watch the first week of real use closely.

Tech stack for LINE MINI App development

We build the front end as a lightweight single-page app with the LIFF SDK, and the back end as a small API on your cloud account. The priority is speed on a mid-range phone over a train-station connection.

For the front end we usually choose React or Vue with a small bundle, because LY Corporation’s performance guidelines are part of the review and a slow first screen is the most common reason customers give up. Japanese web fonts are heavy, so we rely on the phone’s system fonts rather than downloading full font files. Images are compressed and sized for phone screens.

The back end is typically Node.js or Python on AWS, with a managed database such as PostgreSQL. We verify every LIFF ID token on the server rather than trusting the user ID sent from the browser, which prevents someone from impersonating another member. Webhooks from your POS or payment processor are signed and checked.

In our LINE MINI App development work, hosting sits in your cloud account, with the Tokyo region as the default choice so data stays close to your customers. Another of us handles the AWS setup, monitoring and backups, and the whole stack is documented so another developer could take it over.

Connecting a LINE MINI App to your POS, CRM and LINE Official Account

A MINI App is only as useful as the systems behind it, and integration is often the largest part of LINE MINI App development. We connect it through each system’s API where one exists, and through scheduled file imports where one does not.

Common links are a POS for points and receipts, a booking engine or calendar for reservations, a CRM for customer history, and an ecommerce platform when the MINI App sells products. If you run Shopify, for example, orders placed in the MINI App can be created as Shopify orders so stock and fulfilment stay in one place; our Shopify developer for Japan page covers the store side.

The LINE Official Account is the other half. Rich menu buttons open the MINI App; a Messaging API bot can reply to “where is my card?” with a direct link; and the member ID lets you send segmented messages to people with, say, points about to expire. The bot and broadcast side is a separate piece of work, described on our LINE chatbot page, and many clients commission both together.

Personal data and privacy policy requirements for a LINE MINI App

A MINI App collects personal data the moment someone signs up, so the privacy policy, the consent screens and the way data is stored all need attention before launch. The review itself checks that the privacy policy names the right company.

We keep collection to what the feature needs; privacy is part of LINE MINI App development, not an add-on. A point card may need only the LINE user ID, a display name and a birthday for rewards; there is no reason to ask for a home address. Data sits in your cloud account in the Tokyo region, encrypted at rest, with staff access by role and a log of who viewed or changed member records.

Japan’s Act on the Protection of Personal Information (APPI) governs how you acquire, use and share that data, including sharing with overseas parties. Your privacy policy and any consent wording are your responsibility and should be checked by your own lawyer. What we do is build the screens to match the policy you approve, keep our own access to production data minimal, and give you an export and deletion function so you can answer customer requests.

Working with a remote LINE MINI App development team in India

India is three and a half hours behind Japan with no daylight saving on either side, so our working day starts around 12:30 JST and runs well into your evening. Mornings in Japan are for your team to test; afternoons are for questions, demos and decisions.

We work in English. The Japanese text on every screen, from button labels to the privacy policy, comes from you or a translator you choose; we build the layout around it and check that long Japanese strings do not break on small phones. Screenshots and short screen recordings do most of the explaining in both directions.

Proposals are in USD, and you can settle in USD or JPY by Wise or bank wire. Nothing is billed before you approve the proposal in writing, and invoices come from India. Your accountant advises on how to record them.

The first two weeks look like this: a kickoff call in the JST afternoon, your team adding us as admins on the LINE provider and cloud account, a clickable flow for your approval, and by the end of week two the first real screen running on the unverified channel on your own phone. From then on you see progress inside LINE every few days.

Risks and red flags in LINE MINI App development projects

Most LINE MINI App development projects that stall do so for the same few reasons: channels created under the wrong provider, a review rejected for paperwork, or a points ledger nobody can reconcile. Watch for these signs with any developer.

• The developer creates the LINE provider or channels under their own account
• No plan for the verification review, or no allowance for its one-to-two-week wait
• User IDs accepted from the browser without server-side token verification
• Points stored as a single balance with no transaction history
• Promotional content planned inside service messages, which LINE does not allow
• A payment flow that marks orders paid before the processor’s webhook confirms
• Hosting and database in the developer’s cloud account, not yours

Each of these is avoidable at the proposal stage. Ask where the channels, repository and database will live, and ask to see the ledger design before the build starts.

Worked example: a hypothetical Fukuoka café chain moves its stamp card into LINE

This scenario is invented to show how LINE MINI App development might be scoped; it is not a client project. Say a café group with five branches in Fukuoka uses paper stamp cards and has a LINE Official Account with a few thousand followers. It wants a digital card and, later, order-ahead for the morning rush.

Release one would be the member card: sign-up with LINE profile consent, a barcode the existing POS scanners read, stamps posted from the POS sales export, a free-drink reward after ten stamps, and a one-time step to move paper stamps across. Staff get a tablet screen to add stamps by hand if the connection fails. That scope fits our app plan, starting at US$600, over roughly six to eight weeks including the review.

Release two would add mobile ordering with pickup slots at each branch and card or PayPay payment through a processor the café contracts with. Because it adds a kitchen-ticket integration and branch-level stock, it would be quoted separately as custom work from US$900. The rich menu would get two buttons, “Member card” and “Order ahead”, and a short bot reply would answer “how many stamps do I have?” with a link straight into the card.

Checklist before you commission LINE MINI App development

Settle these points before the first line of code. Each one is cheap to decide now and expensive to change after the review.

• LINE provider created under your company name, matching your privacy policy
• One or two launch features chosen, with the rest parked for later
• Japanese copy owner named: who writes and approves each screen’s text
• POS, CRM or booking system API access confirmed, or a file-import fallback agreed
• Service message templates listed for each user action
• Payment methods and processor chosen, if the MINI App takes money
• Privacy policy and consent wording reviewed by your lawyer
• Test accounts and test stores ready for the LY Corporation reviewers
• Rich menu, QR codes and staff briefing planned for launch day

If you are still deciding whether a MINI App or a native app suits your budget, the app development cost guide for Japan sets out what each route usually involves.