The Patent Court's decision in Case No. 2025he10405, the so-called 010PAY case, addresses when a trademark displayed on a mobile app serves as an indication of source for the goods of a “mobile app” and when it serves as an indication of source for the “services” provided through the app. In today's environment where app-based businesses are commonplace, this case provides practical standards for designing the boundaries between Class 9 software trademarks and service trademarks in Classes 35, 36, 42, etc.

The core question of this case is simple: If a mark is displayed on an app screen or in the app's name, can it be immediately considered as being used on a “mobile app” product? The Patent Court did not view it so simplistically. The court considered the app's functionality, usage structure, revenue model, use of in-app payments, and app market payment policies to determine that the mark functioned as an indication of source for the services provided through the app, rather than for the app itself.
The plaintiff was the owner of registered trademarks for goods such as downloadable computer programs and computer application software for mobile phones in Class 9. The defendant, on the other hand, held registered trademarks for services such as mobile payment services, electronic financial transactions, and mobile payment intermediary services in Class 36.
The defendant operated a mobile app named “010PAY,” on which the mark in question was displayed. The plaintiff filed an affirmative action for confirmation of scope of rights, arguing that the defendant's use of the mark fell within the scope of their trademark rights for mobile apps in Class 9.
The Intellectual Property Trial and Appeal Board (IPTAB) acknowledged that the mark was displayed on the app but ruled that it indicated the source of the services provided through the app, not the “mobile app” product specified by the plaintiff. Therefore, the IPTAB determined that there was no legal interest in the confirmation because the actual use of the trademark differed from the goods specified by the plaintiff. The Patent Court upheld this conclusion and dismissed the plaintiff's claim.
The Patent Court acknowledged that mobile apps, being intangible, can be considered goods under trademark law in certain circumstances. If the app itself is offered as the object of a transaction, and users acquire and use it primarily for its own use or enjoyment, the mobile app can be an independent object of trade.
However, what the court emphasized in this case was the “substance of the transaction” rather than the “form.” The source-indicating function of a trademark is not determined solely by the appearance of the mark on the app icon, screen, or name. What is crucial is what the object of the transaction is, directly linked to the payment of consideration, and what the consumer perceives the mark to indicate the source of.
Therefore, even if a trademark is displayed on a mobile app, if the app serves merely as a functional tool or medium for providing other goods or services, rather than being a product consumed in itself, consumers may perceive the mark as indicating the source of the services provided through the app or the provider of those services, rather than the app itself.
The app in this case was structured to enable the purchase of mobile gift certificates, payment processing, and point accumulation and utilization. Users purchased mobile gift certificates or used payment-related services through the app, and the utility extended beyond the app itself to exchanges/purchases of goods at offline stores or payments at external affiliated merchants.
In other words, the reason users installed and ran the app was not to consume the software itself, but to execute external transactions through the app. Based on this usage pattern, the court viewed the substantive object of the transaction not as the app itself, but as the external goods or services acquired and used via the app.
The Patent Court considered the revenue structure as an important determining factor. Whether a mark functions as an indication of source for a particular object is linked to what transaction unit consumers perceive as having economic value.
In this case, the defendant's economic benefit did not arise directly from the installation or simple use of the app. Revenue, such as commissions, was generated through the actual establishment and execution of external transactions, such as the sale of mobile gift certificates. In such a structure, it is highly probable that consumers perceive the object of the transaction to be the external goods or services transacted through the app, rather than the app itself.
Another notable factor in this case was the use of the in-app payment system. The court even examined the payment policies of Google and Apple. Generally, in-app payment systems can be relevant for transactions of digital content or services whose utility is completed within the app. Conversely, for transactions of goods or services consumed or fulfilled outside the app, in-app payment systems are often not intended.
In this app, transactions were conducted through external payment methods, not through the in-app payment system provided by the app market operator. The court viewed this as an indication that the app was perceived not as the object of transaction itself or its internal content, but as a functional tool for connecting and supporting external transactions.
This case went beyond a simple trademark infringement assessment and involved the issue of legal interest in a scope of rights confirmation trial. The plaintiff specified the goods for use of the mark in question as “mobile apps.” However, as the court viewed the actual use as services provided through the app rather than the mobile app itself, a problem arose where the use specified by the plaintiff did not match the defendant's actual usage pattern.
In an affirmative action for confirmation of scope of rights, the identity of the mark in question and the mark actually used, as well as the appropriateness of the specified goods/services, are crucial. If the actual subject of use is a service, but it is specified as a mobile app product, the trial request may not serve its purpose of resolving the dispute. This is why the trial request in this case was deemed to lack legal interest.
The 010PAY case demonstrates that for app-based businesses, Class 9 “apps” alone may not be sufficient when designing trademarks. While the app is the interface exposed to the forefront of the business, the actual subject of protection under trademark law could be the app itself or the services provided through the app.
Companies seeking to protect their app names as trademarks should not stop at filing for Class 9 app goods based solely on the app icon or app store display. If the actual business model is service-centric, including payment, points, coupons, gift certificates, platform brokerage, finance, reservations, delivery, education, or content provision, the relevant service classes must be considered and filed together.
Conversely, when seeking to address another party's use of an app trademark, one must first distinguish whether the mark is used on app products or on services provided through the app. App screen captures alone may not be sufficient. It is necessary to consider terms of use, payment structures, app market registration information, revenue generation methods, user journeys, and actual transaction objects.
In mobile app trademark disputes, the key is not “whether it is displayed on the app,” but “what consumers perceive it to indicate the source of.” The 010PAY case is a ruling that addresses this question through specific factors such as the app's functionality, usage structure, revenue structure, payment methods, and app market policies.
Pine IP Firm recommends a strategy of reviewing both Class 9 app goods and actual service classes during the app brand application stage, and specifying the goods/services for the mark in question accurately according to the actual usage pattern during the rights enforcement stage. In app-based businesses, the strength of trademark rights is not determined solely by the similarity of registered marks. It must be possible to prove in which transaction and as an indication of source for which object it was used.
The 010PAY case clearly shows that in app trademark practice, one should not mechanically equate “Class 9 app goods” with “services provided through the app.” If the app is the entrance to the business, trademark strategy must encompass the actual transaction structure beyond that entrance.