New

Every mark published in the last 90 days — see today's opposition deadlines

All articles
Technology5 September 20268 min read

Protecting App Names and Logos: A Guide for Nepalese Fintech and IT Startups

Fintech and IT startups face Nepal's Class 9/35/36/42 filing puzzle plus app-store realities — how to build brand protection that survives funding rounds and expansion.

A fintech app's brand lives in four places at once: the app store, the register at the DOI, the domain, and the user's memory. Startup brand protection fails when it covers one and assumes the rest.

For Nepal's fintech and IT founders, the filing puzzle has a shape — and a sequence. This guide walks it.

In short

Nepalese brand protection for fintech and IT startups: file the app/platform name and logo at the DOI as a trademark — Class 9 (software, downloadable apps), Class 42 (SaaS, IT services, software development) and Class 36 (financial services) for fintech, plus Class 35 where marketplace/retail functions exist — one class per application under Nepal's single-class rule (NPR 1,000 application + NPR 5,000 registration per class at current rates). Sequence: clear the name first (conflict check across the Bulletin, both scripts, phonetic and transliteration variants — 'eSewa/Khalti/eBanking' territory is crowded), file before launch (first-to-file makes launch-day fame irrelevant to priority), file the logo/device mark alongside or after the word mark (word marks protect the name everywhere; device marks protect the visual identity), secure the .np domain and matching gTLDs, and align app-store listing names with the registered mark. Funding-round realities: investors' diligence checks trademark ownership and chain of title — assigned logo copyright, correct applicant entity, records current at the DOI. International: Nepal has no Madrid route, so foreign expansion means direct country filings (Paris Convention priority within 6 months of the Nepal filing).

The class puzzle: where a fintech/IT brand actually lives

Nepal applies the Nice Classification with the single-class rule — one application per class — so the first strategic decision is which classes cover the business. The working map for tech:

Budget maths at current fees: NPR 1,000 to file + NPR 5,000 to register, per class — a three-class fintech protection is ~NPR 18,000 in official fees. That is the cheapest line item in the cap table's history, which is why deferring it is never a rational trade.

The tech startup's class map
ClassCoversFile if…
Class 9Software, downloadable applications, app-store goodsYou ship an app or downloadable software — nearly always
Class 42SaaS, PaaS, IT consultancy, software development servicesYou run a platform or sell tech services — nearly always
Class 36Financial services, payment processing, e-wallet servicesFintech: payments, wallets, lending, insurance tech
Class 35Advertising, marketplace/retail intermediary servicesYou aggregate sellers, run ads, or broker transactions
Class 38Telecommunications, streaming/ transmissionComms or streaming features are core, not incidental

Clear first, file before launch

Nepal is first-to-file: the launch, the press, the funding announcement — none of it creates priority; the application date does. And Nepal's fintech/IT naming space is crowded and phonetically dense (the e- and pay- prefixes, transliterated names in both scripts), which makes clearance the step that saves refilings: screen the proposed name against the Bulletin's published records — exact spellings, sound-alikes, Devanagari renderings and class overlap — before the name is committed to a pitch deck, let alone an app store.

The sequence that works: clear (search, including transliterations) → file (word mark first — it protects the name across all visual presentations — plus the logo/device as a second mark where the visual identity is distinctive) → launch. The word-then-device order matters: a word mark stops lookalike *names* regardless of styling; the device mark protects the specific logo. Startups that file only the logo discover the gap when a competitor ships a differently-styled same-name app.

  • Filing date, not launch date, is priority in Nepal
  • Word mark first; device/logo as the companion filing
  • Screen both scripts and phonetic variants before committing

Legal references

The domains, the app store, and the record hygiene

Domains: secure the .np ccTLD (registered through Mercantile's register) and the obvious gTLDs at launch; a trademark helps recover a squatted domain later, but prevention is cheaper — and .np disputes have no UDRP, so recovery runs through negotiation or the courts. App stores: list under the registered mark; app-store display names that drift from the registered word mark weaken both. Record hygiene: keep the DOI record's name, address and email current (record changes cost NPR 1,000); mismatches between the register and the cap table are a diligence flag and a correspondence risk.

Chain of title for the logo: the designer owns the artwork's copyright by default — the assignment from the designer (or agency) belongs in the same folder as the trademark certificate, because the device mark's clean registration and any future enforcement assume it.

Funding rounds and foreign expansion

Diligence reality: institutional investors screen trademark ownership, applicant entity and chain of title — the fixes are cheap before the round and expensive during it. Entity alignment: file in the name of the operating company (or assign early from founder names — with clean paperwork either way). Expansion: Nepal is outside the Madrid Protocol, so entering India or elsewhere means direct national filings — with Paris Convention priority available within 6 months of the Nepal application, which is why the Nepal filing date is also the first brick of the international portfolio. File early at home; the priority clock starts whether you plan to expand or not.

Want this handled for your brand?

IP Watch monitors new trademark publications in Nepal and alerts you to potentially conflicting marks — with the context needed to review them.

This article is general information, not legal advice.