Console overview

The official Rezva dashboard is a shared console for businesses and wallet providers. Both enter through the same UI; each track unlocks only after that track’s application is approved. Free API is separate from those tracks: it is always available after sign-in for prototypes.

Entry

Open /dashboard from the site header or marketing CTAs.

Which API key do I use?

The dashboard shows more than one credential path. They are not interchangeable. Pick the key that matches what you are building:

• Free API key (/dashboard/free-api) — for learning, prototypes, and resolver testing. No provider approval. Works only with POST /v1/resolve. Lower rate limits. Pairs with the shared Test Merchant. Not for production wallets.
• Provider API key (/dashboard/provider/api-keys) — for production wallet integrations after the Wallet Provider track is approved. Higher limits. Required for production resolve traffic, namespaces, and merchant-setup APIs. Free API keys never unlock these routes.
• Business track (/dashboard/business/apply) — not an API key for wallets. Merchants use it to register their own identifiers and payment destinations in the UI after approval.

Free API key      → resolve only, prototypes / testing
Provider API key  → resolve (+ optional setup) after approval, production
Business track    → manage your own identifiers in the dashboard UI

Full Free API walkthrough: Free API and Test Merchant. Production wallet auth: Authentication.

Which track do I need?

• Free API — prototype resolver integration and shared Test Merchant testing (no approval).
• Business — own identifiers and payment destinations (application required).
• Wallet Provider — production resolver access and optional merchant setup (application required).
• Operator — review providers, complaints, names, and safety actions (operator credentials).

Navigation

• Overview - shared entry and status for both tracks
• Business - apply, then manage profile, identifiers, destinations, activity, complaints, settings
• Wallet Provider - apply, then overview, integration, API keys, usage, webhooks, sandbox, namespaces, settings
• Free API - resolver-only testing key and Test Merchant QR flow, available without provider approval
• Developers - docs, SDKs, sandbox references
• Support - help channels

Application states

Not applied → submitted → under review → approved (track unlocked) or rejected (reason + reapply). Free API does not use this application flow.

Operational rule

Dashboard access does not grant blockchain custody or transaction authority. The dashboard configures registry data and credentials; the user’s wallet remains responsible for signing and broadcasting payments.