Skip to content
HOOD USDB.
/// Pay Links[02]

Pay someone who has no wallet. They do not need one.

A one-time link carries the amount. The recipient opens it in any browser, takes the money into an account or straight to an address, and never learns what a seed phrase is.

Recipient needs
A browser
Gas
Paid by the relayer
Unclaimed
Auto-refund at 7 days
Create + share
Free
A pay link created and escrowed against the sender's ledger balance, claimed in a browser by a recipient with no wallet — and, on the alternate branch, the seven-day timeout that returns an unclaimed link to the sender automatically.
How it works[01] Flow

Three steps for you. One tap for them.

01

Attach an amount

Pick a figure and a privacy level. Hood USDB mints a single-use link. Nothing about the recipient is needed at this point, because at this point there is no recipient.

One-timeAny privacy level
02

Share it anywhere

Text it, DM it, email it, print it on a card. The link is the rail; the channel is whatever you already use. It carries an amount and a claim token, and nothing that identifies you.

Message · email · DM
03

They claim it

The link opens a page in any browser. They either sign in with a wallet they already have and take the credit in-app, or paste an address and receive the payout on-chain. The relayer covers the gas either way.

Claim to accountOr to any addressRelayer-paid gas
Escrow[02] Safety

Your money is not in limbo while the link is out.

The amount moves into ledger escrow the moment the link is created. It leaves your available balance, so you cannot spend it twice — and it has not left the protocol, so it can come back.

  • 01Escrowed against your ledger balance, not sent anywhere
  • 02Cannot be double-spent while a link is outstanding
  • 03Claimable exactly once — settlement is atomic
  • 04Unclaimed after seven days, it returns to you automatically
  • 05You can cancel a link yourself before anyone claims it
The timeout branch: an unclaimed pay link sweeps a seven-day timeline at a strictly linear pace, its chip goes dashed and struck through on day seven, and the escrowed amount counts back into the sender's available balance as an automatic refund.
Usernames[03] Identity

An @username instead of forty-two characters nobody can check.

Claim a name in Settings and people pay you by it. The resolution happens server-side, so a sender never sees your address — which means the convenience and the privacy are the same feature rather than a trade against each other.

ONE-TIMEPay link0.1000 ETH · HELD@usernameresolved server-side0x addressvalidated EVMa browserno wallet neededan agentscoped keyUNCLAIMED AFTER 7 DAYS · REFUNDS TO THE SENDER
ReachesHow
@usernameLive lookup confirms the account exists. Their address is never returned to you.
0x addressValidated as an EVM address. In-app if it is one of ours, a withdrawal if not.
A browserThe pay link opens anywhere. No install, no seed phrase, relayer-paid gas.
An agentA scoped key settles the request under a spending policy and returns a receipt.
01

Payable by name

Three to twenty characters: letters, numbers, underscores, hyphens. A live lookup confirms the name exists before anything is signed.

02

Your address stays yours

A sender resolving @you never receives your wallet address. The lookup returns an account, not a destination they could go and read.

03

Addresses still work

Paste a 0x address and it is validated as an EVM address. If it belongs to a Hood USDB account they are credited in-app; if not, that is a withdrawal, and the app says so.

Payment requests[04] x402

A priced request, settled exactly once.

Payment requests follow the x402 pattern: a payee names a price, shares it, and anyone can settle it. Use them as invoices, as checkout for a service, or as machine-to-machine pay-per-call — the same object serves a freelancer and an API.

Settlement is atomic, so a request can never be paid twice. Concurrent payers past the first get an explicit conflict rather than a silent duplicate.

StatusMeaningTerminal
pendingCreated and awaiting payment. The creator can still cancel it.No
settledPaid. Records who paid and the settlement reference, and returns a signed receipt.Yes
cancelledWithdrawn by the creator before anyone paid it.Yes
409A second payer arrived after settlement. Refused, not duplicated.
POST /api/x402/verify-receipt
{
  "valid": true,
  "settlement": "settled",
  "signer": "0x4Ae…91",
  "payment": { "amount": 0.0001, "token": "ETH" }
}

Every settlement returns a receipt a payee can check before delivering anything — on our endpoint, or offline with one signature recovery and no API key.

Fees[05] Cost

Two numbers. Everything else is relative.

The withdrawal fee and the internal transfer fee are fixed and published. The rest is set from a live schedule, so we describe the shape rather than print a table that would be wrong by the time you read it.

ActionFee
Transfers between accounts — user to user, agent to userFree
Creating a pay link or a payment requestFree
Settling oneFollows the transfer or withdrawal fee of its path
ETH withdrawal1.5%
USDG withdrawalShown at confirmation
Full-privacy depositA small routing fee during mixing, plus network gas
Agents APINo extra fee — the same as the underlying action
Between accounts
Free
Ledger-settled. No gas, no fee, no on-chain trace.
ETH withdrawal
1.5%
Paid on-chain from the pooled reserve on Robinhood Chain.
Refund window
7 days
After which an unclaimed pay link returns to the sender automatically.
Next

People are not the only thing that needs to be paid.

The same request object a freelancer sends as an invoice is what one piece of software presents to another. Agents settle x402 requests under a spending policy, and hand back a receipt.

Agents
An agent presenting a scoped key, refused by its per-transaction limit before any funds move, then settling a smaller request and emitting a signed receipt.