Rezva overview

Core idea

Every request combines an identifier type and value. The resolver normalizes that value, finds the authoritative mapping, and returns payment destinations that the requesting wallet can use.

Identifier type + value
          ↓
       Resolver
          ↓
Crypto payment options
          ↓
Existing wallet payment flow

Examples include phone numbers, email addresses, existing payment QR values, merchant IDs, custom identifiers, and protocol-native names.

What Rezva does

• Accepts a typed identifier from QR input or manual entry.
• Applies type-specific normalization and validation.
• Resolves protocol-owned identifiers through the registry.
• Uses an authoritative resolver for supported external crypto names.
• Returns lifecycle status, trust timestamps, and payment options.

The same QR, another payment rail

A merchant can keep using an existing QR code. A traditional payment application interprets it through its own network, while a compatible crypto wallet extracts the identifier and asks Rezva for a crypto destination.

Existing QR
   ├─ Traditional app → existing payment network
   └─ Crypto wallet   → Rezva → blockchain payment

Rezva does not need the original payment provider to process or settle the crypto transaction. The transaction goes directly from the user’s wallet to the resolved destination.

Who does what

• Rezva resolves identifiers and reports safety state.
• Registry stores controller-owned mappings and audit events.
• Wallet displays options, gets user confirmation, and executes payment.
• Controller authorizes registration and destination changes.
• Provider integrates the resolver and receives scoped access.

Rezva is not a wallet, payment processor, exchange, blockchain, or custody service. It does not initiate, sign, broadcast, or settle transactions.

Start building

1. Read How It Works for the complete flow.
2. Use the wallet quickstart to add resolver support.
3. Use the Free API and shared Test Merchant for prototypes.
4. Apply as a provider before sending production resolver traffic.

The OpenAPI specification and full LLM reference provide machine-readable request details and copy-paste integration guidance.