Meet us at ETH Belgrade 2026·Aug 26–27

Let's talk
For Fintechs & Neobanks

Send to a Name, Not an Address

Give every user in your app a readable username. Fewer failed transfers, less fraud surface, fewer support tickets, and stablecoin send flow that non-crypto users actually understand.

860k+ subnames22M resolutions30+ partnersBacked by ENS DAO

How payable names work

Fintechs and neobanks can give every customer a payable username - an ENS subname like alice.yourbank.eth or alice.yourbank.id - issued at signup. Instead of pasting a 42-character wallet address, the sender just types a name. Namespace creates these names through an API, with no gas cost and no contract deployment. One name holds address records for every chain you support, so it always resolves to the right address on the right chain before the money moves. The names are not locked to your app. They resolve in wallets, explorers, and other fintechs, so cross-app transfers happen without either side integrating the other.

FreeGaslessOne name, many chainsResolves in 1,000+ appsUse any domain you own (.eth, .id, etc.)
01The problem

Why addresses break payment products

Nobody knows who 0x71C7...F2a9 is.

Addresses are unreadable, unmemorable, and impossible to confirm at a glance. Your users are moving money to a string they cannot verify, so they paste, squint at the first and last four characters, and hope it's correct. It is the highest-friction input in consumer finance, and it sits at the exact moment you need them to feel confident. Names are the only part of this stack a first-time user recognizes from every other app they have ever used.

Wrong-address transfers are irreversible

Address poisoning attacks specifically target payment behavior. Attackers send dust transactions from lookalike addresses so the fake address lands in the user's history, then wait for a copy-paste. Onchain poisoning attempts tracked by security researchers rose from roughly 628,000 in November 2025 to 3.4 million in January 2026. In December 2025 a single user lost close to 50 million USDT this way, 26 minutes after making a small test transfer. You cannot refund those. You can only prevent them, and prevention starts with making the destination human-readable before the user signs.

You probably have siloed usernames

Cash App handles work in Cash App. Revolut tags work in Revolut. Every fintech builds its own username system and none of them talk to each other. The moment your user needs to pay or receive money from someone outside your app, they are back to copying a raw address.

Your brand is invisible, but it shouldn't be

Every transfer your customers make outside your app shows an anonymous string that could belong to any product. Named customers change that: every payment to or from alice.yourbank.id puts your brand in the other side's app, in explorers, and in transaction history - distribution you do not pay for, compounding with every transaction.

02In your product

How usernames changea payments flow

Claim at signup

alice.yourapp.eth, issued automatically with the account. No transaction, no gas, no extra step for the user to understand.

Send by name

The user types a name. Your app resolves it, displays the avatar and profile, and only then enables the confirm button. The verification step becomes visual instead of a character-by-character comparison.

Request and payment links

Share a name instead of an address. It fits in a message, a bio, an invoice, or a QR code, and it does not change when the user rotates wallets.

One name, every chain, 1,000+ apps

Store address records per chain under the same name. The sender picks a person, your app picks the rail.

Interoperable by default

Because these are ENS names, someone in a different wallet can pay your user without your app being involved at all. That is a growth surface most payment products do not have.

Secured and verified

Resolution is verified onchain through ENS, so the name your user pays is provably the account it belongs to. Lookalike addresses and spoofed handles lose their attack surface.

03How it works

How to add usernames to your app

Three integration points, then a choice of name type.

01

Point a name at our resolver

You keep ownership of the root name.

02

Issue at account creation

One API call, no gas, no contract deployment.

03

Resolve on send

ENS-native resolution in your send flow, plus Resolvio for bulk resolution across contact lists and transaction history.

Name types for payment apps

Mode
Cost
Ownership
Speed
Best for
OffchainRecommended
Free, gasless, unlimited
You control issuance and management.
Instant
Every user by default, issued at signup.
L2 onchain
Cents of L2 gas
User-owned NFT, transferable
Seconds
Premium or power users
L1 onchain
Mainnet gas
User-owned NFT, fully trustless
Block time
Flagship and institutional accounts
Case study · Payments

Payment usernames, live in production

Situation. A payments app wanted readable identities for sending and receiving - names people can type instead of addresses.

Built. Payment usernames on Namespace infrastructure: issuance, resolution, and multi-chain address records, operated as a multi-year partnership.

Result. Usernames that resolve across the ENS ecosystem, on the same stack that serves 22M+ resolutions in production.

04What you get

What is included

Subname API and SDK

For issuance and record management.

Resolvio

Our resolution API, with bulk resolution and caching. Free, and self-hostable if your compliance team prefers it.

ENS Components

Drop-in React components for claim flows and profile editing.

Multi-chain address records

Under a single name.

Reserved and blocked name lists

To prevent impersonation of your brand, support staff, or well-known users.

No-code dashboard

For operations and support teams.

05Why Namespace

Why teams choose Namespace

Namespace is the ENS DAO-backed service provider.

Build it yourself, or don't

In-house
Namespace
Issuance and resolution infra
You build, audit and maintain
Managed and monitored
Uptime and monitoring
Your on-call rotation
Operated with SLAs
Reserved and blocked name lists
You write and enforce the policy
Included and managed
Standards work
You track ENSIPs yourself
Follow and actively contribute.
Engineering to production
A quarter, realistically
Days to weeks
Subname expertise
You start from zero
Experts in offchain, L1, and L2 subnames
Lock-in
None, but you maintain it all
None: exportable names, standard ENS records
860k+Subnames issued
22MResolutions served
30+Partnerships and integrations
221Namespaces issuing subnames with us
Trusted byCeloFilecoinPOAPUnicorn
ENS DAO Service Provider

The business case

Names pay for themselves in avoided losses and support tickets - and they open a revenue line. Fintechs price premium and short labels, earn on renewals, and turn usernames into a paid tier of their crypto features.

  • Fewer wrong-send losses and refund disputes
  • Fewer 'did I send this right?' support tickets
  • Premium and short labels, priced by you
  • Named customers carry your brand into other apps

Our pricing, plainly

If names are free for your customers, we charge nothing. We charge only on priced subnames and only earn when you do.

FreeOffchain subnames and integration support
5%On paid onchain mints through our infra
5-10%On mints when we build your integration for free, routed to the ENS DAO
FAQ

Questions teams ask us

Does this actually reduce payment errors and fraud?

Names remove the failure mode. Address poisoning, spoofing, and clipboard hijacking all exploit the fact that customers can't read hex. A name like alice.yourbank.eth is verifiable at a glance - there's nothing to mis-paste and no lookalike to fall for.

Do names work for cross-chain and stablecoin payments?

Yes. ENS names carry multi-chain address records, so one name resolves to the right address on the right chain - whether the transfer is USDC on Base, stablecoins on an L2, or ETH on mainnet. Namespace supports records across 100+ chains.

What does it cost at consumer-fintech volume?

Offchain subnames are free at any volume - for you and your customers. Resolution via the SDK and API is free to use. If you later sell premium names, Namespace charges a fixed 5% of that registration revenue only.

Is resolution reliable enough for a regulated product?

Resolution is trustless and verifiable: offchain records are signed and verified onchain via CCIP-Read (EIP-3668), the same standard the broader ENS ecosystem relies on. Namespace has served 22M+ resolutions at 99.9% uptime and operates with SLAs.

Do our customers need to know what ENS is?

No. To your customers it's just a username - they pick it at signup and pay people by name, like every other feature in your app. The ENS layer underneath is what makes that username work outside your app too.

Can we use our own domain instead of a crypto name?

Yes. ENS supports DNS domains through DNSSEC integration, so usernames can live under yourbank.id or yourbank.com instead of a .eth name. World runs world.id usernames this way - 17 million of them. Your customers see your brand, not a crypto TLD.

Does the recipient need a username too?

No. Your app can send to any raw address. Names are an improvement on both sides but a requirement on neither, so nothing breaks for users who do not have one.

Does issuing names create custody or regulatory exposure?

Issuing a name does not hold, move, or create a claim on user funds. It is a naming and routing record. Your existing custody and transmission posture is unchanged. We are happy to walk your compliance team through the architecture.

What happens to a user's name if they leave our app?

Offchain names remain under your namespace and you decide the policy. Onchain names are user-owned NFTs that travel with them. If you want names to be genuinely portable, issue onchain.

Is the offchain database a privacy problem?

Offchain names are stored in a database we operate, containing the name, the address, and any records you set. It holds no more personal data than the public chain already does. It can also be self-hosted if you need the data inside your own perimeter.

Can we import users who already have ENS names?

Yes. Read their existing primary name first and display it. Users often hold several names, and ENS handles that natively.

What is the resolution latency on a send?

Resolvio caches aggressively and supports bulk resolution, so a send-flow lookup does not add perceptible delay. Contact lists and transaction histories can be resolved in batches rather than one call at a time.

Why not build ENS naming infrastructure in-house?

Many teams try and underestimate the complexity. Production naming requires resolvers, CCIP-Read gateways, metadata services, indexing, ENSIP compliance, security monitoring, and ongoing protocol updates. Namespace abstracts all of that, so you ship in days instead of quarters - without hiring a permanent naming team.

How long does an integration take?

Depending on scope, anywhere from a few days to a few weeks. Namespace works with your team from initial scoping through launch and post-launch support - including SDK integration, resolver setup, and custom configuration.

What happens if Namespace disappears?

Your names are not trapped. ENS records are portable, resolvable, and recoverable through standard ENS mechanisms. Onchain subnames are user-owned NFTs; offchain subnames can be migrated. Namespace is infrastructure - not a custodial lock-in.

ENS partner avatar
ENS partner avatar
ENS partner avatar
ENS partner avatar
ENS partner avatar
Join 30+ Partners

Wall of Love

The Namespace team have been very proactive and supportive of our timelines to build an integrations with our offering. Definitely recommend working with them!
Joan testimonial photo

Joan

Founder of OpenFort

Namespace has been a core partner for PinMe. Their APIs are extremely easy to use, their subdomain infrastructure is stable and built for the long term.
Ted testimonial photo

Ted

Co-founder of PinMe

ENS is the future, and Namespace offers critical tools for making that happen
brantly.eth testimonial photo

brantly.eth

Founder of EFP

Namespace is providing a magical service. They made issuing thousands of subdomains for ETHDenver attendees simple and nearly effortless.
Griff.eth testimonial photo

Griff.eth

Founder of Unicorn & Giveth

When I was exploring ways to launch a local onchain music community, Namespace immediately came to mind. Their tooling made it effortless.
Marcus testimonial photo

Marcus

ENS DAO

Y'all are killing it and I think every product should have their own subname. And y'all are now my go-to rec. Love y'all 💛
Jesse Pollak testimonial photo

Jesse Pollak

Founder of Base

Our collaboration with Namespace and the Web3.js Plugin went really well. The plugin enabled developers to register and interact with ENS domains.
Santiago testimonial photo

Santiago

DevRel at Web3js

Namespace helped PizzaDAO's members mint subnames to show their affiliation all over the metaverse. The pizza flavored minting website is *chef's kiss*.
snax.eth testimonial photo

snax.eth

Head of Stuff at PizzaDAO

The Namespace team have been very proactive and supportive of our timelines to build an integrations with our offering. Definitely recommend working with them!
Joan testimonial photo

Joan

Founder of OpenFort

Namespace has been a core partner for PinMe. Their APIs are extremely easy to use, their subdomain infrastructure is stable and built for the long term.
Ted testimonial photo

Ted

Co-founder of PinMe

ENS is the future, and Namespace offers critical tools for making that happen
brantly.eth testimonial photo

brantly.eth

Founder of EFP

Namespace is providing a magical service. They made issuing thousands of subdomains for ETHDenver attendees simple and nearly effortless.
Griff.eth testimonial photo

Griff.eth

Founder of Unicorn & Giveth

When I was exploring ways to launch a local onchain music community, Namespace immediately came to mind. Their tooling made it effortless.
Marcus testimonial photo

Marcus

ENS DAO

Y'all are killing it and I think every product should have their own subname. And y'all are now my go-to rec. Love y'all 💛
Jesse Pollak testimonial photo

Jesse Pollak

Founder of Base

Our collaboration with Namespace and the Web3.js Plugin went really well. The plugin enabled developers to register and interact with ENS domains.
Santiago testimonial photo

Santiago

DevRel at Web3js

Namespace helped PizzaDAO's members mint subnames to show their affiliation all over the metaverse. The pizza flavored minting website is *chef's kiss*.
snax.eth testimonial photo

snax.eth

Head of Stuff at PizzaDAO

The Namespace team have been very proactive and supportive of our timelines to build an integrations with our offering. Definitely recommend working with them!
Joan testimonial photo

Joan

Founder of OpenFort

Namespace has been a core partner for PinMe. Their APIs are extremely easy to use, their subdomain infrastructure is stable and built for the long term.
Ted testimonial photo

Ted

Co-founder of PinMe

ENS is the future, and Namespace offers critical tools for making that happen
brantly.eth testimonial photo

brantly.eth

Founder of EFP

Namespace is providing a magical service. They made issuing thousands of subdomains for ETHDenver attendees simple and nearly effortless.
Griff.eth testimonial photo

Griff.eth

Founder of Unicorn & Giveth

When I was exploring ways to launch a local onchain music community, Namespace immediately came to mind. Their tooling made it effortless.
Marcus testimonial photo

Marcus

ENS DAO

Y'all are killing it and I think every product should have their own subname. And y'all are now my go-to rec. Love y'all 💛
Jesse Pollak testimonial photo

Jesse Pollak

Founder of Base

Our collaboration with Namespace and the Web3.js Plugin went really well. The plugin enabled developers to register and interact with ENS domains.
Santiago testimonial photo

Santiago

DevRel at Web3js

Namespace helped PizzaDAO's members mint subnames to show their affiliation all over the metaverse. The pizza flavored minting website is *chef's kiss*.
snax.eth testimonial photo

snax.eth

Head of Stuff at PizzaDAO

Our experience working with Namespace has been exceptional. Their team combines strong technical expertise with clear communication and a true spirit of partnership.
Kate testimonial photo

Kate

Head of Product & GTM @ CELO

From simple to complex Subname needs, Namespace has the tools and expertise to make it happen. Fully recommend.
Simon testimonial photo

Simon

Lead DevRel @ ENS Labs

You've developed an innovative and frictionless way for people to monetize their domains, empowering users to unlock new value with ENS.
Alex Netto testimonial photo

Alex Netto

Founder of Blockful

We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions
Patricio testimonial photo

Patricio

Founder of POAP

Namespace has quickly become the go-to platform for managing ENS subnames. What was once confusing and error-prone is now a streamlined, intuitive experience.
Ben testimonial photo

Ben

Co-founder of ETH.LIMO

Namespace is the best tool for creating and issuing ENS subdomains, I think. The dashboard is very easy to use.
Sahil testimonial photo

Sahil

DevRel at QuickNode

The Namespace team is incredibly friendly and a pleasure to work with. Their passion and dedication to the ENS ecosystem are evident in everything they do.
Thomas Clowes testimonial photo

Thomas Clowes

Co-founder of Unruggable

Our experience working with Namespace has been exceptional. Their team combines strong technical expertise with clear communication and a true spirit of partnership.
Kate testimonial photo

Kate

Head of Product & GTM @ CELO

From simple to complex Subname needs, Namespace has the tools and expertise to make it happen. Fully recommend.
Simon testimonial photo

Simon

Lead DevRel @ ENS Labs

You've developed an innovative and frictionless way for people to monetize their domains, empowering users to unlock new value with ENS.
Alex Netto testimonial photo

Alex Netto

Founder of Blockful

We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions
Patricio testimonial photo

Patricio

Founder of POAP

Namespace has quickly become the go-to platform for managing ENS subnames. What was once confusing and error-prone is now a streamlined, intuitive experience.
Ben testimonial photo

Ben

Co-founder of ETH.LIMO

Namespace is the best tool for creating and issuing ENS subdomains, I think. The dashboard is very easy to use.
Sahil testimonial photo

Sahil

DevRel at QuickNode

The Namespace team is incredibly friendly and a pleasure to work with. Their passion and dedication to the ENS ecosystem are evident in everything they do.
Thomas Clowes testimonial photo

Thomas Clowes

Co-founder of Unruggable

Our experience working with Namespace has been exceptional. Their team combines strong technical expertise with clear communication and a true spirit of partnership.
Kate testimonial photo

Kate

Head of Product & GTM @ CELO

From simple to complex Subname needs, Namespace has the tools and expertise to make it happen. Fully recommend.
Simon testimonial photo

Simon

Lead DevRel @ ENS Labs

You've developed an innovative and frictionless way for people to monetize their domains, empowering users to unlock new value with ENS.
Alex Netto testimonial photo

Alex Netto

Founder of Blockful

We have found in Namespace an efficient partner that quickly understood our needs and provided very solid solutions
Patricio testimonial photo

Patricio

Founder of POAP

Namespace has quickly become the go-to platform for managing ENS subnames. What was once confusing and error-prone is now a streamlined, intuitive experience.
Ben testimonial photo

Ben

Co-founder of ETH.LIMO

Namespace is the best tool for creating and issuing ENS subdomains, I think. The dashboard is very easy to use.
Sahil testimonial photo

Sahil

DevRel at QuickNode

The Namespace team is incredibly friendly and a pleasure to work with. Their passion and dedication to the ENS ecosystem are evident in everything they do.
Thomas Clowes testimonial photo

Thomas Clowes

Co-founder of Unruggable

Send-flow live in days,not quarters

It's time to give your customers payable names.

Try it without code

Issue your first usernames in minutes with the no-code app. No contracts, no gas.

Issue payable ENS usernames with no code required

Build it into your app

Add username claiming and send-flow resolution with a few lines of TypeScript.

Build payable names with the Namespace SDK and API

Partner with Namespace

Custom features, white-glove integration, partner pricing. Let's scope your integration on the call.

Partner with Namespace for payable name infrastructure