Rezva

Use familiar identifiers to send crypto.

Register phone numbers, emails, QR codes, and other identifiers with Rezva, or use names you already own from supported naming systems like ENS, SNS, and Unstoppable Domains. Rezva resolves them to the right payment destination for compatible wallets.

Product demoYouTube

Currently testing on Base

Disclaimer

Identifiers are used only for resolution. Rezva does not process, receive, or modify payments through the original payment service. The crypto payment is handled separately by the compatible wallet.

Enter a name or QRSee the merchantPick how to payConfirm in your walletPayment settles onchain

01 / Features

Turn existing payment identifiers into crypto destinations.

Rezva lets compatible wallets resolve familiar identifiers, from payment links and QR codes to usernames, phone numbers, and wallet names, into the crypto address behind them. This makes crypto payments easier to send without replacing the identifiers businesses already use.

Universal Name Resolution

Resolve ENS, Base Names, SNS, and Unstoppable Domains through the same API. New naming systems do not require a wallet update.

Provider namespaces

Wallets offer branded names like coffee.rabby. People pay with a name they trust, and the destination stays under that wallet's namespace.

Existing payment QRs

Register PayPal links, Cash App QR, Bangla QR, SGQR, QRIS, and other national QR strings so crypto wallets can pay the same sticker.

Email, phone & IDs

One resolve API

Wallets keep scanning, signing, and sending. Rezva only answers where the payment should go.

02 / How it works

Identifier in. Destination out.

When a wallet has an identifier, it asks Rezva to resolve it. Rezva normalizes the value, finds the active mapping in the registry or through Universal Name Resolution (UNR) for names like vitalik.eth, checks that the destination can receive funds, and returns payment destinations. The wallet picks a network and asset, then signs and sends the transfer itself.

Resolution path

coffee.rabby

Identifier input

Phone identifier+880 1840 123456

QR payload000201… Bangla QR

Merchant identifierABC-19384

Email identifierpay@shop.com

Namespace namecoffee.rabby

UNRvitalik.eth

Resolved ascoffee.rabby

resolve

Rezva registryNormalize · resolve · verify

NormalizeConvert the raw input into a standard form

ResolveFind the mapping in the registry, or via Universal Name Resolution

VerifyConfirm the destination is ready to receive funds

ReturnHand payment destinations back to the wallet

Mapping statusActive

Destination readyYes

Last destination change6 months ago

destinations

Returned to wallet3 payment destinations

Ready

USDCBase

Preferred

USDCEthereum

USDTArbitrum

Wallet actionSelect destination, sign, send

SpeedResolution usually under 100ms

IdentityMerchant profile included when available

Change alertsFlagged if the destination moved recently

CustodyPrivate keys stay in the wallet

03 / What you can register

Use what people already know.

Register a phone, email, QR, or a wallet name like coffee.rabby. Compatible wallets can also resolve Universal Name Resolution names such as vitalik.eth. Customers type what they already know. Wallets look up where to send the money.

PhoneNumbers people already save

QR codeNational payment QR strings

EmailInboxes customers know

Universal Name ResolutionENS, Base, SNS, Unstoppable names

Wallet nameNames like coffee.rabby

CustomYour own identifier type

Payment QR codes

Same sticker. Crypto wallets too.

Many countries already use one QR for banks and apps. You can register that same QR with Rezva so crypto wallets can pay it too - without a new sticker for every wallet.

Bangla QRBangladesh

QRISIndonesia

SGQR+Singapore

BHIM / Bharat QRIndia

DuitNow QRMalaysia

PixBrazil

Cash AppUnited States

PayPalGlobal

Rezva is not partnered with or affiliated with these payment schemes or brands. Names and logos are shown only as examples of identifier types people already use.

04 / Built for wallets

Add lookup. Keep everything else.

Your wallet still scans, builds, signs, and sends. Rezva only answers: where should this payment go?

For wallet appsHow deep do you want to integrate?

Approved access

Smallest start

Look up only

Scoped access

Add name and QR lookup to the send screen you already have. You still build and sign payments yourself.

Look up phones, QR codes, emails, and wallet names

Show who they are paying and how

Keep your current confirm and send flow

No need to build a merchant signup UI

Integration surface

POST /v1/resolvepayment_options[]

resolve-payment.ts · Rezvav1

1import { ResolverClient } from "@universal-payment/sdk";23const client = new ResolverClient({4  baseUrl: "https://api.example.com",5  apiKey: process.env.REZVA_API_KEY,6});78const result = await client.resolve({9  type: "provider_name",10  value: "coffee.rabby",11});

20042ms · application/json

{
  "status": "active",
  "payment_ready": true,
  "profile": { "name": "Northwind Coffee" },
  "payment_options": [{
    "asset": "USDC",
    "chain": "base"
  }]
}

TypeScriptUTF-8Ln 11

05 / For builders

One simple lookup for wallets.

Send a type and value. Get back whether it is ready to pay, who it belongs to, and which networks and coins work.

Open docsApproved wallets in productionYou keep custody

06 / Before you pay

See who you are paying.

Instead of pasting a long address, you look up a name people already use. Your wallet shows the shop, how they accept money, and where it goes - then you confirm.

01
Who
a clear shop or brand name, not a random address
02
How you found them
phone, email, QR, or a wallet name like coffee.rabby
03
How to pay
currency and network your wallet supports
04
Where it goes
the receiving address, with a warning if it changed recently

SendRezva

Northwind CoffeeVerified shop name

12.00USDC

on Base

Found as