Business SMS in Japan: MIC Compliance, the URL Prohibition

Every market in this compliance series allows URLs in SMS messages. Japan does not. Japan's major carriers commonly filter or block standard SMS containing URLs on many A2P routes as part of anti-phishing measures. A message with a link to a landing page, a ticket confirmation, a tracking update, or any other web address will generally not be delivered to Japanese recipients through standard SMS channels. This single restriction, with no equivalent in any other market covered in this series, reshapes every program that was designed anywhere else and then extended to Japan without adjustment.

Business SMS in Japan is governed by the Ministry of Internal Affairs and Communications (MIC) under the Act on Regulation of Transmission of Specific Electronic Mail (commonly called the Anti-Spam Act), and by the Act on the Protection of Personal Information (APPI), which recent amendments have further strengthened. Explicit opt-in consent is required before any marketing SMS is sent. Japan's major carriers commonly filter or block standard SMS containing URLs on many A2P routes. KDDI overwrites alphanumeric sender IDs to a shortcode or longcode at delivery. Japanese character encoding reduces the per-segment character limit from 160 to 70 characters. 

Japan is a technically complex SMS market where the distance between what works everywhere else and what works in Japan is wider than in most other markets in this series. The compliance requirements are not unusually demanding by regional standards, but the carrier-level technical constraints, particularly the URL ban and KDDI's sender ID behavior, require program redesign rather than adaptation.

The regulatory framework: MIC, PPC, and two parallel obligations

SMS communications in Japan operate under two separate regulatory authorities with overlapping but distinct scopes.

The Ministry of Internal Affairs and Communications (MIC) governs telecommunications and enforces the Anti-Spam Act, formally the Act on Regulation of Transmission of Specific Electronic Mail. The Anti-Spam Act requires explicit prior consent before sending advertising or commercial messages by electronic means, including SMS. Consent must be documented and records must be maintained. The sending organization must include a sender name and contact information in marketing messages and must honor opt-out requests without delay.

The Personal Information Protection Commission (PPC) enforces the Act on the Protection of Personal Information (APPI), which recent amendments have further strengthened with expanded requirements around data subject rights, cross-border data transfers, and consent documentation. Phone numbers collected for SMS programs are personal information under APPI. The purpose for which the data is collected must be specified at the point of collection, and the data may not be used for a different purpose without a lawful basis for that extension.

For practical purposes, a Japan SMS program needs to satisfy both layers: Anti-Spam Act consent for the act of sending, and APPI compliance for the collection, storage, and use of the phone numbers themselves.

A third law, the Act on Specified Commercial Transactions (ASCT), applies to e-commerce and remote selling contexts and adds further disclosure requirements for commercial messaging in those sectors. Organizations in retail, subscription services, and financial products should confirm ASCT obligations with counsel for their specific program type.

The carrier landscape and the KDDI sender ID issue

Four carriers serve Japan's mobile market. NTT Docomo holds approximately 40 to 42% market share. KDDI, operating under the "au" brand, holds approximately 27 to 29%. SoftBank holds approximately 20 to 22%. Rakuten Mobile, the newest national carrier, has grown to around six to eight percent since launching as a full mobile network operator in 2020.

KDDI's behavior with alphanumeric sender IDs is the most operationally significant carrier difference in the Japanese market. On KDDI's network, alphanumeric sender IDs are not preserved. They are overwritten to either a shortcode or longcode at delivery, which means the brand name you registered as your sender ID will not appear on KDDI subscribers' phones. The recipient sees a number, not a brand name. This is not a registration failure or an error. It is how KDDI's A2P routing functions.

NTT Docomo and SoftBank generally support alphanumeric sender IDs, so the sender name is preserved on their networks. Rakuten Mobile's behavior should be confirmed with your provider for the most current routing characteristics. For programs where sender recognition matters across the full national audience, the KDDI overwrite means the message body must do the identification work that the sender field does on Docomo and SoftBank, which is the same design principle that applies in Mexico where all networks replace alphanumeric IDs with short codes.

Domestic short codes, the five or six-digit numbers that provide the most consistent delivery and carrier recognition, typically require five to eight weeks of carrier approval. International long codes are generally available immediately through international routes, but route quality and filtering behavior vary significantly between providers.

The URL prohibition: the constraint that changes program design

The prohibition on URLs in SMS messages is enforced at the carrier level through filtering. A message containing a URL, whether a full link or a shortened URL such as a bit.ly format, will generally be filtered before delivery. The restriction exists because SMS URLs have been heavily abused for phishing and fraud in Japan, and carrier filtering is the practical enforcement mechanism.

The operational consequences are significant. Programs that rely on SMS to drive recipients to a web page cannot use that approach in Japan. A loyalty campaign that elsewhere reads "Your points expire soon. Check your balance at [URL]" needs to be redesigned entirely. Delivery notifications that include tracking links must remove those links. Appointment confirmations that link to a self-service portal cannot carry that link through SMS.

The alternatives that work within this constraint include: directing recipients to call a phone number included in the message body; directing them to use an app or service by name without including a link; providing QR codes through physical or email channels that link to the destination page rather than including the QR code URL in the SMS itself; and using SMS only for notification and routing richer digital engagement through LINE or email where URLs can be included.

For programs built around authentication and transactional notifications, where the message content is the action itself rather than a pointer to somewhere else, the URL prohibition has no practical impact. OTPs, payment alerts, appointment reminders, account balance notifications, and operational status updates all work without URLs and remain the primary SMS use case in Japan.

Sending hours, consent, and Japanese language considerations

Promotional SMS should generally be sent between 9 AM and 8 PM Japan Standard Time (JST, UTC+9). Japan does not observe daylight saving time, so the time zone is constant year-round. Messages sent outside this window may be filtered or may generate consumer complaints that affect sender reputation.

Consent under the Anti-Spam Act must be specific and affirmative. The standard for what constitutes valid opt-in is generally interpreted strictly: vague consent obtained alongside other agreement purposes is generally not considered sufficient for the Anti-Spam Act's requirements. Documentation of when, how, and what the recipient consented to is required.

Japanese character encoding is a practical constraint that affects every message. When messages include Japanese text, which is expected for consumer-facing communications, the encoding shifts from GSM-7 (160 characters per segment) to Unicode UCS-2 (70 characters per segment). A message that fits comfortably within 160 characters in English may require three or more segments in Japanese, significantly affecting both cost and message structure. Testing message length before campaign launch is more important in Japan than in any other market in this series.

Business SMS in Japan should use polite, formal Japanese where appropriate. The register of language expected in business communications (keigo) differs from casual register, and messages that do not meet recipients' expectations for business communication quality tend to generate higher complaint and unsubscribe rates.

LINE: the channel where Japanese engagement actually happens

Most Japanese consumers do not expect to interact with businesses through SMS. They expect LINE.

LINE is Japan's dominant messaging platform with approximately 96 million monthly active users and penetration across around 90% of Japanese smartphone users. For most Japanese consumers, LINE is where daily personal and business messaging takes place. Brand accounts on LINE, called LINE Official Accounts, allow businesses to send messages to users who have "friended" the official account, which functions differently from the broadcast model of SMS marketing.

For a Japan messaging program, the practical architecture is usually: LINE for engagement, notifications that include rich media, links, and two-way interaction; SMS for guaranteed-delivery authentication and critical operational notifications where LINE connectivity cannot be assumed. An OTP for a banking application must arrive reliably regardless of whether the recipient has LINE installed or their LINE account active. A marketing campaign for a retail brand, a loyalty program communication, or a customer service message is better served through LINE where the full engagement toolkit is available.

LINE Official Accounts operate through a completely separate API and licensing model from SMS. LINE's Messaging API requires its own setup, approval, and management workflow. The compliance requirements for LINE messaging overlap with APPI personal data obligations but are distinct from the Anti-Spam Act's SMS-specific rules. Organizations planning a Japan program that includes both SMS and LINE should treat the two channels as separate integration tracks that share a data and consent layer.

WhatsApp penetration in Japan is significantly lower than LINE. For Japanese-audience programs, LINE is the primary messaging platform equivalent, not WhatsApp.

Two-way SMS and channel architecture in Japan

Standard international A2P SMS routes in Japan generally support one-way delivery. Inbound reply functionality depends on the specific carrier route and number type. For programs requiring two-way interaction, whether for survey responses, acknowledgment capture, or opt-out via reply, the architecture should be designed around LINE's native two-way capabilities rather than relying on SMS reply functionality that may be limited or unavailable depending on routing.

For organizations operating programs where genuine two-way SMS is necessary and where LINE is not the appropriate channel for the interaction, the Telerivet Android Gateway provides an alternative path through P2P routing from a local Japanese SIM rather than through A2P carrier infrastructure. This approach has been used in Japan for programs that require reply-based workflows where the standard A2P infrastructure does not provide a practical path. It is worth noting that this is a different architecture from standard carrier A2P, and organizations should discuss their specific requirements with the Telerivet team to assess whether it is the appropriate design for their use case.

Japan rewards channel specialization rather than channel replacement. Organizations sometimes arrive expecting LINE to replace SMS entirely because of its widespread adoption. In practice, the strongest deployments use each channel for what it does best: SMS for guaranteed delivery of authentication codes and critical operational notifications, and LINE for rich customer engagement, customer service, and ongoing conversations. Treating one as a replacement for the other usually produces a weaker customer experience than designing around both from the outset.

BYOC architecture applies in Japan in the same way it applies across Asia-Pacific. Your consent records, suppression lists, and program logic belong to the organization and sit above the connectivity layer. For Japan specifically, where the carrier technical environment is unusual relative to other markets and where channel architecture across SMS and LINE requires careful design from the outset, having the program logic separated from any single connectivity provider gives the flexibility to adapt as routes and channel options develop.

For Japan programs that are part of a broader Asia-Pacific operation including markets like India, Indonesia, or Australia, the channel selection guide covers how to sequence SMS alongside other channels for audiences with different channel expectations. Japan's LINE-first orientation is the sharpest example in the Asia-Pacific cluster of how the right channel architecture depends not just on regulatory compliance but on where the audience actually is.

Frequently asked questions

Why are URLs prohibited in Japan SMS? Japanese carriers filter messages containing URLs due to widespread phishing and fraud abuse through SMS links. This is a carrier-level technical restriction, not a regulatory rule with a specific statutory citation. The practical effect is the same: messages with URLs generally do not reach recipients. Programs must be designed to communicate without links, directing recipients to apps, phone numbers, or physical QR codes instead.

What happens to my alphanumeric sender ID on KDDI? KDDI overwrites alphanumeric sender IDs to either a shortcode or longcode at the point of delivery. The brand name you registered will not appear to KDDI subscribers. NTT Docomo and SoftBank generally preserve alphanumeric sender IDs. For programs where sender recognition matters across the full Japanese audience, the message body must identify the sending organization clearly, since the sender field is not reliable across all carriers.

How does Japanese character encoding affect message length? Messages containing Japanese text use Unicode UCS-2 encoding, which reduces the per-segment character limit from 160 characters to 70. A message that fits in one segment in English may require two or three segments in Japanese, affecting both cost and message structure. Thoroughly testing message length before campaign launch is important for any Japan program.

Is LINE more important than SMS for Japan programs? For most consumer-facing programs, yes. LINE has approximately 90% smartphone penetration in Japan and is the channel where Japanese consumers expect to interact with businesses for engagement, promotions, and customer service. SMS is the appropriate channel for guaranteed-delivery notifications, OTPs, and critical operational messages where LINE connectivity cannot be assumed. The two channels serve different purposes and most effective Japan programs use both.

Does Telerivet support LINE for Japan programs? Not natively at this time but it is technically achievable. Telerivet does currently support WhatsApp, Viber, Telegram, and RCS alongside SMS, which covers the primary messaging channels for most Asia-Pacific programs. If LINE is a meaningful part of your Japan audience's communication behavior and you want to explore what an integration would look like, reach out to us.

Does APPI apply to my organization if I am based outside Japan? Organizations processing the personal information of individuals in Japan should assess whether APPI applies to their activities regardless of where the organization is located. Recent amendments have further strengthened data subject rights and cross-border transfer requirements. Phone numbers collected for Japan SMS programs are personal information under APPI, and organizations should ensure their consent documentation, purpose specification, and data handling practices are consistent with the Act's requirements.

This article provides general operational information and should not be considered legal advice. Organizations should consult qualified legal or data protection professionals regarding their specific compliance obligations under Japanese telecommunications and data protection law.


Talk to our team about building a messaging program for Japan and across your Asia-Pacific markets from one platform.

« Blog