Private receiving for named accounts
Keep each payment separate.
Share your NEAR name. Receive each payment in a separate account, then find it in your private inbox.
An illustration of private receiving. These are not live account records.
What anyone sees for alice.near
Public activity on the named account
No new payments to this name in this example.
What Alice sees
Private payments found with her keys
Payment 010.0100 NEAR
Payment 020.0250 NEAR
Payment 030.0400 NEAR
Each payment has a separate destination.
Network details
- Network
- NEAR testnet
- Registry
- registry2.veil-williams.testnet
- Router
- router2.veil-williams.testnet
Receive with your name
Set up once. Share your name whenever someone needs to pay you.
Connect wallet
Choose the testnet wallet whose name you want to share.
Enable Veil
Sign a message to open your private inbox. Your keys stay in this browser. No payment is made.
Connect your wallet to continue.Register your name
Make your name ready for private payments. Your wallet will show a 0.0100 NEAR storage deposit plus the network fee.
Enable Veil before registering.Share your name
Auditor access
An auditor key lets someone find your incoming payments. It cannot spend them. Share it only with someone you trust.
Earlier inbox
On 14 November 2026 Veil changed the message it asks you to sign, so new keys open a new inbox. Payments sent to keys from the earlier message stay in the earlier inbox. Open it to see and spend them.
Use the same wallet signing key when you return. A different key opens a different inbox.
Send to a name
The recipient receives in a fresh account. You can send without enabling a private inbox of your own.
Private payments
Scan for incoming payments and check the balance in each account.
Enable Veil to find payments sent to you.
Choose a destination and an amount, then press Spend on a payment. The destination becomes publicly linked to that payment, and paying several payments to one destination links them together.
| Payment | Receiving account | Available NEAR | Actions |
|---|
Balances are rounded to four decimals. Any spend publicly links the receiving account to its destination.
Auditor
See incoming payments with a shared auditor key. This mode cannot spend.
Enter a registered name and auditor key to see incoming payments.
How it works
Veil uses a NEP-413 signed message to derive spending and viewing keys in your browser. Registration publishes only their public keys.
A sender derives a fresh implicit account for each payment and posts an announcement. Your viewing key and a view tag help your inbox find the matching payments.
The auditor key is your private viewing key: a 32-byte value written as 64 hexadecimal characters. It reveals incoming payments, but cannot sign a spend.
Amounts, timing, senders and token contracts stay public. Combining balances or sending to a named account can reveal links. Concurrent sends can move an announcement to a later position; your inbox also checks the 32 positions before each one, so those payments are still found.
Keep the same wallet signing key: a different key opens a different inbox. Keys made with the earlier Veil message open from Earlier inbox.