> For the complete documentation index, see [llms.txt](https://docs.reveel.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reveel.id/core-services/payid-registration.md).

# PayID Management

**PayIDs** are:

* A **globally unique identifier** linked to a user (e.g., `Alice(id)`)
* **Chain-agnostic**: works across EVM networks (Ethereum, Base, Polygon, Optimism, etc.)
* **Wallet-flexible**: mapped to one or more wallets, configured through routing logic
* **Human-friendly**: branded and easy to remember, like ENS or Lens handles
* **Programmable**: supports rules for incoming token/network and maps to destination logic

PayID enables seamless user-to-user and app-to-user payments without needing to deal with bridging, token conversions, or wallet compatibility on the sender’s side.

***

### Lifecycle of a PayID

| Phase                    | Description                                                                 |
| ------------------------ | --------------------------------------------------------------------------- |
| **Registration**         | Partner creates a user → claims a PayID via `/payid/claim`                  |
| **Validation & Pricing** | Pricing is determined by AI scoring (free if ≥13 characters)                |
| **Checkout**             | For premium PayIDs, a Loop checkout URL is provided                         |
| **Reservation**          | PayIDs are temporarily reserved until checkout expires or succeeds          |
| **Activation**           | After payment confirmation (via webhook), the PayID becomes active          |
| **Search & Resolve**     | PayIDs can be searched or resolved using `/payid/search` or metadata lookup |

***

***

### PayID Metadata

Each PayID is associated with:

* **userId**: backend identity
* **walletAddress**: default wallet (may be overwritten by routes)
* **email**: optional
* **twitterUsername**: optional
* **ENS/DID**: optional integrations (future)
* **Routes**: active payment logic mapped to incoming tx conditions


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.reveel.id/core-services/payid-registration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.