# Key Concepts

## Overview

Pay(ID) is much more than a name — it's a complete protocol layer for programmable, omnichain stablecoin routing. This section introduces the **core building blocks** that power the Reveel Pay(ID) experience for users, developers, wallets, agents, and dApps.

Understanding these components helps you see how Reveel abstracts away complexity, manages intent-based routing, and enables powerful new UX across the Web3 ecosystem.

## Core Concepts Breakdown

***

### **1. Entry Points**

> **Users, Wallets, Agents, Apps, Custodians**\
> The Reveel journey starts here. Any actor can initiate a payment using a PayID. This entry point could be a user typing a PayID, an AI agent processing a transaction, or a DApp triggering an API call.

***

### **2. PayID**

> **The Universal Identifier**\
> A human-readable ID (e.g. `alice(id)`) that works across chains, tokens, and apps.\
> PayIDs abstract wallet addresses and act as programmable payment endpoints.

* Linked to wallets across multiple chains
* Support ENS, Lens, MocaID and other namespaces
* Can receive *any* supported stablecoin
* Maps to user specific route configurations

***

### **3. Routes Engine**

> **Custom Payment Logic**\
> Routes define **how incoming funds should be handled**, based on:

* Sender (e.g., if Bob pays me…)
* Token (e.g., if USDC…)
* Chain (e.g., if received on BNB…)

This logic defines the final output:

* Which wallet?
* On which chain?
* In which token?

Think of it as "IF THIS, THEN THAT" for payments.

***

### **4. Data Layer**

> **Persistent Identity & Routing Storage**\
> This is the metadata brain of Reveel:

* Stores PayID registrations
* Linked wallet data (onchain + offchain)
* Routes and preferences
* Metadata: ENS, email, app namespace, MocaID

It powers instant resolution, personalization, and cross-app interoperability.

***

### **5. Liquidity Engine / Orchestration Layer**

> **Cross-Chain Optimization**\
> The routing system plugs into bridge & swap partners (e.g., Decent, LayerZero, Stargate etc. ) to:

* Query bridge liquidity
* Evaluate gas costs
* Optimize routes for fees, slippage, and time
* Choose best bridge/swap path

This enables **chain abstraction** behind a single PayID.

***

### **6. Settlement Layer**

> **Final Delivery to Target Wallet**\
> Once a route is selected and liquidity path chosen, the Settlement Layer:

* Executes the crosschain transactions 
* Transfers funds to the user’s preferred wallet, in the right token & chain
* Emits success/failure receipts to APIs/webhooks


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.reveel.id/introduction/readme-1.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.