Receive payments to a Web3 name
This is what Web3 names do best today. Someone types a readable name instead of a long address, and the payment arrives in your wallet.
This is what Web3 names do best today. Someone types a readable name instead of a long address, and the payment arrives in your wallet.
When someone sends a payment to your name, their wallet looks up the receiving address you set in the name’s records and sends the funds there. The name is a label in front of the address. The money never passes through the name, the provider or us.
That gives you one readable line for an invoice, a stream overlay or a shop counter, instead of a forty-character address that is easy to mistype. It works only in wallets that support the naming system your name belongs to, and only on the networks you have set addresses for.
Use a wallet you control and have backed up. Guide 04 covers this step.
Ask a friend, or use a second wallet, to send a very small payment to the name. Confirm it arrives and that the address shown on the sending side matches yours.
If you set an address for only one network, payments on other networks will not reach you. Tell payers which network to use.
Some payers will use a wallet that cannot read the name. Put the full address on the same invoice or page as a fallback.
Endings can look alike. Write the full name with its ending, for example studio.chainwallet, and do not shorten it in messages.
Say which network you expect the payment on. A payment on a network the name has no address for may be lost or need a manual recovery.
Ask them to confirm that their wallet shows an address after they type the name. If it shows nothing or an error, they should stop and ask you.
A blockchain payment sent to the wrong address stays there. Nobody, including the provider, can pull it back. Test before you publish the name, test again after every change to its records, and never change the receiving address because a message asked you to.
On most public blockchains, payments are visible to anyone who looks up the receiving address. A name makes that address easier to find, so treat it as public.
No. Payments go directly from the payer’s wallet to yours. The only cost is the network fee the payer pays when sending.
No. A Web3 name works with blockchain payments in supporting wallets. For cards you still need a payment provider.
Update the receiving address in the name’s records, then send a test payment. Until you do, payments keep going to the old wallet.
If the name should move to another wallet or another person, the last guide covers transfers.