Article summary
LINE and PayPay began phased account linking in summer 2026 for transfers, group bills, friend lists, and points. Review consent, data boundaries, and business impact.
LINE and PayPay announced on July 2, 2026 that phased account linking would begin that summer. Linked users can access experiences such as PayPay transfers and group bills from LINE chats, followed by Mini App, friend-list, and points integration. Linking requires user consent; the basic functions of LINE and PayPay remain available without linking.
The integration connects communication and payment products in Japan. It does not mean a business can look up a PayPay account, balance, spending power, or LINE friend relationship from one phone number. Product convenience and third-party data access are different questions.
Primary boundary: A user linking two accounts through an official consent screen does not open both datasets to every business, and it does not add PayPay fields to a LINE number-check export.
Which features did the announcement describe?
The joint release from PayPay and LY Corporation describes a sequential rollout. Some experiences become possible with account linking, while others follow later. Content should state the feature and stage rather than claiming that everything launched at once.
| Feature | User experience | Important limit |
|---|---|---|
| Transfers and group bills in LINE | Send PayPay Balance or split a bill in chat | Linking required; balance types have different rules |
| PayPay LINE Mini App | Balance, points, history, send/receive, ATM top-up | Limits differ; identity verification remains in PayPay app |
| LINE friends shown in PayPay | Select friends more easily for transfers | User must enable the dedicated setting |
| Points integration | LINE Points move toward PayPay Points | Sequential rollout and unlinked-point rules |
| PayPay registration in LINE | A non-user can register without the PayPay app | Availability depends on rollout stage |
What consent does linking require?
The release explicitly states that users must consent. If someone has already linked LINE or PayPay with Yahoo! JAPAN, accepting the new link may connect all three accounts. The actual consent screen should be reviewed.
A business must not turn “the products can connect” into “every user is linked by default.” Consent should be specific, understandable, and manageable. Product copy and support scripts need to explain what linking changes and which basic services remain without it.
| Status | Safe statement | Do not assume |
|---|---|---|
| Not linked | Basic LINE and PayPay functions remain | The user agreed to data connection |
| Linking accepted | Relevant integrated functions can roll out | Every function is immediately available |
| Friend display enabled | LINE friends may appear in PayPay | A business can export that list |
| PayPay identity verification complete | It affects selected balances and functions | A third party receives verification data |
How does the Mini App differ from the PayPay app?
The release says the Mini App can provide key entry points inside LINE, including balance, points, send/receive, transaction history, and ATM top-up. Its usage limits differ from the standard PayPay app. Identity verification still needs the PayPay app, and payment and point-investment functions were not available in the Mini App at announcement.
“Access selected features without another download” should not be rewritten as “LINE completely replaces the PayPay app.” A tutorial needs to name the entry, account state, verification location, and feature limit.
What does friend-list integration mean?
After linking and enabling the setting, users can display LINE friends in PayPay to choose transfer recipients. This is a user interaction, not a downloadable marketing audience for brands.
A company cannot infer payment capacity, family relationship, or purchase intent from a friend connection. A transfer context is not consent for promotion. Communication and payment data retain their specific purposes.
| Data object | Created by | Appropriate use | Do not put into |
|---|---|---|---|
| LINE friend relationship | User social activity | User selects transfer recipient | Third-party cold audience |
| PayPay balance and transaction | Payment activity | Payment-product functions | Number-check result |
| LINE number check | TXT task | Channel-level status | Payment-capacity profile |
| CRM permission | Form, order, or conversation | Determine contact scope | Inference from friends or linking |
What changes for a business?
A company operating in Japan may need to update support knowledge, payment instructions, refund routing, and campaign copy, especially when a user enters PayPay-related experiences from LINE. Support should know which step happens in LINE, the Mini App, or the standard PayPay app and where identity verification occurs.
The integration is not a new data-acquisition interface. A better content opportunity is user-initiated support: preparation before linking, consent explanation, transfer issues, point rules, and unlinking or escalation.
LINE number checking is a different system
Through the AppShai LINE Number Checker, Registration Check processes phone numbers in TXT with one number per line and exports Excel containing phone number and registration status. LINE Demographic Check is separate and may return phone number, user ID, nickname, gender, age, profile image, people count, image type, and skin-tone field.
These tasks do not return a PayPay account, balance, transaction, friend, or points field. LINE registration does not prove that the user linked PayPay or agreed to marketing. Demographic task fields must not be extended into payment ability or credit decisions.
| Question | Correct evidence | Wrong method |
|---|---|---|
| Is a number registered on LINE? | LINE Registration Check and checked-at date | Inspect PayPay state |
| Did a user link PayPay? | User’s own official interface | Infer from number checking |
| May the business send marketing? | CRM permission and opt-out | Infer from linking or friendship |
| How should a payment issue be resolved? | PayPay support and transaction record | Use checking Excel |
Six steps to update the knowledge base
- Separate live, planned, and region-specific functions from the release.
- Record the LINE, Mini App, and PayPay app paths with real test accounts.
- Redact personal and payment information from consent-screen captures.
- Write separate support flows for unlinked, linked, and verification-error states.
- State which questions require PayPay’s official support.
- Review sequential features and content dates monthly.
The knowledge base should help a user complete a task rather than use a payments headline to expand a phone-number product claim.
Fact-check table before publishing
| Check | Question |
|---|---|
| Date | Is this the announcement, start of linking, or launch of one feature? |
| Scope | Is the function phased and focused on Japan? |
| Consent | Does the copy state that user action and consent are required? |
| Verification | Does identity verification remain in the PayPay app? |
| Product boundary | Does the page falsely claim LINE checking returns payment data? |
| Source | Is the joint release linked with a verification date? |
The LINE–PayPay connection matters because it brings communication and payments closer. That proximity makes it even more important to keep user consent, platform functions, payment data, number checking, and CRM permission clearly separated.
