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