👋Introduction

Welcome to Reveel Pay(ID) Documentation

What is Pay(ID)?

Pay(ID) is the first universal stablecoin payment identifier — a simple, human-readable ID (e.g. alice(id)) that allows anyone to receive any stablecoin, from any network, and have it settle in their preferred token, network, and wallet.

Instead of sharing complex wallet addresses across multiple blockchains, users share a single Pay(ID). Behind the scenes, Reveel routes incoming stablecoin transfers across networks and assets, abstracting away fragmentation and enabling seamless peer-to-peer and app-driven payments.

Pay(ID) transforms how money moves in Web3 — enabling interoperable, programmable, and chain-agnostic stablecoin transactions in a single click.

Why Pay(ID)?

Web3 stablecoin payments are powerful, but the user experience is fundamentally broken:

  • Hyper-fragmentation: 200+ stablecoins across dozens of chains

  • Inconsistent identifiers: Different addresses per chain, per user, per wallet

  • High failure risk: Users send to the wrong chain, wrong token, or wrong format

  • Complex UX: Bridging, swapping, and routing are manual, technical, and error-prone

Pay(ID) solves this. It abstracts away the complexity by letting users define how and where they want to receive funds — and letting developers integrate stablecoin payments without worrying about chains, assets, or liquidity.

How it works

For Users:

  1. Register a Pay(ID) via the Pay(ID) Dashboard or integrated apps.

  2. Link your wallets and configure “Routes” — rules for how to receive funds.

  3. Share your Pay(ID) with anyone. Incoming funds are automatically resolved, swapped, bridged, and settled to your chosen wallet.

For Developers:

  • Offer Pay(IDs) to your users through your app (including registration, routing, and wallet management).

  • Use the Reveel API to resolve any Pay(ID) to a real transaction route.

  • Monetize adoption via Pay(ID) referral economics.

Getting Started

End Users:

→ Visit the Pay(ID) Dashboard to register your Pay(ID) and configure your Routes.

Developers:

→ Jump to the Developer Guide for API access, integration steps, and example implementations.

Last updated

Was this helpful?