Company
About Rezva
Rezva is a shared payment identity and resolution layer, so wallets and payment apps can look up who you’re paying and where funds should go, without inventing a new proprietary address book each time.
What we are
Rezva maps everyday payment identifiers (names, emails, phones, merchant IDs, payment links, QR codes, and custom strings) to crypto payment destinations that compatible wallets can resolve at send time.
We are not a bank, exchange, or card processor. We do not move money on behalf of PayPal, Cash App, bKash, or any other rail. Rezva answers a lookup question: given this identifier, what destination should a compatible wallet use, and who does it represent?
What we build
A public registry and resolver for payment identifiers, a dashboard for businesses and wallet providers, and integration paths so apps can register identifiers and resolve destinations through the same shared layer.
Operators review applications, manage protected names, and handle reports. Wallet providers connect through documented APIs and SDKs. Merchants and individuals register identifiers that map to destinations they control.
Start with how it works, use cases, or the protocol docs.
Who it’s for
Wallets and payment apps that want one resolution path for namespaced usernames, emails, phones, merchant IDs, links, and QR identifiers, instead of maintaining a closed lookup silo.
Merchants and platforms that already show customers a familiar identifier (a shop name, invoice email, national QR, or payment link) and want compatible crypto wallets to resolve that same identifier to an onchain destination.
Integrators building on Rezva via the integrate page and dashboard applications for business or provider tracks.
How to reach us
Partnerships, integrations, and operator questions go through contact. Research and grant interest is outlined on grants / research.
Disclaimer
Important: Rezva identifiers are used only for resolution. Rezva does not process, receive, hold, settle, or modify payments through PayPal, Cash App, bank rails, national QR networks, or any other original payment service. When you pay with crypto, the transfer is created and confirmed inside a compatible wallet (or payment app) that integrates Rezva, not by Rezva itself.
Not a payment rail. Registering or resolving an identifier does not mean Rezva operates that rail, endorses the linked merchant, guarantees delivery of goods or services, or replaces the terms of the destination network or asset you choose. National and brand payment systems (for example Bangla QR, SGQR, QRIS, PayPal links, Cash App links or QR codes) remain those systems; Rezva only stores and returns mapping data that wallets may use for lookup.
Verify before you send. Always confirm the resolved display name, destination address or account, network, and asset in your wallet before signing. Rezva cannot reverse onchain transfers. Report suspicious or incorrect mappings via Report / Dispute.
Identifier examples include names and usernames, email addresses, phone numbers, merchant IDs, payment links, QR code payloads, and free-form custom values when registered as such. Examples people often recognize: PayPal payment links, Cash App payment links or QR codes, bKash QR, Bangla QR, SGQR, QRIS, and similar merchant QR or link formats. Support depends on what has been registered and what a given wallet chooses to resolve.
No affiliation implied. Mentions of third-party brands, apps, or national payment schemes are for illustration of identifier types only, unless we explicitly state a partnership. Rezva is independent of those services.
Product status. Parts of the protocol, pricing, and operator policies are still being built. Registry data, resolver responses, and dashboard review flows may use evolving infrastructure. Production terms and privacy notices will continue to be updated on the terms and privacy pages.