Use cases

Crypto wallets can issue short names under their own brand (a namespace). Under Rabby, that looks like shahtab.rabby: shahtab is the person or shop, .rabby is Rabby’s namespace.

Example: your friend is paid as shahtab.rabby inside Rabby. You’re in another crypto wallet that doesn’t know Rabby’s naming system. Without a shared resolver you’d switch apps or paste a long 0x… address.

With Rezva, your wallet resolves shahtab.rabby, shows who you’re paying, and loads the onchain destination (network, asset, address). You confirm and send crypto in the wallet you already use. Rabby still owns the namespace; Rezva is the lookup layer.

People already put an email on invoices. If that email is registered as a Rezva identifier, a crypto wallet can resolve it to a payment destination instead of asking for a raw address.

Example: a freelancer lists pay@studio.example on an invoice. You open your crypto wallet, enter that email, Rezva returns Base USDC (or whatever they registered), you confirm, and the wallet sends the transfer.

Without Rezva, that email is just text unless you both use the same closed app that invented “pay to email.”

Many merchants already show a national or regional payment QR (for example Bangla QR, SGQR, QRIS). That QR string can also be registered in Rezva as an identifier that points to a crypto destination.

Example: a café keeps one QR sticker for local apps. A customer with a crypto wallet scans the same QR. The wallet sends the QR payload to Rezva, gets back the linked onchain destination, and the user pays with crypto - no second “crypto only” sticker required.

Rezva does not run the national payment network. It only resolves the QR identifier into crypto payment options for compatible wallets.

Open on YouTube

Merchants share PayPal links, Cash App links, or similar payment URLs and QRs. Those normally open that app’s checkout. In Rezva they can also be registered so a crypto wallet resolves them to an onchain destination.

Example: a shop shows a Cash App or PayPal QR / link at the register. Your crypto wallet scans or pastes it, Rezva returns the registered crypto payment option, you confirm chain and amount, and the wallet sends crypto. The shop keeps the same link or sticker.

Open on YouTube

A merchant ID is a stable business handle in the registry (Rezva type merchant_id). It is not a PayPal/Cash App URL and not a national QR payload. It is the ID you register once and point at crypto destinations.

Example: Northwind Coffee registers northwind-coffee as a merchant ID with a Base USDC destination. Customers type or select that ID in a compatible crypto wallet, see “Northwind Coffee,” confirm, and send USDC. If Northwind later changes the receiving wallet or adds another network, the merchant ID stays the same; only the destination mapping updates.

Multi-store: they can also register northwind-store-12 and northwind-store-18 so each location maps to its own crypto destination while keeping clear names at confirm time.

A phone number can be registered as a Rezva identifier that maps to a crypto destination, the same way people already save numbers in contacts.

Example: you pay a contractor at +15551234567. In a compatible wallet you enter that number, Rezva returns their registered onchain destination, you confirm, and the wallet sends crypto - no reading a long address over the phone.

Crypto wallets each invent their own naming. Someone is shahtab.rabby in Rabby; you use a different wallet on the same chain. Without a shared resolver, that name is useless outside Rabby.

Example: you stay in your wallet, resolve shahtab.rabby through Rezva, get the crypto payment options, and send. Each wallet can keep its own namespace; Rezva makes those names payable from other compatible wallets.